DOCSLIB.ORG

High Dynamic Range in AV1

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
High Dynamic Range in AV1 High Dynamic Range in AV1 Matt Frost Chrome Media Alan Chalmers University of Warwick & trueDR IABM Copyright 2018 www.theiabm.org @THEIABM Matt Frost Director --Product AV1 Management Chrome Media At Google IBC 2018 IABM Copyright 2018 www.theiabm.org @THEIABM Open Codecs At Google IBC 2018 IABM Copyright 2018 www.theiabm.org @THEIABM IBC 2018 Why Codecs? IABM Copyright 2018 www.theiabm.org @THEIABM Unlock The World IBC 2018 IABM Copyright 2018 www.theiabm.org @THEIABM Unlock The Future IBC 2018 IABM Copyright 2018 www.theiabm.org @THEIABM Track Record: VP9 + YouTube +25% +20% +15% +10% +5% +2% YouTube VP9 watch time gains vs. H.264 IABM Copyright 2018 www.theiabm.org @THEIABM Who is Founded in Fall 2015, 36 companies came together to develop next generationIBC codecs2018 for the web. IABM Copyright 2018 www.theiabm.org @THEIABM Goals for Video Codec Open Deploy Widely & for the Web source & Quickly With state of royalty- Developed faster the art free than standards compression Grounded bodies and efficiency in the supported across WebM platforms philosophy Logo placeholder IBC 2018 IABM Copyright 2018 www.theiabm.org @THEIABM VOD Services Member companies with video-on-demand streaming consumer products & services.IBC 2018 IABM Copyright 2018 www.theiabm.org @THEIABM Live/RTC Services Member companies with live streaming and/or real time communication consumerIBC products2018 & services. IABM Copyright 2018 www.theiabm.org @THEIABM Results: IABM Copyright 2018 www.theiabm.org @THEIABM Results: IABM Copyright 2018 www.theiabm.org @THEIABM Results: IABM Copyright 2018 www.theiabm.org @THEIABM Results: IABM Copyright 2018 www.theiabm.org @THEIABM Results: IABM Copyright 2018 www.theiabm.org @THEIABM Where We Are 1 2 3 4 5 Tools Codebase Spec Support in SoC Selected frozen Published Chrome Hardware (Complete (Complete (Complete (Q3 2018) (2020) d) d) d) IBC 2018 IABM Copyright 2018 www.theiabm.org @THEIABM Google is Committed to AV1 IBC 2018 IABM Copyright 2018 www.theiabm.org @THEIABM Demo • Download Chrome Canary / Dev Channel ●"Enable AV1 Video Decoding" to "Enabled" in chrome://flags IBC 2018 ●Playback IABM Copyright 2018 www.theiabm.org @THEIABM More Check out our partners’ demos here at IBC2018 Demos! BOOTH SU10725MR BOOTH SU3710 BOOTH SU9901 IBC 2018 IABM Copyright 2018 www.theiabm.org @THEIABM Learn ● Project Site: More https://aomedia.org ● Source code: https://aomedia.googleso urce.com/ ● Bitstream specification: https://aomedia.org/av1- bitstream-and-decoding- IBC 2018 process-specification/ IABM Copyright 2018 www.theiabm.org @THEIABM High Dynamic Range in AV1 An Alternative Future for HDR IABM Copyright 2018 www.theiabm.org @THEIABM IABM Copyright 2018 www.theiabm.org @THEIABM The real world Very wide range of lighting × Peak luminance is NOT 1,000 or even 10,000nits Need to be “scene-referred” A single candle lit in dark a room has a dynamic range 16.8 million to 1 (24 stops) IABM Copyright 2018 www.theiabm.org @THEIABM IABM Copyright 2018 www.theiabm.org @THEIABM What we did Added existing HLG and PQ (HDR10) New HDR methods – scene referred PTF (Gamma) – real-time, on-the-fly adaptive to: . ambient light, creative intent, display luminance Ratnajit – faithfully preserves colour IABM Copyright 2018 www.theiabm.org @THEIABM Why Scene referred HDR viewed under “normal” ambient lighting Future proof IABM Copyright 2018 www.theiabm.org @THEIABM Complexity IABM Copyright 2018 www.theiabm.org @THEIABM Performance IABM Copyright 2018 www.theiabm.org @THEIABM Not in a dark room outside 80,000 lux 4,000nits 10,000nits IABM Copyright 2018 www.theiabm.org @THEIABM trueDR HDR IN AV1 AN ALTERNATIVE FUTURE FOR HDR! Open, royalty-free HDR video coding No more watching HDR in the dark High quality, efficient codecs Wide scope of devices and platforms University of Warwick (UK) | trueDR (UK) | Google (US) | SIM2 (IT) | ORF (A) | Vicomtech (ES) IABM Copyright 2018 www.theiabm.org @THEIABM Enhanced viewing experience IABM Copyright 2018 www.theiabm.org @THEIABM HDR-AV1 is here For TVs, movies … IABM Copyright 2018 www.theiabm.org @THEIABM Even (shortly) for mobile devices … IABM Copyright 2018 www.theiabm.org @THEIABM.
Load more

