Displaying 2 results from an estimated 2 matches for "ogg_channel_".
2005 Nov 19
2
OggPCM2: channel map
> True, but remember that the channel map type implied the number of
> entries in the table, and also that in this organization you'll always
> number the logical channels consequtively since each logical channel
> indeed corresponds to an index into the array. If the channel map type
> says it's a map for 5.1, there will only be 6 slots in the table no
> matter how
2005 Nov 19
0
OggPCM2: channel map
...hink I understand the confusion here, but correct me if I'm wrong. What
we're proposing is to define the channel map for each supported channel
group type. The array syntax I used in my last post probably added to the
confusion - look at it again but without using the assigned values to the
OGG_CHANNEL_* text. A couple examples:
Packet 1:
channel_type = OGG_CHANNEL_MAP_5_1
channel_map [0 = OGG_CHANNEL_FRONT_LEFT] = 1
channel_map [1 = OGG_CHANNEL_FRONT_CENTER] = 2
channel_map [2 = OGG_CHANNEL_FRONT_RIGHT] = 3
Packet 2:
channel_type = OGG_CHANNEL_MAP_STEREO
channel_map [0 = OGG_CHANNEL_FRONT_LEFT]...