IETF Logo Mail Archive

Re: [codec] Ambisonics in an Ogg Opus Container

Monty Montgomery <xiphmont@gmail.com> Fri, 27 May 2016 19:56 UTC

Return-Path: <xiphmont@gmail.com>
X-Original-To: codec@ietfa.amsl.com
Delivered-To: codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91A1612D625 for <codec@ietfa.amsl.com>; Fri, 27 May 2016 12:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HyrY77WueBBJ for <codec@ietfa.amsl.com>; Fri, 27 May 2016 12:56:01 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18F5612D0AB for <codec@ietf.org>; Fri, 27 May 2016 12:56:00 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id 190so78455166iow.1 for <codec@ietf.org>; Fri, 27 May 2016 12:56:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=nkwRiGBLxqQ31zlCQFBFtVrGHtg7Djt7x2BMzSvUc/M=; b=Y/x+YN3KNdxVaXzIo2t8rvVlKpMseOAk8I6C/PDAoGtNg+4tTBYHUQLrsHTmU61qBj +i5szm46hSCejjk5Oelfz0m1zyYbbHM7Q9MJyPq/4/iNzQi9xI5F07BivFXHNJukgZsk N+kLpFlp01QbcYEHYjnBasjDUcQzbg/Ezrbfd3f3aQFCakAbbe1eg2VJ7L7ZClZd/o5C TyfE9p246d8fg0SB2E0dFb+obRzUnSgCDUM/PPOoxI3roPSUvQZ2IQDcZN3aygteyNKP iZEMBzosUOuiU2o4eNVkGDEOIliagfD9R7Sh2DLWHHFcg6uaDMTEJt/aUGSBy+pfa3qq bfiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=nkwRiGBLxqQ31zlCQFBFtVrGHtg7Djt7x2BMzSvUc/M=; b=jYk8NWjvSCDIIESVGwBagcCv4ZepKmoNSy/y8vwwNqjGmsX/MgtunQ0xqirK/OYzwW vfiKHFS+Vp3Qwo+vY0K8w06n5j0s1C3MCnssMywLyLzmFqKsowF2YwuPZ7s3N2slpfXa 8lJ6Za4FBVzfSyMzSKcwJJGcGTBZYUKhyvny5KpoAwnWdaMQxnvHOjRvGd9ig4ZMgcYg d8gaao9DWAMZVU7SwX7sTzby5nZsZszPKrZ6WVPxySTNpolsCMhRune0weMPi2Z0htRY pTZAlbvDBktMt8VBobIg0KO3W818kMeHeIe4gIeODffTBsS0nB6JXc2yUkDc1kbrOLHW ruqg==
X-Gm-Message-State: ALyK8tKxlpaLSesusqilqHmq9+viqw6zjtyjCrk66G4byq736Hodf2Il56gtyjwX4MUBxeXHqLbuv6FDHkISig==
MIME-Version: 1.0
X-Received: by 10.107.152.82 with SMTP id a79mr14473476ioe.46.1464378959434; Fri, 27 May 2016 12:55:59 -0700 (PDT)
Received: by 10.107.11.164 with HTTP; Fri, 27 May 2016 12:55:59 -0700 (PDT)
In-Reply-To: <CABcu6-jN2gC0FRm5Vu6CmT5=yMdJr1WSaJJ_-FOXffw8bWjc_g@mail.gmail.com>
References: <CABcu6-jN2gC0FRm5Vu6CmT5=yMdJr1WSaJJ_-FOXffw8bWjc_g@mail.gmail.com>
Date: Fri, 27 May 2016 15:55:59 -0400
Message-ID: <CACrD=+8uDhoR77o8GHUKwp4N2sxndNGoOj6PFFvELdcx6cFbuA@mail.gmail.com>
From: Monty Montgomery <xiphmont@gmail.com>
To: Michael Graczyk <mgraczyk@google.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/codec/AhJUuuwSB408WzGAkJk7KY3vp_A>
Cc: "video-codec@ietf.org" <codec@ietf.org>
Subject: Re: [codec] Ambisonics in an Ogg Opus Container
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 27 May 2016 19:56:03 -0000

I also fully support this Ambisonics work, and am very happy with the
progress progress thusfar.

There'd been interest in Ambisonics in Vorbis for a long time (more
than 15 years at this point), but there hadn't been a group that was
qualified in practical Ambisonics, motivated to do the work, and had
the time resources available for a long-term investment.  It's natural
this interest would move forward to Opus, and I'm glad to see it
finally sink root.

Cheers,
Monty

On Fri, May 27, 2016 at 4:52 AM, Michael Graczyk <mgraczyk@google.com> wrote:
> Hello,
>
> I work at Google on spatial audio, 3D audio for virtual reality. We
> recently launched spatial audio in 360 videos on Youtube [1] and are
> currently streaming ambisonics [2] to Android devices on supported
> platforms. We will launch on more platforms in the near future.
>
> We plan to use the Opus codec in an Ogg stream on Youtube. We believe
> that the robust quality and relatively low complexity of Opus makes
> the codec well suited for ambisonics and VR in general. In order to
> ensure consistency in how spatial audio is stored and streamed with
> Opus, we have written a draft specification for encapsulating
> ambisonics in an Ogg Opus stream:
>
> https://datatracker.ietf.org/doc/draft-graczyk-codec-ambisonics/
>
> We hope that establishing a standard Ogg Opus ambisonics format will
> help organizations work together and interoperate. I look forward to
> your thoughts and comments on the draft document.
>
> [1] https://support.google.com/youtube/answer/6395969?hl=en
> [2] https://en.wikipedia.org/wiki/Ambisonics
>
> --
>
> Thanks,
> Michael Graczyk
>
> _______________________________________________
> codec mailing list
> codec@ietf.org
> https://www.ietf.org/mailman/listinfo/codec

v2.23.0 | Report a Bug | By Email