Viggle

/

Viggle-Animate

Like 336

Follow

Viggle AI 535

Related to the image-background question in discussion #7. I understand Viggle-Animate and the website's Motion Control / Move are different workflows. If this question belongs in another official API support channel, please point me there.

The goal is to animate a character in a photo from a driving video, while retaining the photo's scene/background.

I tested the current public V1 API:

POST https://apis.viggle.ai/v1/renders
multipart/form-data:
  image = character photo
  motion_video = driving clip
  model = V4
  mode = full_pipeline
  background_mode = original

This transfers the major dance poses, but keeps the driving video's background. With the same source photo and clip, the website's Motion Control retains the photo scene. I also reproduced the latter through the website's authenticated first-party client with V4; I have not generated a V4.5 Pro result.

Additional checks:

• The website configuration identifies bgMode=3 as From Image, modelInfoID=5 as V4, and modelInfoID=7 as V4.5 Pro.
• The public /v1/renders endpoint rejects model=V4.5 Pro and model=V4.5_Pro with unknown model.
• mode=move / motion_control and background_mode=image / from_image are rejected.
• Adding the website fields modelInfoID=7 and bgMode=3 to the public request still yields the video background. An invalid-number control is also accepted, so acceptance does not establish that these selectors work.

Could you clarify:

1. Which supported public REST endpoint/parameter selects Move with the image background?
2. Is V4.5 Pro available to API-key clients under a different model name or a separate account entitlement?
3. Does the official Meme MCP expose Move, or only Mix?

I am looking for a supported server-side integration. Generic H3 reference-to-video and Viggle-Animate character replacement do not by themselves establish the image-background Motion Control behavior. A minimal working request or official clarification would be very helpful. Thank you!