Recommended publications
  • Microsoft Powerpoint
    Development of Multimedia WebApp on Tizen Platform 1. HTML Multimedia 2. Multimedia Playing with HTML5 Tags (1) HTML5 Video (2) HTML5 Audio (3) HTML Pulg-ins (4) HTML YouTube (5) Accessing Media Streams and Playing (6) Multimedia Contents Mgmt (7) Capturing Images 3. Multimedia Processing Web Device API Multimedia WepApp on Tizen - 1 - 1. HTML Multimedia • What is Multimedia ? − Multimedia comes in many different formats. It can be almost anything you can hear or see. − Examples : Pictures, music, sound, videos, records, films, animations, and more. − Web pages often contain multimedia elements of different types and formats. • Multimedia Formats − Multimedia elements (like sounds or videos) are stored in media files. − The most common way to discover the type of a file, is to look at the file extension. ⇔ When a browser sees the file extension .htm or .html, it will treat the file as an HTML file. ⇔ The .xml extension indicates an XML file, and the .css extension indicates a style sheet file. ⇔ Pictures are recognized by extensions like .gif, .png and .jpg. − Multimedia files also have their own formats and different extensions like: .swf, .wav, .mp3, .mp4, .mpg, .wmv, and .avi. Multimedia WepApp on Tizen - 2 - 2. Multimedia Playing with HTML5 Tags (1) HTML5 Video • Some of the popular video container formats include the following: Audio Video Interleave (.avi) Flash Video (.flv) MPEG 4 (.mp4) Matroska (.mkv) Ogg (.ogv) • Browser Support Multimedia WepApp on Tizen - 3 - • Common Video Format Format File Description .mpg MPEG. Developed by the Moving Pictures Expert Group. The first popular video format on the MPEG .mpeg web.
    [Show full text]
  • Pre-Roll & Mid-Roll Video
    Pre-roll & Mid-roll Video 1/2 THIRD PARTY ALL ASSETS BELOW ARE REQUIRED VAST SPECIFICATIONS TO BE PRESENT IN THE VAST TAG Not available for live stream sponsorships or feature sponsorships. All assets for sponsored Bit rate Codecs accepted Min dimensions Max file size Use cases content must use the "Network 10 Hosted Video In-Stream Ad with Companion" specifications. Mezzanine File 15–30 Mbps H.264 1920x1080 1.7 GB Required for SSAI Aspect ratio Format (High profile) Environments 16:9 Video will auto-scale correctly Frame Rate: 24 :15 – 4.5MB High Codec Constant frame rate only 2,100 kbps H.264 Mezzanine File - .mov +/- 50 kbps (High profile) 1024x576 :30 – 9MB bandwidth (H.264 High Profile) No de-interlacing with :18 – 18MB users no frame blending mp4 (high profile) :15 – 3.5MB Standard asset Remove any pull-down 1,500 kbps H.264 +/- 50 kbps (High profile) 960x540 :30 – 7MB for most users webm (VP8 or VP9) added for broadcast :18 – 14MB and pre roll Duration Audio :15 – 1MB Low 750 kbps H.264 768x432 :30 – 2MB bandwidth Network 10 accepts a variety of length Mezzanine file: 2 Channels only, AAC +/- 50 kbps (High profile) :18 – 4MB users creatives, standards include :6*, :15, :30, Codec, 192 KBPS minimum, 16 or 24 bit Available on :60*, :90*. only, 48 kHz Sample Rate. :15 – 4.5MB High 375 kbps H.264 Any tag submitted must contain creative mp4 assets: 2 Channels only, AAC Codec, +/- 50 kbps (High profile) 640x360 :30 – 9MB bandwidth of all the same length. 192 KBPS minimum, 16 or 24 bit only, 48 :18 – 18MB users kHz Sample Rate.
    [Show full text]
  • Opus, a Free, High-Quality Speech and Audio Codec
    Opus, a free, high-quality speech and audio codec Jean-Marc Valin, Koen Vos, Timothy B. Terriberry, Gregory Maxwell 29 January 2014 Xiph.Org & Mozilla What is Opus? ● New highly-flexible speech and audio codec – Works for most audio applications ● Completely free – Royalty-free licensing – Open-source implementation ● IETF RFC 6716 (Sep. 2012) Xiph.Org & Mozilla Why a New Audio Codec? http://xkcd.com/927/ http://imgs.xkcd.com/comics/standards.png Xiph.Org & Mozilla Why Should You Care? ● Best-in-class performance within a wide range of bitrates and applications ● Adaptability to varying network conditions ● Will be deployed as part of WebRTC ● No licensing costs ● No incompatible flavours Xiph.Org & Mozilla History ● Jan. 2007: SILK project started at Skype ● Nov. 2007: CELT project started ● Mar. 2009: Skype asks IETF to create a WG ● Feb. 2010: WG created ● Jul. 2010: First prototype of SILK+CELT codec ● Dec 2011: Opus surpasses Vorbis and AAC ● Sep. 2012: Opus becomes RFC 6716 ● Dec. 2013: Version 1.1 of libopus released Xiph.Org & Mozilla Applications and Standards (2010) Application Codec VoIP with PSTN AMR-NB Wideband VoIP/videoconference AMR-WB High-quality videoconference G.719 Low-bitrate music streaming HE-AAC High-quality music streaming AAC-LC Low-delay broadcast AAC-ELD Network music performance Xiph.Org & Mozilla Applications and Standards (2013) Application Codec VoIP with PSTN Opus Wideband VoIP/videoconference Opus High-quality videoconference Opus Low-bitrate music streaming Opus High-quality music streaming Opus Low-delay
    [Show full text]
  • Google Chrome Browser Dropping H.264 Support 14 January 2011, by John Messina
    Google Chrome Browser dropping H.264 support 14 January 2011, by John Messina with the codecs already supported by the open Chromium project. Specifically, we are supporting the WebM (VP8) and Theora video codecs, and will consider adding support for other high-quality open codecs in the future. Though H.264 plays an important role in video, as our goal is to enable open innovation, support for the codec will be removed and our resources directed towards completely open codec technologies." Since Google is developing the WebM technology, they can develop a good video standard using open source faster and better than a current standard video player can. The problem with H.264 is that it cost money and On January 11, Google announced that Chrome’s the patents for the technologies in H.264 are held HTML5 video support will change to match codecs by 27 companies, including Apple and Microsoft supported by the open source Chromium project. and controlled by MPEG LA. This makes H.264 Chrome will support the WebM (VP8) and Theora video expensive for content owners and software makers. codecs, and support for the H.264 codec will be removed to allow resources to focus on open codec Since Apple and Microsoft hold some of the technologies. patents for the H.264 technology and make money off the licensing fees, it's in their best interest not to change the technology in their browsers. (PhysOrg.com) -- Google will soon stop supporting There is however concerns that Apple and the H.264 video codec in their Chrome browser Microsoft's lack of support for WebM may impact and will support its own WebM and Ogg Theora the Chrome browser.
    [Show full text]
  • Qoe Based Comparison of H.264/AVC and Webm/VP8 in Error-Prone Wireless Networkqoe Based Comparison of H.264/AVC and Webm/VP8 In
    QoE based comparison of H.264/AVC and WebM/VP8 in an error-prone wireless network Omer Nawaz, Tahir Nawaz Minhas, Markus Fiedler Department of Technology and Aesthetics (DITE) Blekinge Institute of Technology Karlskrona, Sweden fomer.nawaz, tahir.nawaz.minhas, markus.fi[email protected] Abstract—Quality of Experience (QoE) management is a prime the subsequent inter-frames are dependent will result in more topic of research community nowadays as video streaming, quality loss as compared to lower priority frame. Hence, the online gaming and security applications are completely reliant traditional QoS metrics simply fails to analyze the network on the network service quality. Moreover, there are no standard models to map Quality of Service (QoS) into QoE. HTTP measurement’s impact on the end-user service satisfaction. media streaming is primarily used for such applications due The other approach to measure the user-satisfaction is by to its coherence with the Internet and simplified management. direct interaction via subjective assessment. But the downside The most common video codecs used for video streaming are is the time and cost associated with these qualitative subjective H.264/AVC and Google’s VP8. In this paper, we have analyzed assessments and their inability to be applied in real-time the performance of these two codecs from the perspective of QoE. The most common end-user medium for accessing video content networks. The objective measurement quality tools like Mean is via home based wireless networks. We have emulated an error- Squared Error (MSE), Peak signal-to-noise ratio (PSNR), prone wireless network with different scenarios involving packet Structural Similarity Index (SSIM), etc.
    [Show full text]
  • Standards – ST.88 Page: 3.88.1 En / 03-88-01 Date
    HANDBOOK ON INDUSTRIAL PROPERTY INFORMATION AND DOCUMENTATION Ref.: Standards – ST.88 page: 3.88.1 STANDARD ST.88 RECOMMENDATIONS FOR ELECTRONIC REPRESENTATION OF INDUSTRIAL DESIGNS Adopted by the Committee on WIPO Standards (CWS) at its eighth session on December 4, 2020 Editorial Note by the International Bureau At its eighth session, the CWS discussed the treatment of SVG format within this Standard. The CWS referred the issue of SVG back to the Design Representation Task Force to recommend a revision to this Standard at the ninth session of the CWS. This Standard does not currently make recommendations on 3D objects. Recommendations for 3D objects and file formats are being evaluated by the 3D Task Force of the CWS. It is proposed to revisit this topic when the 3D Task Force completes their evaluation, and possibly make revisions to this Standard if appropriate. INTRODUCTION 1. These recommendations provide guidance on how to create, store, display, manage, search, publish and exchange electronic representations of industrial designs. OBJECTIVES 2. These recommendations are intended to achieve: The maximum re-use of the same electronic representations for applicants to file the same design at multiple Intellectual Property (IP) offices; A common set of requirements for IP offices to exchange electronic representations data; A common set of requirements for IP offices to process and publish electronic representations; and A common set of requirements to enhance automated search of electronic representations. DEFINITIONS AND TERMINOLOGY 3. For the purposes of these recommendations, the following terms apply unless otherwise specified: (a) “3D model” means an electronic file that is created by a specialized software, for mathematically representing the surface of an object in three dimensions; (b) “industrial design” means the visual aspect of an object, including its two-dimensional and three-dimensional features of shape and surface.
    [Show full text]
  • Forcepoint DLP Supported File Formats and Size Limits
    Forcepoint DLP Supported File Formats and Size Limits Supported File Formats and Size Limits | Forcepoint DLP | v8.8.1 This article provides a list of the file formats that can be analyzed by Forcepoint DLP, file formats from which content and meta data can be extracted, and the file size limits for network, endpoint, and discovery functions. See: ● Supported File Formats ● File Size Limits © 2021 Forcepoint LLC Supported File Formats Supported File Formats and Size Limits | Forcepoint DLP | v8.8.1 The following tables lists the file formats supported by Forcepoint DLP. File formats are in alphabetical order by format group. ● Archive For mats, page 3 ● Backup Formats, page 7 ● Business Intelligence (BI) and Analysis Formats, page 8 ● Computer-Aided Design Formats, page 9 ● Cryptography Formats, page 12 ● Database Formats, page 14 ● Desktop publishing formats, page 16 ● eBook/Audio book formats, page 17 ● Executable formats, page 18 ● Font formats, page 20 ● Graphics formats - general, page 21 ● Graphics formats - vector graphics, page 26 ● Library formats, page 29 ● Log formats, page 30 ● Mail formats, page 31 ● Multimedia formats, page 32 ● Object formats, page 37 ● Presentation formats, page 38 ● Project management formats, page 40 ● Spreadsheet formats, page 41 ● Text and markup formats, page 43 ● Word processing formats, page 45 ● Miscellaneous formats, page 53 Supported file formats are added and updated frequently. Key to support tables Symbol Description Y The format is supported N The format is not supported P Partial metadata
    [Show full text]
  • Webm Audio Codec
    Less is More - The Opus WebM Audio Codec Compressing digital audio has always been a trade-off between the quality of the sound and the size of the file. Twenty-five years ago, the mp3 codec1 took the audio world by storm, finding a way to reduce a .wav file to approximately 1/5 - 1/10 of its original size while maintaining similar audio quality. But when audio is highly compressed using the mp3 codec, it loses quality. The listener begins to hear audio artifacts and may have problems understanding the audio being played. Several attempts have been made to create a new codec that outperforms mp3 by maintaining high quality audio while reducing the file size, but none have gained significant attention. In the last decade a new codec, Opus WebM, has emerged that significantly outperforms mp3 in both size and quality when it comes to audio compression. It was developed by On2, Xiph and Matroska, sponsored by Google and released under a BSD license, which is a software license that imposes minimal restrictions on its use and distribution. It is incorporated in the open-source FFmpeg codec library that is widely used by developers around the world. More information about the Opus WebM codec is available here. Unfortunately, .webm has not been widely publicized in the consumer world, nor has it been made available in freeware audio editors like Audacity. The only way to convert audio to .webm is by installing FFmpeg and using the command line to do the conversion, which keeps it out of the realm of the common man.
    [Show full text]
  • Video - Dive Into HTML5
    Video - Dive Into HTML5 You are here: Home ‣ Dive Into HTML5 ‣ Video on the Web ❧ Diving In nyone who has visited YouTube.com in the past four years knows that you can embed video in a web page. But prior to HTML5, there was no standards- based way to do this. Virtually all the video you’ve ever watched “on the web” has been funneled through a third-party plugin — maybe QuickTime, maybe RealPlayer, maybe Flash. (YouTube uses Flash.) These plugins integrate with your browser well enough that you may not even be aware that you’re using them. That is, until you try to watch a video on a platform that doesn’t support that plugin. HTML5 defines a standard way to embed video in a web page, using a <video> element. Support for the <video> element is still evolving, which is a polite way of saying it doesn’t work yet. At least, it doesn’t work everywhere. But don’t despair! There are alternatives and fallbacks and options galore. <video> element support IE Firefox Safari Chrome Opera iPhone Android 9.0+ 3.5+ 3.0+ 3.0+ 10.5+ 1.0+ 2.0+ But support for the <video> element itself is really only a small part of the story. Before we can talk about HTML5 video, you first need to understand a little about video itself. (If you know about video already, you can skip ahead to What Works on the Web.) ❧ http://diveintohtml5.org/video.html (1 of 50) [6/8/2011 6:36:23 PM] Video - Dive Into HTML5 Video Containers You may think of video files as “AVI files” or “MP4 files.” In reality, “AVI” and “MP4″ are just container formats.
    [Show full text]
  • List of EPFL Recommended File Formats
    List of EPFL Recommended File Formats Type of Data Sub Type Recommended File Formats for Sharing, Reuse and Long-Term Preservation Acceptable Formats (up to 10 year) Not Suitable for Preservation Dataset Tabular data with extensive metadata comma-separated values (CSV) file unicode UTF-8 (.csv) with CSV on the Web descriptive metadata plain text data, ASCII (.txt) Hierarchical Data Format version 5 HDF5 (.hdf5) Hypertext Mark-up Language (HTML) (.html) LaTeX (.tex) SPSS portable format (.por) Tabular data with minimal metadata comma-separated values (CSV) unicode UTF-8 file (.csv) eXtensible Mark-up Language (XML) text according to an appropriate MS Excel (xls, .xlsb) tab-delimited file (.tab) Document Type Definition (DTD) or schema (.xml) OpenDocument Spreadsheet (.ods) MS Excel (.xlsx) Structured Query Language (SQL) dump, preferably from an open tool (PostgreSQL, MariaDB) Text Textual data PDF/A (.pdf) widely-used proprietary formats, e.g. MS Word (.docx) PowerPoint (.pptx) MS Word (.doc) plain text, unicode UTF-8 (.txt) PDF with embedded forms PowerPoint (.ppt) Open Document Text (.odt, .odm) Rich Text Format (.rtf) LaTeX (.tex) Markdown (.md) HTML (.htm, .html), XHMTL 1.0 XML marked-up text (.xml), with specified schema Code Plain text formats (e.g. Matlab/Octave .m , R-project .R, Python .py , and so on) Text files for S-plus (.sdd) Matlab (.mat) Jupyter Notebook (.iypnb) Matlab .mat, should be saved in HDF format. R-project (.rdata) Rstudio (.rstudio), Rmarkdown (.rmd) NetCDF Multimedia Digital image data Raster : Raster : Vector
    [Show full text]
  • Openmax IL VP8 and Webp Codec
    OpenMAX™ Integration Layer Extension VP8 and WebP Codec Component Version 1.0.0 Copyright © 2012 The Khronos Group Inc. February 14, 2012 Document version 1.0.0.0 Copyright © 2005-2012 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast, or otherwise exploited in any manner without the express prior written permission of the Khronos Group. You may use this specification for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be reformatted AS LONG AS the contents of the specification are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group website should be included whenever possible with specification distributions.
    [Show full text]
  • Content Guidelines
    APPEDINX H Content Guidelines Content Guidelines The following table lists the content guidelines for the Cisco IEC 4650. Table H-1 Content Guidelines Video formats Multiple video formats are supported on the native player including MPEG-1, MPEG-2, MPEG-4, and H.264. Multiple containers/muxers are supported on the native player including AVI, MOV, MP4, MPEG2, and MPEG-2/TS (extensions: .wmv, .avi, .mov, .mp4, .mpg, .ts). Formats not recommended: On2 VP 6 (used by old FLV) Note Native video is strongly preferred over Flash video. Note The IEC 4650 supports WebM (VP8/Vorbis) and Ogg (Theora/Vorbis) for HTML5 video. Note Use of the native player strongly preferred over HTML5 video. Note The native player’s video compatibility can be validated by using VLC 2.0.8. Audio formats Multiple audio formats are supported on the native player including mp2, mp3, aac, mp4a, wma1, wma2, flac, and mpga. HTML HTML4 / CSS3 (early support for HTML5) Flash Up to Flash 11 Cisco Interactive Experience Client User Guide H-1 Appendix H Content Guidelines Content Guidelines Video Performance When using a native player, the IEC 4610 can support H.264 video up to Limitations 720p @ 6Mbps. Note The amount of CPU power required to decode a video clip depends on multiple factors such as codec, bitrate, and resolution of the video source. Different video codecs have different compression algorithms. H.264 offers much better compression efficiency than MPEG-2 or MPEG-4 but uses much more a complex algorithm and requires more CPU power to decode. For example, to achieve the same level of quality, it may require 5 Mbps using MPEG2 but less than 2 Mbps using H.264.
    [Show full text]