DOCSLIB.ORG

Video Codecs in Close Battle Stephen Wright, Openwave Mobility 8/25/2014 06:00 AM EDT

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Video Codecs in Close Battle Stephen Wright, Openwave Mobility 8/25/2014 06:00 AM EDT Video Codecs in Close Battle Stephen Wright, Openwave Mobility 8/25/2014 06:00 AM EDT The battle between today's leading video codecs -- HEVC and VP9 -- will be a closer fight than we saw between the leaders in the prior generation, VP8 and AVC. There may be room in the market for both – at least in the short term. The Advanced Video Codec (AVC, a.k.a. H.264) will likely remain the dominant, mature video codec for the mobile market in the short term. Content providers will not provide High Efficiency Video Codec (HEVC, otherwise known as H.265) or VP9 variants for mobile until a critical mass of mobile devices provide support. The mobile market will not have critical mass until hardware accelerated chipsets are available, and these devices permeate the market. VP9 is the follow on to VP8, which Google used in its WebM format. VP8 was developed by On2 Technologies, who were acquired by Google in February 2010. WebM is a combination of the VP8 video codec, OGG Vorbis audio, and the Matroksa container format. All of which are open source. With WebM, Google attempted to exploit the chink in the AVC armour that it is a patented technology. It is hard to predict a clear winner between HEVC and VP9. Apple has shown no sign of adding support for VPx codecs, and maintains its support for the MPEG standards (AVC and HEVC). Given the popularity of Apple devices, HEVC is all but guaranteed a place in the ecosystem. The first 4K device from Apple should validate this. At this point, comparative studies show HEVC to be the superior format. The situation may change over time as the codecs mature. On paper, HEVC has 10 times the encoding complexity of AVC and twice decoding complexity. This means that modern laptop and high end mobile devices area already capable of decoding in software. The cost is a heavy battery drain, which can be addressed with hardware acceleration The success of VP9 depends on support from clients and content providers, and in Google the owner of the standard has a large share of the client and content market. YouTube already publishes VP9 content as variants in its DASH format, with no current support for HEVC. However if Apple releases a 4K-capable device using HEVC and maintains its stance in not supporting VP9, YouTube will be forced to either: Encode 4K using AVC. Unlikely as the bandwidth costs would be prohibitive. Do not provide 4K to Apple users. Again, an unlikely scenario. Provide HEVC variants. The most likely outcome. Also in question is the patent-free status of VP9. Given that Google had to license patents from the MPEG-LA patent pool for VP8, it is likely that VP9 also infringes patents in the MPEG-LA patent pool which has grown to include HEVC. It's unclear if Google will need to license the technology from MPEG-LA and, if so, if MPEG-LA will be willing to grant the license or see an opportunity to hurt a competing format. YouTube is currently providing VP9 content as a DASH variant. Netflix have chosen to use a HEVC encoding for their 4K TV service. This has punished the early adopters of 4K television, as the first models contained hardware support for AVC decoding only. This makes the early release 4K equipment incompatible with the Netflix service. 4K video is unlikely to be delivered to devices on mobile networks in the short to medium term. Displays supporting 4K will only be supported on larger tablet screens, and so not applicable to the majority of mobile devices. In addition, even using the new generation codecs the bandwidth cost is simply too high. Even today on smartphone and tablet devices, content providers such as YouTube will serve a lower resolution to the same device on 3G than on WiFi due to the bandwidth demands. However, 4K video will drive adoption of the new generation codecs in video publishing. Once the codec implementations and content publishing tools reach a level of maturity with HEVC/VP9, content publishers will have the ability to easily produce lower resolution versions of the content targeted at mobile devices using the next generation codecs, saving 40% to 50% in the bandwidth costs. At that point, hardware acceleration will become desirable on mobile devices to minimize the increased battery drain. We are likely to see a lot of movement in this space over the coming year. As more 4K devices become available, more 4K content will become available. A clearer picture should then emerge on the adoption of HEVC and VP9, and use will filter down into lower resolution video. It is then that we will see the real impact on the mobile market. One dark horse clouds the picture for next generation of video codecs. The Mozilla Foundation is working on a royalty-free codec named Daala. The project is in very early development, however Mozilla says its goal is "...to provide a free to implement, use and distribute digital media format and reference implementation with technical performance superior to H.265." This will be an interesting project to watch. — Stephen Wright is a software architect with Openwave Mobility. He has 15 years of experience in software development for the telecommunications industry and currently specializes in content adaptation and optimization for mobile devices with a focus on delivering the best possible experience for mobile users browsing the web. .
Load more

