Video-model duration compatibility in OfflineCreator Studio

The current Studio compatibility matrix

OfflineCreator Studio's public catalog currently lists three launch video paths: Kling 2.6 Pro for text-to-video, Kling 2.6 Pro Motion for image-to-video, and Veo 3.1 Fast for text-to-video. A current deployed first-party catalog bundle exposes the exact configured fal endpoints and duration fields: five seconds for both Kling paths and eight seconds for Veo.

The underlying fal schemas accept more values: five or ten seconds for both Kling endpoints, and four, six, or eight seconds for Veo. Provider compatibility is therefore broader than Studio's current five/five/eight configuration. The published OfflineCreator MCP `generate` schema exposes no duration argument, so an MCP caller cannot override the configured length directly.

Kling 2.6 Pro

Studio: 5 seconds · Provider: 5 or 10Configured endpoint: fal-ai/kling-video/v2.6/pro/text-to-video. Public MCP duration control: not exposed.

Kling 2.6 Pro Motion

Studio: 5 seconds · Provider: 5 or 10Configured endpoint: fal-ai/kling-video/v2.6/pro/image-to-video. Public MCP duration control: not exposed.

Veo 3.1 Fast

Studio: 8 seconds · Provider: 4, 6, or 8Configured endpoint: fal-ai/veo3.1/fast. Public MCP duration control: not exposed.

Separate provider compatibility from Studio compatibility

A provider endpoint can accept more values than a product exposes. fal's current Kling 2.6 Pro text-to-video schema defines `duration` as an optional string, defaults it to `"5"`, and accepts `"5"` or `"10"`. The corresponding image-to-video endpoint publishes the same duration enum and default. These facts describe fal's endpoint contracts; they do not make ten seconds selectable in OfflineCreator Studio.

Veo uses a different value format. fal's current Veo 3.1 Fast text-to-video schema accepts `"4s"`, `"6s"`, or `"8s"` and defaults to `"8s"`. Kling's documented values omit the suffix. Studio's deployed catalog proves the selected numeric durations and endpoints, but it does not expose the server-side request body. Do not infer live provider acceptance merely because the configured value appears in the catalog.

What the accessible evidence does and does not prove

The reader-accessible primary sources prove the deployed five/five/eight model configuration, the public MCP surface, and the provider duration enums. They support this compatibility table and the warning that an MCP caller cannot select a different duration. They do not expose Studio's server-side provider request or show a completed generation.

No reader-accessible Studio duration acceptance-test artifact was found. This page therefore treats the deployed bundle as configuration evidence, not proof that a live provider accepted the constructed payload. It makes no claim about private test coverage, invalid-duration rejection, queue success, returned file length, or whether an undocumented service layer transforms the configured value.

Continue with the model or budgeting guide

Use the model directory to refresh the launch catalog, open a Kling guide for the relevant input workflow, or move to the budgeting guide after the duration decision is fixed. These links answer the next operational question without turning this page into a general model ranking.

Evidence boundary and refresh rule

This page owns the narrow compatibility question for clip duration across Studio's configured endpoints, published MCP surface, and underlying provider schemas. It does not claim that Studio exposes every duration supported by fal, that a locally constructed payload reached or was accepted by the provider, that one clip length is better, or that a provider enum will remain unchanged.

Recent community evidence was insufficient: the engine returned 76 items, but none substantiated Studio's configured duration compatibility. Digg was rate-limited, Instagram errored, Reddit was partial, and X was not configured; arXiv, Polymarket, Techmeme, and YouTube completed with no results. No community item is used as a product claim. This pass performed no live paid generation, provider acceptance request, invalid-duration submission, or output measurement. Refresh the deployed catalog bundle, published MCP implementation, and fal schemas before editorial review.