Mitti: prepare opening, holding and closing video cues

Version and starting information

This guide uses Mitti 2.8.19, revision 1449, dated September 28, 2026, as its reference, following the official changelog. It runs on macOS; record the OS version, Mac, connections, audio device and planned license. The web help describes the 2.8 family; compare its controls with the installed version.

Preserve original media and save a playlist copy. For each cue, record the approved filename, duration, aspect ratio, frame rate, audio and caller. A date and draft running order are enough to begin, even while final exports are pending.

Prepare each cue’s behavior

In Standalone, Enter plays the selected cue; JUMP can load or trigger it according to preferences. Confirm that behavior with the operator before rehearsal.

Pause at End pauses at the end and Goto targets another cue. Choose the intended result: retain the last frame or return to the background. Prepare the action in a copy and rehearse the combination; do not assume a pause triggers the background.

Label cues so production and the operator can call them without relying on file order. If the running order changes, review target references and repeat the affected calls.

Choose the output feeding the display

Video Output supports displays, compatible Blackmagic devices, NDI and Syphon. It distinguishes duplication from Span Across Displays. Confirm format, canvas, connections and equipment capacity; several outputs do not establish independent programs.

During rehearsal, use destination identification and known movement. Compare the Mac or device output with the final receiver, including aspect ratio, crop and embedded audio if used. Save settings and observations; a correct preview alone does not confirm that path.

When the picture is right but audio reaches the wrong place

Which device receives audio? In Audio Output, check destination, Master Volume and mute. The manual distinguishes multichannel audio from multiple tracks. Record the file and channels actually received.

Does only one cue fail? Its preferences can override general volume and routing. Compare the affected cue with a known one without changing the console or normalizing the whole playlist as a diagnostic.

Can’t route the channels separately? Stereo downmix disables that routing; check the discrete channel count in Mitti 2.8. Agree with the audio team which channel feeds each input and test them separately.

Proposed example: opening → holding background → closing

Propose three identified cues: opening with audio, a silent holding background during speakers and a called closing video. For each, record the caller, starting condition, ending action and destination. If the background must remain until a human call, define that state explicitly and test a longer wait than planned.

Check at least: the opening’s ending and agreed return; a pause followed by a fresh closing call; audio level and destination for both videos. Include a rehearsal jump near the end and reopening the playlist. Record observations; a saved copy alone does not prove recovery.

If different displays need simultaneous independent content, describe that requirement before choosing the application. If only the gap between pieces changes, prepare a dedicated still cue rather than extending or altering the approved video.

Sources and rehearsal records

Mitti 2.8.19, Rev.1449 · Playback · Cue Basics · Cue Preferences · Video Output · Audio Output · What’s New in 2.8. Consulted October 23, 2026. Use the proposed scenario to plan a rehearsal with the event media, license and destinations.