Recommended publications
  • Thumbor-Video-Engine Release 1.2.2
    thumbor-video-engine Release 1.2.2 Aug 14, 2021 Contents 1 Installation 3 2 Setup 5 2.1 Contents.................................................6 2.2 License.................................................. 13 2.3 Indices and tables............................................ 13 i ii thumbor-video-engine, Release 1.2.2 thumbor-video-engine provides a thumbor engine that can read, crop, and transcode audio-less video files. It supports input and output of animated GIF, animated WebP, WebM (VP9) video, and MP4 (default H.264, but HEVC is also supported). Contents 1 thumbor-video-engine, Release 1.2.2 2 Contents CHAPTER 1 Installation pip install thumbor-video-engine Go to GitHub if you need to download or install from source, or to report any issues. 3 thumbor-video-engine, Release 1.2.2 4 Chapter 1. Installation CHAPTER 2 Setup In your thumbor configuration file, change the ENGINE setting to 'thumbor_video_engine.engines. video' to enable video support. This will allow thumbor to support video files in addition to whatever image formats it already supports. If the file passed to thumbor is an image, it will use the Engine specified by the configuration setting IMAGING_ENGINE (which defaults to 'thumbor.engines.pil'). To enable transcoding between formats, add 'thumbor_video_engine.filters.format' to your FILTERS setting. If 'thumbor.filters.format' is already present, replace it with the filter from this pack- age. ENGINE = 'thumbor_video_engine.engines.video' FILTERS = [ 'thumbor_video_engine.filters.format', 'thumbor_video_engine.filters.still', ] To enable automatic transcoding to animated gifs to webp, you can set FFMPEG_GIF_AUTO_WEBP to True. To use this feature you cannot set USE_GIFSICLE_ENGINE to True; this causes thumbor to bypass the custom ENGINE altogether.
    [Show full text]
  • C-Based Hardware Design of Imdct Accelerator for Ogg Vorbis Decoder
    C-BASED HARDWARE DESIGN OF IMDCT ACCELERATOR FOR OGG VORBIS DECODER Shinichi Maeta1, Atsushi Kosaka1, Akihisa Yamada1, 2, Takao Onoye1, Tohru Chiba1, 2, and Isao Shirakawa1 1Department of Information Systems Engineering, 2Sharp Corporation Graduate School of Information Science and Technology, 2613-1 Ichinomoto, Tenri, Nara, 632-8567 Japan Osaka University phone: +81 743 65 2531, fax: +81 743 65 3963, 2-1 Yamada-oka, Suita, Osaka, 565-0871 Japan email: [email protected], phone: +81 6 6879 7808, fax: +81 6 6875 5902, [email protected] email: {maeta, kosaka, onoye, sirakawa}@ist.osaka-u.ac.jp ABSTRACT ARM7TDMI is used as the embedded processor since it has This paper presents hardware design of an IMDCT accelera- come into wide use recently. tor for an Ogg Vorbis decoder using a C-based design sys- tem. Low power implementation of audio codec is important 2. OGG VORBIS CODEC in order to achieve long battery life of portable audio de- 2.1 Ogg Vorbis Overview vices. Through the computational cost analysis of the whole decoding process, it is found that Ogg Vorbis requires higher Figure 1 shows a block diagram of the Ogg Vorbis codec operation frequency of an embedded processor than MPEG processes outlined below. Audio. In order to reduce the CPU load, an accelerator is designed as specific hardware for IMDCT, which is detected MDCT Psycho Audio Remove Channel Acoustic VQ as the most computation-intensive functional block. Real- Signal Floor Coupling time decoding of Ogg Vorbis is achieved with the accelera- FFT Model Ogg Vorbis tor and an embedded processor both run at 36MHz.
    [Show full text]
  • 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]
  • Blackberry QNX Multimedia Suite
    PRODUCT BRIEF QNX Multimedia Suite The QNX Multimedia Suite is a comprehensive collection of media technology that has evolved over the years to keep pace with the latest media requirements of current-day embedded systems. Proven in tens of millions of automotive infotainment head units, the suite enables media-rich, high-quality playback, encoding and streaming of audio and video content. The multimedia suite comprises a modular, highly-scalable architecture that enables building high value, customized solutions that range from simple media players to networked systems in the car. The suite is optimized to leverage system-on-chip (SoC) video acceleration, in addition to supporting OpenMAX AL, an industry open standard API for application-level access to a device’s audio, video and imaging capabilities. Overview Consumer’s demand for multimedia has fueled an anywhere- o QNX SDK for Smartphone Connectivity (with support for Apple anytime paradigm, making multimedia ubiquitous in embedded CarPlay and Android Auto) systems. More and more embedded applications have require- o Qt distributions for QNX SDP 7 ments for audio, video and communication processing capabilities. For example, an infotainment system’s media player enables o QNX CAR Platform for Infotainment playback of content, stored either on-board or accessed from an • Support for a variety of external media stores external drive, mobile device or streamed over IP via a browser. Increasingly, these systems also have streaming requirements for Features at a Glance distributing content across a network, for instance from a head Multimedia Playback unit to the digital instrument cluster or rear seat entertainment units. Multimedia is also becoming pervasive in other markets, • Software-based audio CODECs such as medical, industrial, and whitegoods where user interfaces • Hardware accelerated video CODECs are increasingly providing users with a rich media experience.
    [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]
  • Detail Streaming Support Protocols
    Encore+ User Guide Detail Streaming Support Protocols Supported Audio Codecs Supported Container Formats • MP3 • WAV • AAC • M4A • FLAC • OGG • LPCM/WAV/AIFF • AIFF • ALAC Supported Protocols • WMA, WMA9 • SHOUTcast • Ogg Vorbis • HTTPS Supported Playlist • WMA streaming • ASX • RTSP/SDP • M3U • PLS • WPL 43 Detail Audio Codec Support Encore+ User Guide Supported MP3 encoding parameters • Sampling rates [kHz]: 32, 44.1, 48 • Resolution [bits]: 16 • Bit rate [kbps]: 32, 40, 48, 56, 64, 80, 96, 112, 128, 160, 192, 224, 256, 320, VBR • Channels: stereo, joined stereo, mono • MP3PRO playback • MP3 File extensions: *.mp3 • Decoding of ID3v1, ID3v2, MP3 ID tags including optional album art in .jpeg format up to 2 megapixels • Gapless MP3: Playback is gapless if the container provides LAME encoder delay and padding tags. Supported Vorbis encoding parameters • Sampling rates [kHz]: 32, 44.1, 48 • Resolution [bits]: 16 • Nominal bit rate [kbps] (quality level): 80 (Q1), 96 (Q2), 112 (Q3), 128 (Q4), 160 (Q5), 192 (Q6), • Channels: stereo • The audio player supports reading of Vorbis content stored in Ogg containers. Supported file name extensions: *.ogg and *.oga. • The audio player supports decoding of Vorbis comments. NOTE: There is no specification for tag names. The system relies on the OSS implementation. • Tag names decoded: TITLE, ALBUM, ARTIST, GENRE. • Binary data (e.g. for album art) is not supported. • The audio player supports gapless Vorbis playback. Supported FLAC encoding parameters • Sampling rates [kHz]: 44.1, 48, 88.2, 96, 176.4, 192 • Resolution [bits]: 16, 24 • Channels: stereo, mono • The audio player supports reading of FLAC content stored in native FLAC containers.
    [Show full text]
  • Ogg Audio Codec Download
    Ogg audio codec download click here to download To obtain the source code, please see the xiph download page. To get set up to listen to Ogg Vorbis music, begin by selecting your operating system above. Check out the latest royalty-free audio codec from Xiph. To obtain the source code, please see the xiph download page. Ogg Vorbis is Vorbis is everywhere! Download music Music sites Donate today. Get Set Up To Listen: Windows. Playback: These DirectShow filters will let you play your Ogg Vorbis files in Windows Media Player, and other OggDropXPd: A graphical encoder for Vorbis. Download Ogg Vorbis Ogg Vorbis is a lossy audio codec which allows you to create and play Ogg Vorbis files using the command-line. The following end-user download links are provided for convenience: The www.doorway.ru DirectShow filters support playing of files encoded with Vorbis, Speex, Ogg Codecs for Windows, version , ; project page - for other. Vorbis Banner Xiph Banner. In our effort to bring Ogg: Media container. This is our native format and the recommended container for all Xiph codecs. Easy, fast, no torrents, no waiting, no surveys, % free, working www.doorway.ru Free Download Ogg Vorbis ACM Codec - A new audio compression codec. Ogg Codecs is a set of encoders and deocoders for Ogg Vorbis, Speex, Theora and FLAC. Once installed you will be able to play Vorbis. Ogg Vorbis MSACM Codec was added to www.doorway.ru by Bjarne (). Type: Freeware. Updated: Audiotags: , 0x Used to play digital music, such as MP3, VQF, AAC, and other digital audio formats.
    [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]
  • Encoding H.264 Video for Streaming and Progressive Download
    W4: KEY ENCODING SKILLS, TECHNOLOGIES TECHNIQUES STREAMING MEDIA EAST - 2019 Jan Ozer www.streaminglearningcenter.com [email protected]/ 276-235-8542 @janozer Agenda • Introduction • Lesson 5: How to build encoding • Lesson 1: Delivering to Computers, ladder with objective quality metrics Mobile, OTT, and Smart TVs • Lesson 6: Current status of CMAF • Lesson 2: Codec review • Lesson 7: Delivering with dynamic • Lesson 3: Delivering HEVC over and static packaging HLS • Lesson 4: Per-title encoding Lesson 1: Delivering to Computers, Mobile, OTT, and Smart TVs • Computers • Mobile • OTT • Smart TVs Choosing an ABR Format for Computers • Can be DASH or HLS • Factors • Off-the-shelf player vendor (JW Player, Bitmovin, THEOPlayer, etc.) • Encoding/transcoding vendor Choosing an ABR Format for iOS • Native support (playback in the browser) • HTTP Live Streaming • Playback via an app • Any, including DASH, Smooth, HDS or RTMP Dynamic Streaming iOS Media Support Native App Codecs H.264 (High, Level 4.2), HEVC Any (Main10, Level 5 high) ABR formats HLS Any DRM FairPlay Any Captions CEA-608/708, WebVTT, IMSC1 Any HDR HDR10, DolbyVision ? http://bit.ly/hls_spec_2017 iOS Encoding Ladders H.264 HEVC http://bit.ly/hls_spec_2017 HEVC Hardware Support - iOS 3 % bit.ly/mobile_HEVC http://bit.ly/glob_med_2019 Android: Codec and ABR Format Support Codecs ABR VP8 (2.3+) • Multiple codecs and ABR H.264 (3+) HLS (3+) technologies • Serious cautions about HLS • DASH now close to 97% • HEVC VP9 (4.4+) DASH 4.4+ Via MSE • Main Profile Level 3 – mobile HEVC (5+)
    [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]
  • Game Audio the Role of Audio in Games
    the gamedesigninitiative at cornell university Lecture 18 Game Audio The Role of Audio in Games Engagement Entertains the player Music/Soundtrack Enhances the realism Sound effects Establishes atmosphere Ambient sounds Other reasons? the gamedesigninitiative 2 Game Audio at cornell university The Role of Audio in Games Feedback Indicate off-screen action Indicate player should move Highlight on-screen action Call attention to an NPC Increase reaction time Players react to sound faster Other reasons? the gamedesigninitiative 3 Game Audio at cornell university History of Sound in Games Basic Sounds • Arcade games • Early handhelds • Early consoles the gamedesigninitiative 4 Game Audio at cornell university Early Sounds: Wizard of Wor the gamedesigninitiative 5 Game Audio at cornell university History of Sound in Games Recorded Basic Sound Sounds Samples Sample = pre-recorded audio • Arcade games • Starts w/ MIDI • Early handhelds • 5th generation • Early consoles (Playstation) • Early PCs the gamedesigninitiative 6 Game Audio at cornell university History of Sound in Games Recorded Some Basic Sound Variability Sounds Samples of Samples • Arcade games • Starts w/ MIDI • Sample selection • Early handhelds • 5th generation • Volume • Early consoles (Playstation) • Pitch • Early PCs • Stereo pan the gamedesigninitiative 7 Game Audio at cornell university History of Sound in Games Recorded Some More Basic Sound Variability Variability Sounds Samples of Samples of Samples • Arcade games • Starts w/ MIDI • Sample selection • Multiple
    [Show full text]
  • The Daala Video Codec Project Next-Next Generation Video
    The Daala Video Codec Project Next-next Generation Video Timothy B. Terriberry Mozilla & The Xiph.Org Foundation ● Patents are no longer a problem for free software – We can all go home 2 Mozilla & The Xiph.Org Foundation ● Except... not quite 3 Mozilla & The Xiph.Org Foundation Carving out Exceptions in OIN (Table 0 contains one Xiph codec: FLAC) 4 Mozilla & The Xiph.Org Foundation Why This Matters ● Encumbered codecs are a billion dollar toll-tax on communications – Every cost from codecs is repeated a million fold in all multimedia software ● Codec licensing is anti-competitive – Licensing regimes are universally discriminatory – An excuse for proprietary software (Flash) ● Ignoring licensing creates risks that can show up at any time – A tax on success 5 Mozilla & The Xiph.Org Foundation The Royalty-Free Video Challenge ● Creating good codecs is hard – But we don’t need many – The best implementations of patented codecs are already free software ● Network effects decide – Where RF is established, non-free codecs see no adoption (JPEG, PNG, FLAC, …) ● RF is not enough – People care about different things – Must be better on all fronts 6 Mozilla & The Xiph.Org Foundation We Did This for Audio 7 Mozilla & The Xiph.Org Foundation The Daala Project ● Goal: Better than HEVC without infringing IPR ● Need a better strategy than “read a lot of patents” – People don’t believe you – Analysis is error-prone ● Try to stay far away from the line, but... ● One mistake can ruin years of development effort ● See: H.264 Baseline 8 Mozilla & The Xiph.Org
    [Show full text]