13 Dec 2021, 20:04 by jamr...@gmail.com: > > > On 12/13/2021 3:05 PM, Jean-Baptiste Kempf wrote: > >> On Mon, 13 Dec 2021, at 16:25, Michael Niedermayer wrote: >> >>> If you know of any major issues which need to be done before the release do >>> them >>> now. If you know of any issues which are release-blocking list them in a >>> reply >>> here please. >>> >> >> Maybe the audio channel layout would be nice to settle before? >> > > There are two or three requests/blockers, by Nicolas and i think Lynne. > > - The request to have either a string to give custom channels a name, or at > least an opaque pointer per channel that can be used for such purpose. This > has seen opposition from Anton. >
Consensus was reached. A 16-bit opaque identifier, which users can simply use as an index into their own frame opaque structure, if they want, and a 16-bit channel identifier, which would result in a 32-bit structure, which is pretty acceptable. > - The request to allow a channel ID to be present multiple times. This has > seen opposition from Anton and Hendrik (API user), and, if i understood it > correctly, support from Marton. > Consensus was reached here too - keep the current behaviour. On decoding, multiple channels with the same identifier may be present, if the user requested a custom layout, or the codec explicitly stated that the channels carry no meaning. On encoding, document that encoders are allowed to drop undefined/user-defined channels, unless the codec is capable of this (maybe add a codec flag to signal this). _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
