Jump to content

NETVC: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Flugaal (talk | contribs)
No edit summary
Flugaal (talk | contribs)
mNo edit summary
Line 10: Line 10:
At the IETF there are now also other partners involved in the development of NETVC.<ref name=NETVCJuly2015ThorIETF/><ref name="Thor"/>
At the IETF there are now also other partners involved in the development of NETVC.<ref name=NETVCJuly2015ThorIETF/><ref name="Thor"/>


At the IETF meeting 101 in March 2018 xvc was presented by Divideon as another candidate. Thor developer Steinar Midskogen confirmed that a subset of xvc that Divideon considers royalty-free has better compression than Thor at comparable complexity settings. It was agreed to pause physical meetings of the working group to see how the market for royalty-free video formats develops given that the teams behind several of the format candidates presented instead chose to develop a royalty-free standard in the AOM forum.<ref>{{Citation|last=|first=|title=NETVC working group session at IETF102|date=2018-07-19|url=https://www.youtube.com/watch?v=EDX2tFTDH70|volume=|pages=|publisher=Internet Engineering Task Force|access-date=2019-03-24}}</ref>
At the IETF meeting 101 in March 2018 xvc was presented by Divideon as another candidate. Thor developer Steinar Midtskogen confirmed that a subset of xvc that Divideon considers royalty-free has better compression than Thor at comparable complexity settings. It was agreed to pause physical meetings of the working group to see how the market for royalty-free video formats develops given that the teams behind several of the format candidates presented instead chose to develop a royalty-free standard in the AOM forum.<ref>{{Citation|last=|first=|title=NETVC working group session at IETF102|date=2018-07-19|url=https://www.youtube.com/watch?v=EDX2tFTDH70|volume=|pages=|publisher=Internet Engineering Task Force|access-date=2019-03-24}}</ref>


==Schedule==
==Schedule==

Revision as of 20:07, 24 March 2019

The Internet Video Codec (NETVC) is a standardization project for a royalty-free video codec hosted by the IETF.[1] It is intended to provide a royalty-free alternative to industry standards such as MPEG-4 and HEVC that require licensing payments for many uses. The group has put together a list of criteria to be met by the new video standard. The VP9-based format AOMedia Video 1 (AV1) from the Alliance for Open Media (AOM) is the primary contender for standardisation by the NetVC working group.[2][3]

The October 2015 basic draft requirements for NETVC are support for a bit depth of 8-bits to 10-bits per sample, 4:2:0 chroma subsampling, 4:4:4 YUV, low coding delay capability, feasible real time decoder/encoder software implementations, temporal scalability, and error resilience tools.[4] The October 2015 optional draft requirements for NETVC is support for a bit depth of up to 16-bits per sample, 4:2:2 chroma subsampling, RGB video, auxiliary channel planes, high dynamic range, and parallel processing tools.[4]

On March 24, 2015, Xiph.org's Daala codec was presented to the IETF as a candidate for NETVC.[1][5][6] Daala coding techniques have been proposed to the IETF for inclusion into NETVC.[7]

On July 22, 2015, Cisco Systems' Thor video codec was presented to the IETF as a candidate for their NETVC video standard.[8] Thor is being developed by Cisco Systems and uses some Cisco elements that are also used by HEVC.[9] The Constrained Low-Pass Filter (CLPF) and motion compensation that are used in Thor were tested with Daala.[10]

At the IETF there are now also other partners involved in the development of NETVC.[9][10]

At the IETF meeting 101 in March 2018 xvc was presented by Divideon as another candidate. Thor developer Steinar Midtskogen confirmed that a subset of xvc that Divideon considers royalty-free has better compression than Thor at comparable complexity settings. It was agreed to pause physical meetings of the working group to see how the market for royalty-free video formats develops given that the teams behind several of the format candidates presented instead chose to develop a royalty-free standard in the AOM forum.[11]

Zeitplan

The planned schedule for the development of NETVC is:[12]

  • April 2018: Informational document on requirements and evaluation criteria.
  • July 2018: Informational document on test results, initial codec specification and reference implementation.
  • December 2018: Standards documents on codec specification and storage format specification.

References

  1. ^ a b "Birds of a Feather Meetings (IETF Pre-WG Efforts)". Internet Engineering Task Force. Retrieved 2015-08-05.
  2. ^ Sebastian Grüner (golem.de), July 19, 2016: Der nächste Videocodec soll 25 Prozent besser sein als H.265 (german)
  3. ^ https://tools.ietf.org/html/draft-ietf-netvc-requirements
  4. ^ a b A. Filippov (2015-10-19). "Video Codec Requirements and Evaluation Methodology". IETF. Retrieved 2015-11-08.
  5. ^ Lucian Armasu (2015-03-25). "IETF Begins Standardization Process For Next-Generation 'NETVC' Video Codec (Daala)". Tom's Hardware. Retrieved 2015-08-05.
  6. ^ "NETVC BoF" (PDF). Internet Engineering Task Force. 2015-03-24. Retrieved 2015-08-06.
  7. ^ NetVC Working Group Documents
  8. ^ "NETVC IETF 93". Internet Engineering Task Force. Retrieved 2015-08-11.
  9. ^ a b "Thor" (PDF). Internet Engineering Task Force. Retrieved 2015-08-11.
  10. ^ a b NETVC Hackathon Results IETF 93 (Prague) (PDF)
  11. ^ NETVC working group session at IETF102, Internet Engineering Task Force, 2018-07-19, retrieved 2019-03-24
  12. ^ "Internet Video Codec (netvc)". IETF. Retrieved 2015-08-02.