Dub a scene after you set the timing.
Dub Packs build on Voice Pack-style prompts, but Dub Mode needs a video and metadata that tells the game when each sample belongs in that video. Treat it as an advanced format, not a Voice Pack with one extra file.
- 01
Start with a short OGV scene
The official Dub workflow requires OGV because of the video support available to the game. Convert and play one small scene before preparing many lines.
- 02
Create the samples players will record
Use a small set of clearly distinct lines so you can recognise a timing error immediately during testing.
- 03
Add timing metadata for every sample
Record the timing information that tells the game where the sample belongs in the video. Validate each entry against the scene, not against memory.
- 04
Run the full reveal
Test the Dub flow through to the saved combined playback. Check both individual retakes and the final sequence.
Do not carry Voice Pack filename assumptions into Dub metadata. OGV and per-sample timing are required parts of the Dub workflow.
Ready to test
- The scene is an OGV video.
- Every sample has its own timing metadata.
- A short scene was tested before adding more lines.
- The final Dub playback matches the intended timing.
Quick answers
Dub Pack FAQ
Most Dub Pack failures come from treating video timing or the video format as optional.
Next step
Keep the first Dub Pack small and testable.
Validate one short scene, its OGV file, and each timing entry before adding a larger set of lines.