Hope you'll be more active on the mailing list when you back home ;)
Aside question to you. To date time stretching, required by JB was done by the means, outside to a codec. But I feel that codec should have enough information about the speech in the frame to stretch it with high quality. Is that correct feeling? I guess that should be correct for some codecs (like CELP-based), but not for the others (like G.711). Could you comment on this? Avoiding extra CPU-cycles, required for time-stretching would be a very nice (if not a killer) feature for The Ultimate Internet Codec.
PS What is the mood of you, Jason and IESG - should this WG work on developing a codec or rather recommending one of existing or developing codecs?
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2009-08-02 06:22 pm (UTC)Aside question to you. To date time stretching, required by JB was done by the means, outside to a codec. But I feel that codec should have enough information about the speech in the frame to stretch it with high quality. Is that correct feeling? I guess that should be correct for some codecs (like CELP-based), but not for the others (like G.711). Could you comment on this?
Avoiding extra CPU-cycles, required for time-stretching would be a very nice (if not a killer) feature for The Ultimate Internet Codec.
PS What is the mood of you, Jason and IESG - should this WG work on developing a codec or rather recommending one of existing or developing codecs?