Return to README.oc CVS log

Up to [DVB] / dsmcc-mhp-tools

Annotation of dsmcc-mhp-tools/README.oc, revision 1.2

1.1       mass        1: # README file for dsmcc-oc
                      2: 
                      3: dsmcc-oc: create an object-carousel.
                      4: 
                      5: If you want to include stream- or stream-event objects in the stream,
                      6: then you have to mark them accordingly. Stream-objects are recognized
                      7: by the execute-bit which has to be set in the bitmask of the executing
                      8: user, while stream-events are recognized by the write+execute bits,
                      9: which both have to be set.
                     10: 
1.2     ! mass       11: First, Stream- and Stream-Event objects include a description which
        !            12: can be provided by the broadcaster, e.g. a short textual description
        !            13: about e.g. what the object is for.
        !            14: After that, some information about the referenced stream follow, i.e.
        !            15: the component-tag identifying the elementary stream associated with
        !            16: the Stream- or Stream-Event object (hex), the stream-duration in
        !            17: seconds and milliseconds (decimal) and finally the data-types included
        !            18: with the referenced stream, i.e. a permutation of (audio,video,data).
        !            19: Stream-Event objects also include their event-names and event-ids;
        !            20: there have to be the same number of names as ids - the list of events
        !            21: starts with an event-name followed by its associated event-id.
        !            22: 
1.1       mass       23: For an example how stream- and stream-event objects are formatted
                     24: look e.g. at example/teststream resp. example/teststreamevent.
                     25: 
                     26: Additionally, if you want to include dummy stream-event-descriptors
                     27: in the stream, e.g. for really basic testing, pass the '-ste' option
                     28: to the encoder (this puts in descriptors referring to all event-ids
                     29: described by all stream-event-objects included within the object-
                     30: carousel twice in the stream: once at the beginning and second at the
                     31: end of the stream, whereby the descriptor-version gets incremented.
                     32: Otherwise, you can use the other tools to create single descriptors
                     33: and put them in real-time into the stream, by your streaming-server.
                     34: 
                     35: You can also include references to object in other carousels, i.e.
                     36: these references include a lite options profile instead of a biop
                     37: profile in their IOR. Such links to external objects are represented
                     38: by soft-links. The name of the link itself stands for the object-name
                     39: in the current object-carousel, where the destination-path follows a
                     40: fixed format:
                     41: The relative path to the referenced object in the external carousel
                     42: followed by a colon-separeted list including the object-type (which
                     43: can be "dir", "fil", "str" or "ste") and the carousel-location of the
                     44: external carousel, i.e. carousel-id, original network-id, transport
                     45: stream-id and finally the service-id (all in hexadecimal format).
                     46: 
                     47: For an example how links to external objects are formatted look
                     48: e.g. at example/pictures.
                     49: 
                     50: And of course, all files to encode should be readable.
                     51: 
                     52: Check 'dsmcc-oc --help'.