-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Tina,

Thanks for the feedback. I'll make the changes.

> * Section 6. Can you describe how to remove the 180-degree phase
> shift?

Not sure what part of my explanation isn't clear. What happens is that
the encoder has a per-band "inversion flag" it can use for intensity
stereo and when the decoder sees that flag, it flips the sign of the
right channel to make it 180-degrees out of phase with the left
channel. The proposal is simply to make the inversion step optional on
the decoder side, even when the flag is set by the encoder. Any
suggestion on how to fix the current text?

Cheers,

        Jean-Marc

> Thanks, Tina le Grand.
> 
> 
> 
> On Thu, Aug 1, 2013 at 5:18 PM, Timothy B. Terriberry
> <[email protected] <mailto:[email protected]>> wrote:
> 
> Jean-Marc Valin wrote:
> 
> See these proposed fixes to the Opus RFC. These are minor changes
> to the normative part of the reference implementation.
> 
> 
> With my chair hat on:
> 
> Although JDR originally said we would handle updates to RFC 6716 
> through the normal errata process [1], after conferring with our 
> ADs, we decided to do them via a new draft, so that there was no 
> question about overriding working group consensus.
> 
> To that end, we'd like to run a consensus call to add a milestone 
> for doing these updates. It would be helpful to have reviews of
> this document before doing that call. I propose we allow a month
> (until Sep. 1) for such reviews, and then run the call.
> 
> 
> [1] 
> https://datatracker.ietf.org/__documents/LIAISON/liaison-__2012-09-21-codec-isoiec-jtc-__1sc-29wg-11-liaison-from-ietf-__codec-working-group-to-isoiec-__regarding-speech-and-audio-__coding-standardization-__attachment-1.pdf
>
> 
<https://datatracker.ietf.org/documents/LIAISON/liaison-2012-09-21-codec-isoiec-jtc-1sc-29wg-11-liaison-from-ietf-codec-working-group-to-isoiec-regarding-speech-and-audio-coding-standardization-attachment-1.pdf>
> 
> _________________________________________________ codec mailing
> list [email protected] <mailto:[email protected]> 
> https://www.ietf.org/mailman/__listinfo/codec 
> <https://www.ietf.org/mailman/listinfo/codec>
> 
> 
> 
> 
> _______________________________________________ codec mailing list 
> [email protected] https://www.ietf.org/mailman/listinfo/codec
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSKiXYAAoJEJ6/8sItn9q9lxsH/RqmAGCEoVvPedtlFsXQ24h7
rOtg7VREBlKaEanpmq0atSjSwz+chbNxIkqkjAKRiLQTWpWxR5r98XxZJNM3PAZr
v/O4unDTG0KvIzu8mpqOsetsCGzfnMKxp3K1yxTx0vB6Bo0WNSNLK3GSqPX98ofC
XG1jt2KztKolnvOUiB99X2HEjRook0igQZb1WyEGAXsvws0tYTfmetOTg5fEcgKu
mLnzpTVygDqu1xEPtZFbBusKodzu4hwwzHgTrVIkeHLFHXs7Fwbwc7db5+k1K+Ni
iFT/JGIcXL6ZQ0TPXBmzQJ429NkVtLzH2BqewOSFQiGKqrij42AfctZIdg1uPQM=
=up2q
-----END PGP SIGNATURE-----
_______________________________________________
codec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/codec

Reply via email to