		Magnifying Glass Sample
	Author: Jean Le Feuvre (jean@avipix.com)

This file describes the media data organisation of the MP4 file produced.
The scene is a presentation with:
2 JPEGs (button.jpg and sky.jpg)
1 AAC stream (bashung.aac - sorry i'm french!)
1 H263 stream (Angelika.h263)
1 OD stream
1 BIFS stream

The video stream is played twice (first time at 0 s, second at 20 s)

A - BATCH files:
1_scene_flat.bat:	produces a flat MP4 file, without any interleaving
2_scene_inter.bat:	produces an interleaved MP4 file
3_scene_dump.bat:	dumps MP4 file info (and track at prompt if desired)


B - URL example
In the script file:
{
  objectDescriptorID  2
  esDescr [
    {
      ES_ID 20
      muxInfo {
       streamFormat JPEG
       GroupID 1
      }
      URLString ..\streams\sky.jpg
      [ ... ]
    }
  ]
}

The file name is not specified in the MuxInfo structure but n the URLString field.
This means that the stream SKY.JPG will not be contained in the MP4 file, but only referenced.
This allows storage of MetaData (timing, size and location) in an MP4 File without changing the 
originla media container (in our case, sky.jpg)

C - Timimg example:
In the script file
{
  objectDescriptorID  10
  esDescr [
    {
      ES_ID 40
      muxInfo {
       fileName ..\streams\children.h263
       streamFormat H263
       streamAttr "5"
       GroupID 3
      }
      OCR_ES_ID 5
      [ ... ]
    }
  ]
}

The OCR_ES_ID of this stream is set to 5 (our AAC stream ID). This will create a 'sync' 
dependancy on track 5 (in MP4 language, adds a TREF of type 'sync' and value 5
(works the same way for streamDependancy, field DependsOn_ES_ID)


D - Group Example

In the script file:
GroupID 1: sky.jpg (the background)
GroupID 1: button.jpg (the magnifying glass icon)
GroupID 2: BIFS stream
GroupID 2: OD stream
GroupID 3: Video stream
GroupID 3: Audio stream

This means that the interleaving will be the following:
- First media written in the MDAT: sky and button (eg, the "interface" data is written 
before the resources (BIFS and OD) that will use it)
- Then the MPEG4 resources BIFS and OD
- And finally the "BIG" media data (video and audio)

Therefore, when the file is downloaded, the two JPGs are present in the terminal 
BEFORE the BIFS and OD are downloaded, making sure that the interface will load with
the pictures (if the player supports that, of course!).
And once BIFS and OD are present (interface loaded), the audio/video are downloaded 
and viewed on the fly (interleaving of audio/video).
