Re: [codec] Next Steps for WG

"Christian Hoene" <hoene@uni-tuebingen.de> Fri, 14 January 2011 08:24 UTC

Return-Path: <hoene@uni-tuebingen.de>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4147F3A6C58 for <codec@core3.amsl.com>; Fri, 14 Jan 2011 00:24:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sM0Va-OT2n9V for <codec@core3.amsl.com>; Fri, 14 Jan 2011 00:24:40 -0800 (PST)
Received: from mx06.uni-tuebingen.de (mx06.uni-tuebingen.de [134.2.3.3]) by core3.amsl.com (Postfix) with ESMTP id B17A93A6AB9 for <codec@ietf.org>; Fri, 14 Jan 2011 00:24:39 -0800 (PST)
Received: from hoeneT60 (u-173-c044.cs.uni-tuebingen.de [134.2.173.44]) (authenticated bits=0) by mx06.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id p0E8R1xx022878 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 14 Jan 2011 09:27:02 +0100
From: Christian Hoene <hoene@uni-tuebingen.de>
To: 'Jean-Marc Valin' <jmvalin@jmvalin.ca>, 'Roman Shpount' <roman@telurix.com>
References: <6963A8AD-F30C-4688-909A-68D4FEAF91C2@cisco.com> <AANLkTi=wT52U2ceJcfTPih-UY=NBWykmZE=3QicVtN2N@mail.gmail.com> <4D2FBA0F.3040904@jmvalin.ca>
In-Reply-To: <4D2FBA0F.3040904@jmvalin.ca>
Date: Fri, 14 Jan 2011 09:27:02 +0100
Organization: Universitat Tubingen
Message-ID: <006601cbb3c4$d2cd6870$78683950$@uni-tuebingen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJktPotNG8jvenizKbKD0XJxNxZmgJCrN5+AbafNDqSflScYA==
Content-Language: de
X-AntiVirus: NOT checked by Avira MailGate (version: 3.0.0-4; host: mx06)
Cc: codec@ietf.org
Subject: Re: [codec] Next Steps for WG
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2011 08:24:41 -0000

The easiest way to mix the multiple streams is to take advantage of the DTX
feature, which is available in the Silk and hybrid mode. However, I am not
aware whether DTX or VAD is supported in the CELT mode.

Christian

> -----Original Message-----
> From: codec-bounces@ietf.org [mailto:codec-bounces@ietf.org] On Behalf
> Of Jean-Marc Valin
> Sent: Friday, January 14, 2011 3:51 AM
> To: Roman Shpount
> Cc: codec@ietf.org
> Subject: Re: [codec] Next Steps for WG
> 
> Hi Roman,
> 
> We believe that we meet all requirements that were identified. As for
mixing
> multiple encoded streams, that was marked as desirable in the draft
because
> it's very hard to achieve without sacrificing efficiency.
> To some extent, if you constrain the Opus encoder to a subset of the
> available options (CELT only without short blocks or post-filter), then
you can
> create streams that can be mixed at roughly half the normal complexity. I
> think that's about as much as we can do here.
> 
> Cheers,
> 
> 	Jean-Marc
> 
> On 11-01-13 07:34 PM, Roman Shpount wrote:
> > Just out of curiosity, have the OPUS codec been review against the
> > list of requirements that we put together?
> >
> > In particular, I raised the requirement that multiple encoded streams
> > form different sources can be efficiently combined. Is it possible
> > with OPUS? If it is, then how?
> > _____________________________
> > Roman Shpount - www.telurix.com <http://www.telurix.com>
> >
> >
> > On Thu, Jan 13, 2011 at 5:29 PM, Cullen Jennings <fluffy@cisco.com
> > <mailto:fluffy@cisco.com>> wrote:
> >
> >
> >     The OPUS draft authors believe the bitstream for OPUS will be ready
> >     to be "frozen" by the end of the month. At that point we plan to
> >     spend the following month testing and, baring any surprises, will
> >     likely go to WGLC after that.
> >
> >     There has been some questions about what "frozen" means in IETF
> >     context. The bitstream could change any time up to when the IESG
> >     approves it which is after Working Group Last call and after IETF
> >     Last Call so there is no guarantee that nothing will change but ...
> >       by "frozen" we mean that we believe no changes are needed and
> >     don't plan to make changes unless some significant problem is found.
> >
> >     Thanks,
> >     Cullen, Jonathan, and Mike
> >
> >
> >     _______________________________________________
> >     codec mailing list
> >     codec@ietf.org <mailto:codec@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/codec
> >
> >
> >
> >
> > _______________________________________________
> > codec mailing list
> > codec@ietf.org
> > https://www.ietf.org/mailman/listinfo/codec
> _______________________________________________
> codec mailing list
> codec@ietf.org
> https://www.ietf.org/mailman/listinfo/codec