> This is the reason the changes below to 7845 are necessary. I.e.,
> not interpreting as channel mapping family 255, and instead “A
> demuxer implementation encountering a 'channel mapping family'
> value that it does not recognize SHOULD NOT attempt to decode the
> packets“
>
> Sorry, I'm not following. Is your point that previously it would have
> misdecoded it and now it will just refuse to play? That's a reasonable
> design choice, but it seems like it was always present in this design,
> so why does it need to change?
Basically, RFC 7845 didn't consider the possibility of new mappings
requiring some kind of transformation (in the case of family 3, a matrix
multiply) between the Opus streams and what the decoder needs to output.
Once you consider that, then it makes no sense to output the "raw"
decoded streams as if it were a family 255.
Cheers,
Jean-Marc
_______________________________________________
codec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/codec
