This document is a draft of the Menu system that will be the default one in
As it will just be composed of a Control Track, it will be seen as a “codec” and could be
replaced later by something else if needed.
A menu is like what you see on DVDs, when you have some screens to select the audio format, subtitles or scene selection.
What we’ll try to have is a system that can do almost everything done on a DVD, or more, or better, or drop the unused features if necessary.
As the name suggests, a Control Track is a track that can control the playback of the file
and/or all the playback features. To make it as simple as possible for
the Control Track will just give orders to the
Matroska Player and get the actions
associated with the highlights/hotspots.
A highlight is basically a rectangle/key associated with an action UID. When that
rectangle/key is activated, the
Matroska Player send the UID of the action to the
Control Track handler (codec). The fact that it can also be a key means that even for
audio only files, a keyboard shortcut or button panel could be used for menus.
But in that case, the hotspot will have to be associated with a name to display.
This highlight is sent from the Control Track to the
Matroska Player. Then the
Matroska Player has to handle that highlight until it’s deactivated; see (#playback-features).
The highlight contains a UID of the action, a displayable name (UTF-8), an associated key (list of keys to be defined, probably up/down/left/right/select), a screen position/range and an image to display. The image will be displayed either when the user place the mouse over the rectangle (or any other shape), or when an option of the screen is selected (not activated). There could be a second image used when the option is activated. And there could be a third image that can serve as background. This way you could have a still image (like in some DVDs) for the menu and behind that image blank video (small bitrate).
When a highlight is activated by the user, the
Matroska Player has to send the UID of
the action to the Control Track. Then the Control Track codec will handle the action
and possibly give new orders to the
The format used for storing images SHOULD be extensible. For the moment we’ll use PNG and BMP, both with alpha channel.
All the following features will be sent from the Control Track to the
Matroska Player :
- Jump to chapter (UID, prev, next, number)
- Disable all tracks of a kind (audio, video, subtitle)
- Enable track UID (the kind doesn’t matter)
- Define/Disable a highlight
- Enable/Disable jumping
- Enable/Disable track selection of a kind
- Select Edition ID (see chapters)
- Pause playback
- Stop playback
- Enable/Disable a Chapter UID
- Hide/Unhide a Chapter UID
All the actions will be written in a normal Matroska track, with a timestamp. A “Menu Frame” SHOULD be able to contain more that one action/highlight for a given timestamp. (to be determined, EBML format structure)
Matroska Players might not support the control track. That mean they will play
the active/looped parts as part of the data. So I suggest putting the active/looped
parts of a movie at the end of a movie. When a Menu-aware
Matroska Player encounter
the default Control Track of a
Matroska file, the first order SHOULD be to jump at
the start of the active/looped part of the movie.
Matroska Source file -> Control Track <-> Player. -> other tracks -> rendered