Subject: Re: Menu Structure
Newsgroups: gmane.comp.multimedia.matroska.devel
Date: 2003-03-13 06:09:32 GMT (6 years, 16 weeks, 3 days, 3 hours and 14 minutes ago)
I had a few ideas about requirements for a scripting language. 1. The control track needs to allow for some simple scripting such as: GotoTimecode xx:xx.xxx GotoChapter x SetAudioTrack x 2. The control track might allow for some more complicated scripting such as: if then while for 3. And possible some player controls such as: Play Pause Mute/unMute Next Chapter/Track SkipToTimecode xx:xx.xxx And some ideas about how this could be implemented. 1. Use XML to store the commands so that multiple scripts can be stored in parallel, and they could all be aligned by timecodes. 2. If the scripts can be stored in parallel, and are activated by timcodes, then you could store a portion of the scripts, that should run at a timecode, in a regular block (ala USF). 3. Store the XML as EBML. You would save a few bytes, and we're using EBML/XML for everything else so its not like anything extra would need to be coded. 4. Again, this should be outside of the container specs. And really, it should be outside of the menu specs too. The menu and control track should be able to operate completely independantly of each other, however, there should be a few instructions in both to activate some portions of the other. http://www.matroska.org