Return to README.oc CVS log

Up to [DVB] / dsmcc-mhp-tools

- parse out info from an APPSPEC line as passed to dsmcc-ait

# README file for dsmcc-oc

dsmcc-oc: create an object-carousel.

If you want to include stream- or stream-event objects in the stream,
then you have to mark them accordingly. Stream-objects are recognized
by the execute-bit which has to be set in the bitmask of the executing
user, while stream-events are recognized by the write+execute bits,
which both have to be set.

First, Stream- and Stream-Event objects include a description which
can be provided by the broadcaster, e.g. a short textual description
about e.g. what the object is for.
After that, some information about the referenced stream follow, i.e.
the component-tag identifying the elementary stream associated with
the Stream- or Stream-Event object (hex), the stream-duration in
seconds and milliseconds (decimal) and finally the data-types included
with the referenced stream, i.e. a boolean-triple whch stands for
(audio,video,data).
Stream-Event objects also include their event-names and event-ids;
there have to be the same number of names as ids - the list of events
starts with an event-name followed by its associated event-id.

For an example how stream- and stream-event objects are formatted
look e.g. at example/teststream resp. example/teststreamevent.

Additionally, if you want to include dummy stream-event-descriptors
in the stream, e.g. for really basic testing, pass the '-ste' option
to the encoder (this puts in descriptors referring to all event-ids
described by all stream-event-objects included within the object-
carousel twice in the stream: once at the beginning and second at the
end of the stream, whereby the descriptor-version gets incremented.
Otherwise, you can use the other tools to create single descriptors
and put them in real-time into the stream, by your streaming-server.

You can also include references to object in other carousels, i.e.
these references include a lite options profile instead of a biop
profile in their IOR. Such links to external objects are represented
by soft-links. The name of the link itself stands for the object-name
in the current object-carousel, where the destination-path follows a
fixed format:
The relative path to the referenced object in the external carousel
followed by a colon-separeted list including the object-type (which
can be "dir", "fil", "str" or "ste") and the carousel-location of the
external carousel, i.e. carousel-id, original network-id, transport
stream-id and finally the service-id (all in hexadecimal format).

For an example how links to external objects are formatted look
e.g. at example/pictures.

And of course, all files to encode should be readable.

Check 'dsmcc-oc --help'.