Anton Khirnov (12021-12-09): > It is not possible for them to behave "like that", because our current > channel layout API does not support duplicated channels at all.
They behave like in the sense they output channels from several sources in a single stream of AVFrame. They could not properly label it with a layout. The new API should allow to enhance that, not break it utterly. > I disagree. Technical limitations that were overcome 10 years ago should > not guide new API design. In the case of amerge, it was not a technical limitation, merging several streams into one so that they can be handled by single-stream filters is 100% part of the design. I suspect devices that capture several independent channels are designed that way intentionally too, possibly to reduce the risk of desynchronization. > If you insist then we can have a TC vote about this. Please, the TC is for when discussion has failed. Let us see what arguments other developers bring to the discussion first. I observe that about the ability to attach an arbitrary string label to any channel, Lynne was with me for independent reasons. And of course, if it comes to the TC, since you are a member yourself, I expect you to recuse yourself from the proceedings on this question, as you would be judge and party. Regards, -- Nicolas George
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".
