Pipecat Simli max_session_length vs Sume's 4 to 60 second clip

What limits does Pipecat's Simli service set?

Pipecat describes Simli as real-time avatar video over WebRTC, animated by your agent's audio. The service takes an api_key and a face_id. It exposes max_session_length, the absolute maximum session duration in seconds, and max_idle_time, the maximum idle time before disconnect. Audio is resampled to 16 kHz internally.

What is the Sume equivalent?

There is no session on Sume, so there is nothing to disconnect. The limit is on the job: the target video duration, estimated from your script, must be 4 to 60 seconds inclusive. Longer scripts are rejected; split them into more jobs.

The aspect ratio is 1:1, 3:4, 9:16, 4:3 or 16:9 (default 9:16), at 720p.

How do I stretch past 60 seconds?

Split the script at sentence breaks into scenes of under 60 seconds and join the finished clips with Timeline. A Timeline render takes up to 200 video slots and bills $0.10 per output minute, so a three clip, 2 minute video is $0.30 to join, plus the avatar jobs.

For a pause where the avatar waits, use a silence voice input with a duration, which is covered in the silence beats post.

What should I check before choosing?

• Does the viewer need to interrupt? Then a live service fits and Sume does not.
• Is the script fixed? A recorded clip is cheaper per view and reviewable.
• Is the length under 60 seconds per piece? Then one job per piece works.