-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 05/27/2016 01:45 PM, Timothy B. Terriberry wrote:
> With my chair hat on: I think it would be helpful for us to gage
> the level of interest if people would comment on the list if they
> think this is something useful for this group to work on.
I support this work. I believe it is useful and am willing to do
reviews and also contribute directly if necessary.
> For n = 0, (1 + n)^2 == 1, but that's not on your explicit list.
> Was the intention here to exclude mono as redundant with other
> channel mapping families? We didn't do that for channel mapping
> family 1 (since, for example, the presence of an explicit channel
> mapping table allows you to extract a single channel from an
> already-encoded coupled stream, which is not possible with channel
> mapping family 0). But if you did intend to exclude mono, you
> should explicitly say why, and adjust the range of n.
I personally don't think 1-channel ambisonics should be allowed
(unless there's a good reason I missed). We might want to say that
encoders MUST NOT create them, but decoders SHOULD handle them as if
they were regular mono files.
>> Updates: 7845 (if approved)
>
> Does this actually update RFC7845? I think the intent was to allow
> updates to the channel mapping registry to be done without an
> explicit update of 7845, since it's possible it might not even be
> done with an IETF RFC (e.g., if there were some broadcast-specific
> standard done at a different standards body).
I agree, I'm pretty sure we don't want the "Updates: 7845" line.
Cheers,
Jean-Marc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXSIswAAoJEJ6/8sItn9q9aUcIAJjr+jYS++C9mxPKbUV0oVgg
Ahce4hi02bW4Fiopqdk4A4h2SRwO1oWDlH2TUiDHspcx/BhYxuru41rqRRcfd6Em
pe75f3jwyVCRtlsqfHIDZOcECei1uSPuowa1rqv0sB1zu4wzgr/n/ikpM+YwVEiK
mBFLIHQNMfo88n9xYhwFPAB3g8ystNKpgi7mzvp9Nm2kMYXe/She+06PwGm+HiqJ
HNaWWqLUXxMFRNMy2R3ToCYhW+JlpQEdgy+v9fhF+0fN1R36BZP1EUZUIe+Q1Jzk
1fhTPF2fFD6SWOCEOgDaPvjgrXryauWKKysz/BGrIYOIg1zYbqPFqXPsKO4Fj1Y=
=dFEK
-----END PGP SIGNATURE-----
_______________________________________________
codec mailing list
codec@ietf.org
https://www.ietf.org/mailman/listinfo/codec
