Files
Davids048andClaude Fable 5.1 a5aa64ab6b [refactor]: decide every config value before the config freezes, and drop the from_pretrained keywords
VideoGenerator.from_pretrained(model_path, config) takes the same nested
settings as from_config; the 24 flat keywords, from_pretrained_kwargs_to_config,
FROM_PRETRAINED_KWARGS, and every flat_field in the schema are deleted.
nvfp4_fa4 is the typed field engine.attention.nvfp4_fa4, applied by a
resolution step. 65 call sites and the docs use the nested form; the three
kwargs golden cases are config cases with byte-identical results.

Every value is decided during resolution; no runtime code calls
with_override. The device offload policy (unified memory, MPS, layerwise
conflicts, lazy module load) runs as resolution steps in the main process
(fastvideo/api/device_policy.py), and the worker runs on the config it
receives. The LTX-2 refine defaults from model_index.json and the MiniMax-H3
schedule from fastvideo_inference.json are resolution steps
(fastvideo/api/checkpoint_defaults.py) that read local checkpoints or download
only those files; the H3 pipeline validates the schedule against the loaded
schedulers but no longer writes it. The preprocessing entry point passes the
downloaded local path as run state instead of a config override. Teacher and
critic models load with override_transformer_cls_name as a load argument.
The test isolation turns the device policy off, as it blocks downloads, so
that the goldens do not depend on the machine.

Against the 3f6893a0 goldens, every field still matches except boundary_ratio
and ltx2_vae_tiling (DESIGN section 9) and the fields that no longer exist.
The launcher and trainer YAML verifications report 0 unexplained differences.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-04 07:14:31 +00:00

4.5 KiB

Configuration

Multi-GPU Setup

FastVideo automatically distributes the generation process when multiple GPUs are specified:

# Will use 4 GPUs in parallel for faster generation
generator = VideoGenerator.from_pretrained(
    "Wan-AI/Wan2.1-T2V-1.3B-Diffusers",
    {"engine": {"num_gpus": 4}},
)

One node uses the multiprocessing executor (execution_backend: mp, the default). Two machines — for example two DGX Sparks, one GPU each — need Ray:

generator:
  engine:
    num_gpus: 2
    execution_backend: ray
    parallelism:
      sp_size: 2

Set RAY_ADDRESS and FASTVIDEO_HOST_IP to the interconnect IPs, not Wi-Fi. The FastH3 example selects Ray automatically when RAY_ADDRESS is set. Full bring-up: Pair two NVIDIA DGX Sparks.

Customizing Generation

VideoGenerator.from_pretrained(model_path, config) takes the startup settings as a nested mapping at their typed config paths, such as {"engine": {"num_gpus": 2, "offload": {"dit": False}}}; it is VideoGenerator.from_config with model_path added to the mapping. Pass generation settings to VideoGenerator.generate as a request:

from fastvideo import VideoGenerator

def main():
    model_name = "Wan-AI/Wan2.1-T2V-1.3B-Diffusers"

    # Create the generator
    generator = VideoGenerator.from_config({
        "model_path": model_name,
        "engine": {
            "num_gpus": 1,
            "offload": {"dit_layerwise": True},
            "precision": {"vae": "fp16"},
        },
    })

    # Generate video with custom parameters
    prompt = "A beautiful sunset over a calm ocean, with gentle waves."
    video = generator.generate({
        "prompt": prompt,
        "sampling": {
            # How many frames to generate
            "num_frames": 45,
            # Video resolution (width, height)
            "width": 1024,
            "height": 576,
            # How many steps we denoise the video (higher = better quality, slower generation)
            "num_inference_steps": 30,
            # How strongly the video conforms to the prompt (higher = more faithful to prompt)
            "guidance_scale": 7.5,
            # Random seed for reproducibility
            "seed": 42,  # Optional, leave unset for random results
        },
        "output": {
            "output_path": "my_videos/",  # Controls where videos are saved
            "save_video": True,
        },
    })

    # If return_frames=True, frames are available in video.frames
    print(f"Generated {len(video.frames)} frames")

if __name__ == '__main__':
    main()

JSON/YAML Config Files (CLI)

The inference CLI is config-first. Use an explicit subcommand with --config, then apply optional dotted overrides on top, matching the training CLI style. By default, CLI generation uses return_frames=false unless you set request.output.return_frames: true in config or via a dotted override.

fastvideo generate --config config.yaml

Example nested config:

generator:
  model_path: FastVideo/FastHunyuan-diffusers
  engine:
    num_gpus: 2
    parallelism:
      sp_size: 2
request:
  prompt: A capybara relaxing in a hammock
  sampling:
    num_frames: 45
    height: 720
    width: 1280
    num_inference_steps: 6
    seed: 1024
  output:
    output_path: outputs/

Override individual values from the CLI with dotted paths:

fastvideo generate --config config.yaml --request.sampling.seed 42

Where a Value Came From

FastVideo resolves the generator config once at startup and records the source of every value: the input config (input; explicit tells whether you wrote the value or it is the schema default), a FASTVIDEO_* environment variable, the model's defaults, or a derived value. A worker's device policy and values read from checkpoint files are recorded too.

generator = VideoGenerator.from_config(config)
generator.resolved_config.provenance("engine.parallelism.sp_size")
# PathProvenance(path='engine.parallelism.sp_size', value=2, source='derive_parallel_sizes', ...)

result = generator.generate(request)
result.resolved_request.provenance("sampling.num_frames")
# PathProvenance(..., value=81, source='fill_sampling_defaults[preset wan_t2v_1_3b]', explicit=False)

resolved_config.provenance_table() lists every path. Every value is decided before resolution ends, including the device offload policy and the checkpoint defaults; after that, resolved_config is read-only.

Performance Optimization

For configuring optimizations, please see our optimizations guide