James Almer (12021-12-13):
> To achieve this you don't need the same AVChannel value to appear several
> times in the same layout. You have INT_MAX values available, so just assign
> one to each of these you mentioned. No need for an abstract value "user
> defined" that would then show up several times in a layout. Oboe can be 65,
> piano can be 66.
> Also, each channel is meant to map to a speaker in a different physical
> location. If your idea is to have oboe and piano play through the same

The idea is that if some filters takes the oboe and piano from a single
stream and extracts them into two streams, then the left and right will
automatically be correctly marked left and right in the extracted
streams.

> speaker, then you're thinking filtering, and that sounds beyond the scope of
> a channel layout API.

Making sure existing filters and devices can flag the channel layout
they need, which they could not because of the limitation of the current
API, seems 100% in scope to me.

What is your definition of the scope of a channel layout API? I hope it
is not "we did it that way, anything it cannot do is beyond the scope".

Regards,

-- 
  Nicolas George

Attachment: signature.asc
Description: PGP signature

_______________________________________________
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".

Reply via email to