Welcome to Mitti! This article is an introduction to Mitti's basic principles and user interface.
When you open Mitti and create a new project, it will present you an empty Playlist with most of the controls disabled, since there are no Cues yet. Mitti automatically disabled non-relevant controls. So lets check out the major parts of the user interface now.
Mitti's Main Window is divided into three 3 parts:
Located at the left side of Mitti's Main Window, you can find the Transport Controls, the Main Timecode Field on the top, below that the Playhead Slider.
The stripped area is the Playlist: this is where your Cues will be displayed.
Located at the right side of Mitti's Main Window, the Preview displays the current Cue at the current timeline location.
The Preview Window also displays the Cue Time Overlays, which you can configure in Preferences-Overlays and toggle on/off from the View menu.
Located at the bottom of Mitti's Main Window, you can find the Fullscreen Indicator and the Main Fader on the left side, which controls the overall opacity of the Playlist.
With the "Eye" icon on it's left side, you can trigger Auto Fading, which will fade-in or -out the Playlist during the Fade Time specified in Playlist settings. If you hold down the ALT key while clicking on this button, it will toggle the opacity on or off.
On the right side you can show or hide the Playlist & Transport or the Preview views.
Time in Mitti represented as SMPTE time, so it always using the hh:mm:ss:ff format. The Playlist can be, and must be configured in the Playlist Preferences to use one of the following frame rates: 24, 25, 30/29.97 - even if your movies has a different frame rate.
Mitti's internal timeline must be consecutive, which means Cues will be always consecutive, so no empty time are allowed between them. Mitti will manage that for you, so no things to do on your side. Whenever you are creating a new Cue, that will be added after the last one.
You can set the Start Time of the Playlist as well, and this setting will be also applied as the timecode offset if Mitti is timecode slaved.
You can also specify the duration of Cue Fades, non-movie Cue duration as well as default Cue states.
There are multiple ways to create Cues in Mitti. Video, Still Image and Audio Cues can be created by simply drag-n-dropping files from Finder to Mitti's Playlist view, while Syphon, Camera and NDI Cues types are only accessible from the File Menu. Once you created a Cue it will be added to the Playlist.
Once you have multiple Cues you can set the Current Cue, and also remove or re-order Cues when needed.
Each Cue has its own Preferences, such as Color Controls, Source, Video Effect, Transition and so on.
You can read about Cues in-depth in the Cues Section.
Once you have your Cues set up you can start playback, either using Mitti's Standalone mode or even MTC/LTC timecode driven - these modes are available from the Playlist Menu.
During Playback, you cannot create new Cues from the File menu - but drag & drop from Finder still works - or removing existing ones.
Standalone Playback means Mitti will use its internal clock to manage playback. There is 1 additional option available when you are using this mode - either by the icon next to the Play button or from the Playlist... menu:
You can start and pause playback with
SPACEBAR , while hitting
ENTER will switch to and play the selected Cue.
With the JUMP command you can switch to a specific Cue, and you can define what Mitti should do after that: either stand by, or start playback of that Cue.
You can define the following behaviours in the Playlist Preferences:
The following JUMP commands are available from the Playlist... menu:
In case you need to "kill" the outgoing signal, there is an action called Panic - available from the Playlist... menu or by hitting -
The playback can be slaved to an MTC or LTC timecode source, and there is an article dedicated to that topic, you can find it here.
Mitti supports video output on multiple displays, even with Corner Pinning and Edge Blending applied - you can read more about this in the Video Output section.
Still stuck? How can we help?