Versatile Video Coding: Difference between revisions

From HandWiki
update
 
fixing
 
Line 1: Line 1:
{{Short description|Video compression standard}}
{{Short description|Video compression standard}}
{{Infobox technology standard
{{Infobox technology standard
| title             = VVC / H.266 / MPEG-I Part 3
| title = VVC / H.266 / MPEG-I Part 3
| long_name         = Versatile video coding
| long_name = Versatile video coding
| image             = File:Versatile Video Coding (logo).svg
| image = File:Versatile Video Coding (logo).svg
| caption           =  
| caption =  
| status           = In force
| status = In force
| year_started     = 2017
| year_started = 2017
| version           = 3rd Edition
| version = 4th Edition<ref>https://www.itu.int/rec/T-REC-H.266-202601-P/en</ref>
| version_date     = 29 September 2023<!-- ITU final approval date -->
| version_date = 13 January 2026<!-- ITU final approval date -->
| preview           =
| preview =  
| preview_date     =
| preview_date =  
| organization     = ITU-T, ISO, [[Organization:International Electrotechnical Commission|IEC]]
| organization = ITU-T, ISO, [[Organization:International Electrotechnical Commission|IEC]]
| committee         = SG16 (Secretary: Simao Campos) (VCEG), MPEG
| committee = SG16 (Secretary: Simao Campos) (VCEG), MPEG
| base_standards   = [[H.261]], H.262, [[H.263]], H.264, H.265, ISO/IEC 14496-2, [[MPEG-1]]
| base_standards = [[H.261]], H.262, [[H.263]], H.264, H.265, ISO/IEC 14496-2, [[MPEG-1]]
| predecessor       = H.265
| predecessor = H.265
| abbreviation     =
| abbreviation =  
| domain           = Video compression
| domain = Video compression
| license           = [[Social:Reasonable and non-discriminatory licensing|RAND]]
| license = [[Social:Reasonable and non-discriminatory licensing|RAND]]
| website           = {{URL|https://www.itu.int/rec/T-REC-H.266}}
| website = {{URL|https://www.itu.int/rec/T-REC-H.266}}
|first_published=2020}}
| first_published = 2020
}}


'''Versatile Video Coding''' ('''VVC'''), also known as '''H.266''',<ref>{{Cite web |title=H.266: Versatile video coding |url=https://www.itu.int/rec/T-REC-H.266 |url-status=live |archive-url=https://web.archive.org/web/20210621114852/https://www.itu.int/rec/T-REC-H.266 |archive-date=2021-06-21 |access-date=2021-06-21 |website=[[Organization:International Telecommunication Union|International Telecommunication Union]]}}</ref> '''ISO/IEC 23090-3''',<ref>{{cite web |date=September 2022 |title=Information technology — Coded representation of immersive media — Part 3: Versatile video coding |url=https://www.iso.org/standard/83531.html |accessdate=2021-02-16 |website=[[Organization:International Organization for Standardization|International Organization for Standardization]] |language=en |id=ISO/IEC 23090-3:2022 |edition=2nd}}</ref> and '''MPEG-I Part 3''', is a [[Video coding format|video compression standard]] finalized on 6 July 2020, by the Joint Video Experts Team (JVET)<ref>{{Cite web |title=JVET - Joint Video Experts Team |url=https://www.itu.int/en/ITU-T/studygroups/2017-2020/16/Pages/video/jvet.aspx |access-date=2019-01-21 |website=[[Organization:International Telecommunication Union|International Telecommunication Union]]}}</ref> of the [[Organization:Video Coding Experts Group|VCEG]] working group of ITU-T Study Group 16 and the [[Moving Picture Experts Group|MPEG]] working group of ISO/IEC JTC 1/SC 29. It is the successor to [[High Efficiency Video Coding]] (HEVC, also known as ITU-T H.265 and MPEG-H Part 2). It was developed with two primary goals{{snd}}improved compression performance and support for a very broad range of applications.<ref>{{cite journal |first1=Benjamin |last1=Bross |first2=Jianle |last2=Chen |first3=Jens-Rainer |last3=Ohm |first4=Gary J. |last4=Sullivan |first5=Ye-Kui |last5=Wang |title=Developments in International Video Coding Standardization After AVC, With an Overview of Versatile Video Coding (VVC) |journal=[[Proceedings of the IEEE]] |volume=109 |issue=9 |pages=1463–1493 |doi=10.1109/JPROC.2020.3043399 |date=September 2021 |s2cid=234183758 |doi-access=free }}</ref><ref>{{cite journal |first1=Benjamin |last1=Bross |first2=Ye-Kui |last2=Wang |first3=Yan |last3=Ye |first4=Shan |last4=Liu |first5=Gary J. |last5=Sullivan |first6=Jens-Rainer |last6=Ohm |title=Overview of the Versatile Video Coding (VVC) Standard and its Applications |journal=  IEEE Transactions on Circuits and Systems for Video Technology|volume=31 |issue=10 |pages=3736–3764 |doi=10.1109/TCSVT.2021.3101953 |date=October 2021 |bibcode=2021ITCSV..31.3736B |s2cid=238243504 |doi-access=free }}</ref><ref>{{cite journal |first1=Jill M. |last1=Boyce|first2=Jianle |last2=Chen |first3=Shan |last3=Liu |first4=Jens-Rainer |last4=Ohm |first5=Gary J. |last5=Sullivan |first6=Thomas |last6=Wiegand |first7=Yan |last7=Ye |first8=Wenwu |last8=Zhu |title=Guest Editorial Introduction to the Special Section on the VVC Standard |journal=  IEEE Transactions on Circuits and Systems for Video Technology|volume=31 |issue=10 |pages=3731–3735 |doi=10.1109/TCSVT.2021.3111712 |date=October 2021 |bibcode=2021ITCSV..31.3731B |s2cid=238425004 |doi-access=free }}</ref>
'''Versatile Video Coding''' ('''VVC'''), also known as '''H.266''',<ref>{{Cite web |title=H.266: Versatile video coding |url=https://www.itu.int/rec/T-REC-H.266 |url-status=live |archive-url=https://web.archive.org/web/20210621114852/https://www.itu.int/rec/T-REC-H.266 |archive-date=2021-06-21 |access-date=2021-06-21 |website=[[Organization:International Telecommunication Union|International Telecommunication Union]]}}</ref> '''ISO/IEC 23090-3''',<ref>{{cite web |date=September 2022 |title=Information technology — Coded representation of immersive media — Part 3: Versatile video coding |url=https://www.iso.org/standard/83531.html |access-date=2021-02-16 |website=[[Organization:International Organization for Standardization|International Organization for Standardization]] |language=en |id=ISO/IEC 23090-3:2022 |edition=2nd}}</ref> and '''MPEG-I Part 3''', is a [[Video coding format|video compression standard]] finalized on 6 July 2020, by the Joint Video Experts Team (JVET)<ref>{{Cite web |title=JVET - Joint Video Experts Team |url=https://www.itu.int/en/ITU-T/studygroups/2017-2020/16/Pages/video/jvet.aspx |access-date=2019-01-21 |website=[[Organization:International Telecommunication Union|International Telecommunication Union]]}}</ref> of the [[Organization:Video Coding Experts Group|VCEG]] working group of ITU-T Study Group 16 and the [[Moving Picture Experts Group|MPEG]] working group of ISO/IEC JTC 1/SC 29. It is the successor to [[High Efficiency Video Coding]] (HEVC, also known as ITU-T H.265 and MPEG-H Part 2). It was developed with two primary goals{{snd}}improved compression performance and support for a very broad range of applications.<ref>{{cite journal |first1=Benjamin |last1=Bross |first2=Jianle |last2=Chen |first3=Jens-Rainer |last3=Ohm |first4=Gary J. |last4=Sullivan |first5=Ye-Kui |last5=Wang |title=Developments in International Video Coding Standardization After AVC, With an Overview of Versatile Video Coding (VVC) |journal=[[Proceedings of the IEEE]] |volume=109 |issue=9 |pages=1463–1493 |doi=10.1109/JPROC.2020.3043399 |date=September 2021 |s2cid=234183758 |doi-access=free }}</ref><ref>{{cite journal |first1=Benjamin |last1=Bross |first2=Ye-Kui |last2=Wang |first3=Yan |last3=Ye |first4=Shan |last4=Liu |first5=Gary J. |last5=Sullivan |first6=Jens-Rainer |last6=Ohm |title=Overview of the Versatile Video Coding (VVC) Standard and its Applications |journal=  IEEE Transactions on Circuits and Systems for Video Technology|volume=31 |issue=10 |pages=3736–3764 |doi=10.1109/TCSVT.2021.3101953 |date=October 2021 |bibcode=2021ITCSV..31.3736B |s2cid=238243504 |doi-access=free }}</ref><ref>{{cite journal |first1=Jill M. |last1=Boyce|first2=Jianle |last2=Chen |first3=Shan |last3=Liu |first4=Jens-Rainer |last4=Ohm |first5=Gary J. |last5=Sullivan |first6=Thomas |last6=Wiegand |first7=Yan |last7=Ye |first8=Wenwu |last8=Zhu |title=Guest Editorial Introduction to the Special Section on the VVC Standard |journal=  IEEE Transactions on Circuits and Systems for Video Technology|volume=31 |issue=10 |pages=3731–3735 |doi=10.1109/TCSVT.2021.3111712 |date=October 2021 |bibcode=2021ITCSV..31.3731B |s2cid=238425004 |doi-access=free }}</ref>


== Concept ==
== Concept ==
In October 2015, the [[Moving Picture Experts Group|MPEG]] and [[Organization:Video Coding Experts Group|VCEG]] formed the Joint Video Exploration Team (JVET) to evaluate available compression technologies and study the requirements for a next-generation video compression standard. The new standard has about 50% better compression rate for the same perceptual quality compared to HEVC,<ref name=":0" /> with support for lossless and lossy compression. It supports resolutions ranging from very low resolution up to [[4K resolution|4K]] and 16K as well as 360° videos. VVC supports [[YCbCr]] 4:4:4, 4:2:2 and 4:2:0 with 8–10 bits per component, [[Engineering:Rec. 2100|BT.2100]] wide color gamut and [[Engineering:High-dynamic-range video|high dynamic range (HDR)]] of more than 16 [[Physics:Exposure value|stop]]s (with peak brightness of 1,000, 4,000 and 10,000 [[Candela per square metre|nits]]), auxiliary channels (for depth, transparency, etc.), variable and fractional frame rates from 0 to 120&nbsp;Hz and higher, scalable video coding for temporal (frame rate), spatial (resolution), SNR, color gamut and dynamic range differences, stereo/multiview coding, panoramic formats, and still-picture coding. Work on high bit depth support (12 to 16 bits per component) started in October 2020<ref>{{Cite web |author1=T. Ikai |author2=T. Zhou |author3=T. Hashimoto |title=AHG12: VVC coding tool evaluation for high bit-depth coding |url=http://phenix.it-sudparis.eu/jvet/doc_end_user/current_document.php?id=10466 |website=JVET document management system |access-date=15 November 2020 |archive-date=11 April 2024 |archive-url=https://web.archive.org/web/20240411164311/http://phenix.it-sudparis.eu/jvet/doc_end_user/current_document.php?id=10466 |url-status=dead }}</ref> and was included in the second edition published in 2022. Encoding complexity of several times (up to ten times) that of [[High Efficiency Video Coding|HEVC]] is expected, depending on the quality of the encoding algorithm (which is outside the scope of the standard). The decoding complexity is about twice that of HEVC.
In October 2015, the [[Moving Picture Experts Group|MPEG]] and [[Organization:Video Coding Experts Group|VCEG]] formed the Joint Video Exploration Team (JVET) to evaluate available compression technologies and study the requirements for a next-generation video compression standard. The new standard has about 50% better compression rate for the same perceptual quality compared to HEVC,<ref name=":0" /> with support for lossless and lossy compression. It supports resolutions ranging from very low resolution up to [[4K resolution|4K]] and 16K as well as 360° videos. VVC supports [[YCbCr]] 4:4:4, 4:2:2 and 4:2:0 with 8–10 bits per component, [[Engineering:Rec. 2100|BT.2100]] wide color gamut and [[Engineering:High-dynamic-range video|high dynamic range (HDR)]] of more than 16 [[Physics:Exposure value|stop]]s (with peak brightness of 1,000, 4,000 and 10,000 [[Candela per square metre|nits]]),{{Clarify|date=March 2026|reason=What is meant by "and"?}} auxiliary channels (for depth, transparency, etc.), variable and fractional frame rates from 0 to 120&nbsp;Hz and higher, scalable video coding for temporal (frame rate), spatial (resolution), SNR, color gamut and dynamic range differences, stereo/multiview coding, panoramic formats, and still-picture coding. Work on high bit depth support (12 to 16 bits per component) started in October 2020<ref>{{Cite web |author1=T. Ikai |author2=T. Zhou |author3=T. Hashimoto |title=AHG12: VVC coding tool evaluation for high bit-depth coding |url=http://phenix.it-sudparis.eu/jvet/doc_end_user/current_document.php?id=10466 |website=JVET document management system |access-date=15 November 2020 |archive-date=11 April 2024 |archive-url=https://web.archive.org/web/20240411164311/http://phenix.it-sudparis.eu/jvet/doc_end_user/current_document.php?id=10466 }}</ref> and was included in the second edition published in 2022. Encoding complexity of several times (up to ten times) that of [[High Efficiency Video Coding|HEVC]] is expected, depending on the quality of the encoding algorithm (which is outside the scope of the standard). The decoding complexity is about twice that of HEVC.


VVC development has been made using the VVC Test Model (VTM), a reference software codebase that was started with a minimal set of coding tools. Further coding tools have been added after being tested in Core Experiments (CEs). Its predecessor was the Joint Exploration Model (JEM), an experimental software codebase that was based on the reference software used for [[High Efficiency Video Coding|HEVC]].
VVC development has been made using the VVC Test Model (VTM), a reference software codebase that was started with a minimal set of coding tools. Further coding tools have been added after being tested in Core Experiments (CEs). Its predecessor was the Joint Exploration Model (JEM), an experimental software codebase that was based on the reference software used for [[High Efficiency Video Coding|HEVC]].


Like its predecessor, VVC uses motion-compensated DCT video coding. While HEVC supports integer [[Discrete cosine transform|discrete cosine transform]] (DCT) square block sizes between 4×4 and 32×32, VVC adds support for non-square DCT rectangular block sizes. VVC also introduces several intra-frame prediction modes based on these rectangular DCT blocks to provide improved [[Motion compensation|motion compensation]] prediction.<ref>{{Cite book |last=Bailey |first=Donald G. |url=https://books.google.com/books?id=4DHOEAAAQBAJ&pg=PA359 |title=Design for Embedded Image Processing on FPGAs |date=2023-08-14 |publisher=[[Company:John Wiley & Sons|John Wiley & Sons]] |isbn=978-1-119-81979-0 |pages=359}}</ref>
Like its predecessor, VVC uses motion-compensated DCT video coding. While HEVC supports integer [[Discrete cosine transform|discrete cosine transform]] (DCT) square block sizes between 4×4 and 32×32, VVC adds support for non-square DCT rectangular block sizes. VVC also introduces several intra-frame prediction modes based on these rectangular DCT blocks to provide improved [[Motion compensation|motion compensation]] prediction.<ref>{{Cite book |last=Bailey |first=Donald G. |url=https://books.google.com/books?id=4DHOEAAAQBAJ&pg=PA359 |title=Design for Embedded Image Processing on FPGAs |date=2023-08-14 |publisher=[[Company:John Wiley & Sons|John Wiley & Sons]] |isbn=978-1-119-81979-0 |page=359}}</ref>


== History ==
== History ==
JVET issued a final Call for Proposals in October 2017, and the standardization process officially began in April 2018 when the first working draft of the standard was produced.<ref>{{Cite web|url=https://mpeg.chiariglione.org/standards/exploration/future-video-coding/n17195-joint-call-proposals-video-compression-capability|title=N17195, Joint Call for Proposals on Video Compression with Capability beyond HEVC|website=mpeg.chiariglione.org|access-date=2019-01-21|archive-date=11 March 2018|archive-url=https://web.archive.org/web/20180311140613/https://mpeg.chiariglione.org/standards/exploration/future-video-coding/n17195-joint-call-proposals-video-compression-capability|url-status=dead}}</ref><ref>{{Cite web|url=https://mpeg.chiariglione.org/standards/mpeg-i/versatilevideo-coding/n17669-working-draft-1-versatile-video-coding|title=N17669, Working Draft 1 of Versatile Video Coding|website=mpeg.chiariglione.org|access-date=2019-08-18|archive-date=18 August 2019|archive-url=https://web.archive.org/web/20190818110718/https://mpeg.chiariglione.org/standards/mpeg-i/versatilevideo-coding/n17669-working-draft-1-versatile-video-coding|url-status=dead}}</ref>
JVET issued a final Call for Proposals in October 2017, and the standardization process officially began in April 2018 when the first working draft of the standard was produced.<ref>{{Cite web|url=https://mpeg.chiariglione.org/standards/exploration/future-video-coding/n17195-joint-call-proposals-video-compression-capability|title=N17195, Joint Call for Proposals on Video Compression with Capability beyond HEVC|website=mpeg.chiariglione.org|access-date=2019-01-21|archive-date=11 March 2018|archive-url=https://web.archive.org/web/20180311140613/https://mpeg.chiariglione.org/standards/exploration/future-video-coding/n17195-joint-call-proposals-video-compression-capability}}</ref><ref>{{Cite web|url=https://mpeg.chiariglione.org/standards/mpeg-i/versatilevideo-coding/n17669-working-draft-1-versatile-video-coding|title=N17669, Working Draft 1 of Versatile Video Coding|website=mpeg.chiariglione.org|access-date=2019-08-18|archive-date=18 August 2019|archive-url=https://web.archive.org/web/20190818110718/https://mpeg.chiariglione.org/standards/mpeg-i/versatilevideo-coding/n17669-working-draft-1-versatile-video-coding}}</ref>


At [[Engineering:International Broadcasting Convention|IBC]] 2018, a preliminary implementation based on VVC was demonstrated that was said to compress video 40% more efficiently than HEVC.<ref>{{Cite web |last=Richter |first=Thomas |date=2018-09-12 |title=Fraunhofer Institut zeigt 50% besseren HEVC Nachfolger VVC auf der // IBC 2018 |url=https://www.slashcam.de/news/single/Fraunhofer-Institut-zeigt-50--besseren-HEVC-Nachfo-14589.html |url-status=live |archive-url=https://web.archive.org/web/20181108065644/https://www.slashcam.de/news/single/Fraunhofer-Institut-zeigt-50--besseren-HEVC-Nachfo-14589.html |archive-date=2018-11-08 |access-date=2019-01-21 |website=slashCAM |language=de}}</ref>
At [[Engineering:International Broadcasting Convention|IBC]] 2018, a preliminary implementation based on VVC was demonstrated that was said to compress video 40% more efficiently than HEVC.<ref>{{Cite web |last=Richter |first=Thomas |date=2018-09-12 |title=Fraunhofer Institut zeigt 50% besseren HEVC Nachfolger VVC auf der // IBC 2018 |url=https://www.slashcam.de/news/single/Fraunhofer-Institut-zeigt-50--besseren-HEVC-Nachfo-14589.html |url-status=live |archive-url=https://web.archive.org/web/20181108065644/https://www.slashcam.de/news/single/Fraunhofer-Institut-zeigt-50--besseren-HEVC-Nachfo-14589.html |archive-date=2018-11-08 |access-date=2019-01-21 |website=slashCAM |language=de}}</ref>
Line 40: Line 41:


* October 2017: Call for proposals
* October 2017: Call for proposals
* April 2018: Evaluation of the proposals received and first draft of the standard<ref>{{cite web |url=http://phenix.int-evry.fr/jvet/doc_end_user/current_document.php?id=3538 |title=JVET-J1001: Versatile Video Coding (Draft 1) |date=April 2018 |access-date=17 October 2019 |archive-date=17 October 2019 |archive-url=https://web.archive.org/web/20191017144509/http://phenix.int-evry.fr/jvet/doc_end_user/current_document.php?id=3538 |url-status=dead }}</ref>
* April 2018: Evaluation of the proposals received and first draft of the standard<ref>{{cite web |url=http://phenix.int-evry.fr/jvet/doc_end_user/current_document.php?id=3538 |title=JVET-J1001: Versatile Video Coding (Draft 1) |date=April 2018 |access-date=17 October 2019 |archive-date=17 October 2019 |archive-url=https://web.archive.org/web/20191017144509/http://phenix.int-evry.fr/jvet/doc_end_user/current_document.php?id=3538 }}</ref>
* July 2019: Ballot issued for committee draft
* July 2019: Ballot issued for committee draft
* October 2019: Ballot issued for draft international standard
* October 2019: Ballot issued for draft international standard
Line 46: Line 47:


== Licensing ==
== Licensing ==
To reduce the risk of the problems seen when licensing [[High Efficiency Video Coding|HEVC]] implementations, for VVC a new group called the Media Coding Industry Forum (MC-IF) was founded.<ref>{{Cite web|url=http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=129386|title=A Video Codec Licensing Update|last=Ozer|first=Jan|date=2019-01-13|website=Streaming Media |access-date=2019-01-21}}</ref><ref>{{Cite web|url=http://www.mc-if.org/|title=MC-IF|website=mc-if|language=en|access-date=2019-01-21}}</ref> However, MC-IF had no power over the standardization process, which was based on technical merit as determined by consensus decisions of JVET.<ref name="ves104">{{cite web |last1=Feldman |first1=Christian |title=Video Engineering Summit East 2019 – AV1/VVC Update |url=http://streamingmedia.brightcovegallery.com/detail/videos/video-engineering-summit-east-2019/video/6036724771001/ves104.-av1-vvc-update |access-date=20 June 2019 |location=New York |date=7 May 2019 |quote=No change to the standardization has been done, so it could theoretically happen that the same thing with HEVC happens again. No measures have been done to prevent that, unfortunately. Also, JVET is not directly responsible; they are just a technical committee. (…) There is the Media Coding Industry Forum (…), but they don't have any real power. |archive-date=20 June 2019 |archive-url=https://web.archive.org/web/20190620232436/http://streamingmedia.brightcovegallery.com/detail/videos/video-engineering-summit-east-2019/video/6036724771001/ves104.-av1-vvc-update |url-status=dead }}</ref>
To reduce the risk of the problems seen when licensing [[High Efficiency Video Coding|HEVC]] implementations, for VVC a new group called the Media Coding Industry Forum (MC-IF) was founded.<ref>{{Cite web|url=http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=129386|title=A Video Codec Licensing Update|last=Ozer|first=Jan|date=2019-01-13|website=Streaming Media |access-date=2019-01-21}}</ref><ref>{{Cite web|url=http://www.mc-if.org/|title=MC-IF|website=mc-if|language=en|access-date=2019-01-21}}</ref> However, MC-IF had no power over the standardization process, which was based on technical merit as determined by consensus decisions of JVET.<ref name="ves104">{{cite web |last1=Feldman |first1=Christian |title=Video Engineering Summit East 2019 – AV1/VVC Update |url=http://streamingmedia.brightcovegallery.com/detail/videos/video-engineering-summit-east-2019/video/6036724771001/ves104.-av1-vvc-update |access-date=20 June 2019 |location=New York |date=7 May 2019 |quote=No change to the standardization has been done, so it could theoretically happen that the same thing with HEVC happens again. No measures have been done to prevent that, unfortunately. Also, JVET is not directly responsible; they are just a technical committee. (…) There is the Media Coding Industry Forum (…), but they don't have any real power. |archive-date=20 June 2019 |archive-url=https://web.archive.org/web/20190620232436/http://streamingmedia.brightcovegallery.com/detail/videos/video-engineering-summit-east-2019/video/6036724771001/ves104.-av1-vvc-update }}</ref>


Four companies were initially vying to be [[Social:Patent pool|patent pool]] administrators for VVC, in a situation similar to the previous AVC<ref>{{Cite web |last1=Siglin |first1=Timothy |date=2009-02-12|title=The H.264 Licensing Labyrinth |url=https://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=65403 |access-date=2020-07-08|website=Streaming Media |language=en-US}}</ref> and HEVC<ref>{{Cite web|date=2020-01-17 |first=Jan |last=Ozer |title=Balance of Power Shifts Among HEVC Patent Pools|url=https://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=136123|access-date=2020-07-08|website=Streaming Media |language=en-US}}</ref> codecs. Two companies later formed patent pools: Access Advance and [[Company:MPEG LA|MPEG LA]] (now known as [[Company:Via-LA|Via-LA]]).<ref>{{Cite web |first=Jan |last=Ozer |url=https://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=144949 |title= VVC Patent Pools: And Then There Were Two |website=Streaming Media |language=en|date=28 January 2021|access-date=2021-02-23}}</ref>
Four companies were initially vying to be [[Social:Patent pool|patent pool]] administrators for VVC, in a situation similar to the previous AVC<ref>{{Cite web |last1=Siglin |first1=Timothy |date=2009-02-12|title=The H.264 Licensing Labyrinth |url=https://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=65403 |access-date=2020-07-08|website=Streaming Media |language=en-US}}</ref> and HEVC<ref>{{Cite web|date=2020-01-17 |first=Jan |last=Ozer |title=Balance of Power Shifts Among HEVC Patent Pools|url=https://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=136123|access-date=2020-07-08|website=Streaming Media |language=en-US}}</ref> codecs. Two companies later formed patent pools: Access Advance and [[Company:MPEG LA|MPEG LA]] (now known as [[Company:Via-LA|Via-LA]]).<ref>{{Cite web |first=Jan |last=Ozer |url=https://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=144949 |title= VVC Patent Pools: And Then There Were Two |website=Streaming Media |language=en|date=28 January 2021|access-date=2021-02-23}}</ref>


Access Advance published their licensing fee in April 2021.<ref>{{Cite web |title=access advance royalties |url=https://accessadvance.com/hevc-advance-patent-pool-detailed-royalty-rates/}}</ref> Via-LA published their licensing fee in January 2022.<ref>{{Cite web |title=via-la licensing fees |work=ViaLa |url=https://www.via-la.com/licensing-2/vvc/vvc-license-fees/ |access-date=17 November 2023 |archive-date=3 December 2024 |archive-url=https://web.archive.org/web/20241203180943/https://www.via-la.com/licensing-2/vvc/vvc-license-fees/ |url-status=dead }}</ref>
Access Advance published their licensing fee in April 2021.<ref>{{Cite web |title=access advance royalties |url=https://accessadvance.com/hevc-advance-patent-pool-detailed-royalty-rates/}}</ref> Via-LA published their licensing fee in January 2022.<ref>{{Cite web |title=via-la licensing fees |work=ViaLa |url=https://www.via-la.com/licensing-2/vvc/vvc-license-fees/ |access-date=17 November 2023 |archive-date=3 December 2024 |archive-url=https://web.archive.org/web/20241203180943/https://www.via-la.com/licensing-2/vvc/vvc-license-fees/ }}</ref>


Companies known not to be a part of the Access Advance or Via-LA patent pools as of May 2025 are: Apple, Broadcom, Canon, Ericsson, Fraunhofer, Google, Huawei, Intel, Interdigital, LG, Maxell, Microsoft, Nokia, Oppo, Qualcomm, Samsung, Sharp and Sony.<ref>{{Cite web |title=access advance companies |url=https://accessadvance.com/vvc-worldwide-patent-landscape/}}</ref> Access Advance promotes a standalone VVC licensing program under the name of VVC Advance, while Via-LA is promoting a combined HEVC/VVC licensing program; until April 2024, Via-LA was licensing VVC standalone.<ref>{{Cite web|date=2024-04-03|title=Via LA Announces Extension of HEVC Patent Pool to Include VVC and Welcomes TCL Into Newly Formed Program|url=https://via-la.com/wp-content/uploads/2025/08/Via-LA-HEVC-VVC-Press-Release.pdf|access-date=2025-11-14}}</ref>
Companies known not to be a part of the Access Advance or Via-LA patent pools as of May 2025 are: Apple, Broadcom, Canon, Ericsson, Fraunhofer, Google, Huawei, Intel, Interdigital, LG, Maxell, Microsoft, Nokia, Oppo, Qualcomm, Samsung, Sharp and Sony.<ref>{{Cite web |title=access advance companies |url=https://accessadvance.com/vvc-worldwide-patent-landscape/}}</ref> Access Advance promotes a standalone VVC licensing program under the name of VVC Advance, while Via-LA is promoting a combined HEVC/VVC licensing program; until April 2024, Via-LA was licensing VVC standalone.<ref>{{Cite web|date=2024-04-03|title=Via LA Announces Extension of HEVC Patent Pool to Include VVC and Welcomes TCL Into Newly Formed Program|url=https://via-la.com/wp-content/uploads/2025/08/Via-LA-HEVC-VVC-Press-Release.pdf|access-date=2025-11-14}}</ref>


In December 2025 Access Advance acquired Via Licensing Alliance’s HEVC and VVC patent pools but that still doesn't resolve the licensing situation because multiple companies beyond the former two patent pools administrators hold patents for the codec.<ref>{{Cite web |last=Hollander |first=Meredith |date=2025-12-15 |title=Access Advance and Via Licensing Alliance Announce HEVC/VVC Program Acquisition |url=https://accessadvance.com/2025/12/15/access-advance-and-via-licensing-alliance-announce-hevc-vvc-program-acquisition/ |access-date=2025-12-26 |website=Access Advance |language=en-US}}</ref><ref>{{Cite web |date=2025-12-15 |title=BREAKING: Access Advance acquires Via Licensing Alliance’s HEVC, VVC patent pools – ip fray |url=https://ipfray.com/breaking-access-advance-acquires-via-licensing-alliances-hevc-vvc-patent-pools/ |access-date=2025-12-26 |language=en-US}}</ref>  
In December 2025 Access Advance acquired Via Licensing Alliance's HEVC and VVC patent pools but that still doesn't resolve the licensing situation because multiple companies beyond the former two patent pools administrators hold patents for the codec.<ref>{{Cite web |last=Hollander |first=Meredith |date=2025-12-15 |title=Access Advance and Via Licensing Alliance Announce HEVC/VVC Program Acquisition |url=https://accessadvance.com/2025/12/15/access-advance-and-via-licensing-alliance-announce-hevc-vvc-program-acquisition/ |access-date=2025-12-26 |website=Access Advance |language=en-US}}</ref><ref>{{Cite web |date=2025-12-15 |title=BREAKING: Access Advance acquires Via Licensing Alliance's HEVC, VVC patent pools – ip fray |url=https://ipfray.com/breaking-access-advance-acquires-via-licensing-alliances-hevc-vvc-patent-pools/ |access-date=2025-12-26 |language=en-US}}</ref>  


== Adoption ==
== Adoption ==
=== Software ===
=== Software ===
'''Operating Systems'''
* Support for the stream format and MIME type was added to [[Software:Android (operating system)|Android]] in version [[Engineering:Android version history|17]]. However, the decoder implementation still needs to be added by an OEM.<ref>{{Cite web |last=Aufranc (CNXSoft) |first=Jean-Luc |date=2026-02-14 |title=Android 17 Beta 1 released with H.266/VCC support, camera improvements, and more - CNX Software |url=https://www.cnx-software.com/2026/02/14/android-17-beta-1-released-with-h-266-vcc-support-camera-improvements-and-more/ |access-date=2026-02-14 |website=CNX Software - Embedded Systems News |language=en-US}}</ref>
'''Encoders/decoders'''
'''Encoders/decoders'''
* Fraunhofer HHI released a source-available<ref group=Note name=Note01/> encoder called VVenC<ref name="VVenC">{{cite web |title=Fraunhofer HHI has developed a software encoder that fully exploits the compression potential of VVC. Its source code is available on GitHub. |url=https://www.hhi.fraunhofer.de/en/departments/vca/technologies-and-solutions/h266-vvc/fraunhofer-versatile-video-encoder-vvenc.html |website=hhi.fraunhofer.de |access-date=29 June 2021 |language=en}}</ref> and decoder called VVdeC<ref name="VVdeC">{{cite web |title=Fraunhofer HHI has developed a resource efficient, multithreaded VVC software decoder that enables live decoding. Its source code is available on GitHub. |url=https://www.hhi.fraunhofer.de/en/departments/vca/technologies-and-solutions/h266-vvc/fraunhofer-versatile-video-decoder-vvdec.html |website=hhi.fraunhofer.de |access-date=29 June 2021 |language=en}}</ref>
* Fraunhofer HHI released a source-available<ref group="Note" name="Note01" /> encoder called VVenC<ref name="VVenC">{{cite web |title=Fraunhofer HHI has developed a software encoder that fully exploits the compression potential of VVC. Its source code is available on GitHub. |url=https://www.hhi.fraunhofer.de/en/departments/vca/technologies-and-solutions/h266-vvc/fraunhofer-versatile-video-encoder-vvenc.html |website=hhi.fraunhofer.de |access-date=29 June 2021 |language=en}}</ref> and decoder called VVdeC<ref name="VVdeC">{{cite web |title=Fraunhofer HHI has developed a resource efficient, multithreaded VVC software decoder that enables live decoding. Its source code is available on GitHub. |url=https://www.hhi.fraunhofer.de/en/departments/vca/technologies-and-solutions/h266-vvc/fraunhofer-versatile-video-decoder-vvdec.html |website=hhi.fraunhofer.de |access-date=29 June 2021 |language=en}}</ref>
** [https://github.com/fraunhoferhhi/vvenc Fraunhofer Versatile Video Encoder (VVenC)]
** [https://github.com/fraunhoferhhi/vvenc Fraunhofer Versatile Video Encoder (VVenC)]
** [https://github.com/fraunhoferhhi/vvdec Fraunhofer Versatile Video Decoder (VVdeC)]
** [https://github.com/fraunhoferhhi/vvdec Fraunhofer Versatile Video Decoder (VVdeC)]
*[https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM VVC VTM reference software]
*[https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM VVC VTM reference software]
* [[Company:Tencent|Tencent]] Media Lab offers a [[On the fly#Computer usage|real time]] decoder<ref>{{cite web |author=[[Company:Tencent|Tencent]] |url=https://multimedia.tencent.com/news/202102011 |title=High performance Real-time H.266/VVC decoder now available from Tencent Media Lab |publisher=Tencent |date=2021-06-22 |language=en |access-date=2021-06-22 |archive-date=22 June 2021 |archive-url=https://web.archive.org/web/20210622112915/https://multimedia.tencent.com/news/202102011 |url-status=dead }}</ref> and the Tencent Cloud service offers transcoding and streaming in its cloud infrastructure.<ref>{{cite web |author=[[Company:Tencent|Tencent]] |url=https://intl.cloud.tencent.com/dynamic/news-details/100152 |title=Tencent Cloud Becomes First Cloud Service Provider to Support H.266/VVC Standard |date=2021-07-16 }}</ref>
* [[Company:Tencent|Tencent]] Media Lab offers a [[On the fly#Computer usage|real time]] decoder<ref>{{cite web |author=[[Company:Tencent|Tencent]] |url=https://multimedia.tencent.com/news/202102011 |title=High performance Real-time H.266/VVC decoder now available from Tencent Media Lab |publisher=Tencent |date=2021-06-22 |language=en |access-date=2021-06-22 |archive-date=22 June 2021 |archive-url=https://web.archive.org/web/20210622112915/https://multimedia.tencent.com/news/202102011 }}</ref> and the Tencent Cloud service offers transcoding and streaming in its cloud infrastructure.<ref>{{cite web |author=[[Company:Tencent|Tencent]] |url=https://intl.cloud.tencent.com/dynamic/news-details/100152 |title=Tencent Cloud Becomes First Cloud Service Provider to Support H.266/VVC Standard |date=2021-07-16 }}</ref>
* Tencent offers an open source O266dec library.<ref>{{Citation |title=TencentCloud/O266player |date=2026-03-20 |url=https://github.com/TencentCloud/O266player |access-date=2026-03-22 |publisher=Tencent Cloud}}</ref>
* [https://github.com/ultravideo/uvg266 uvg266] open source encoder
* [https://github.com/ultravideo/uvg266 uvg266] open source encoder
* [[Software:FFmpeg|ffmpeg]] starting with version 7.0 supports experimental decoding.<ref>{{Cite web |title=FFmpeg |url=https://ffmpeg.org/index.html#news |access-date=2024-04-05 |website=ffmpeg.org}}</ref> Version 7.1 elevated support to official status.<ref>{{Cite web |title=git.videolan.org Git - ffmpeg.git/commitdiff |url=https://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=6df0c5f9f4c3261acf5b0efe43597b9eb765d6b6 |access-date=2024-09-06 |website=git.videolan.org}}</ref> As of July 2025, ffmpeg has two decoders available: one software decoder and one qsv decoder.<ref>{{cite web|url=https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/HEAD:/libavcodec/allcodecs.c|title=HEAD/libavcodec/allcodecs.c|website=git.ffmpeg.org}}</ref>
* [[Software:FFmpeg|ffmpeg]] starting with version 7.0 supports experimental decoding.<ref>{{Cite web |title=FFmpeg |url=https://ffmpeg.org/index.html#news |access-date=2024-04-05 |website=ffmpeg.org}}</ref> Version 7.1 elevated support to official status.<ref>{{Cite web |title=git.videolan.org Git - ffmpeg.git/commitdiff |url=https://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=6df0c5f9f4c3261acf5b0efe43597b9eb765d6b6 |access-date=2024-09-06 |website=git.videolan.org}}</ref> As of July 2025, ffmpeg has two decoders available: one software decoder and one qsv decoder.<ref>{{cite web|url=https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/HEAD:/libavcodec/allcodecs.c|title=HEAD/libavcodec/allcodecs.c|website=git.ffmpeg.org}}</ref>
Line 97: Line 101:
|Encoder IP core
|Encoder IP core
|
|
|<ref>{{Cite web |title=Allegro DVT Launches The Industry's First Real-Time VVC/H.266 Encoder IP |url=https://www.afp.com/en/news/1313/allegro-dvt-launches-industrys-first-real-time-vvc/h266-encoder-ip-202407166576681 |access-date=2024-07-17 |website=AFP.com |date=17 April 2012 |language=en |archive-date=17 July 2024 |archive-url=https://web.archive.org/web/20240717130657/https://www.afp.com/en/news/1313/allegro-dvt-launches-industrys-first-real-time-vvc/h266-encoder-ip-202407166576681 |url-status=dead }}</ref><ref>{{Cite web |title=Allegro DVT Launches The Industry's First Real-Time VVC/H.266 Encoder IP |url=https://www.allegrodvt.com/news/allegro-dvt-industrys-real-time-vvc-h-266-encoder-ip/ |access-date=2024-07-17 |website=www.allegrodvt.com |language=en-US}}</ref>
|<ref>{{Cite web |title=Allegro DVT Launches The Industry's First Real-Time VVC/H.266 Encoder IP |url=https://www.afp.com/en/news/1313/allegro-dvt-launches-industrys-first-real-time-vvc/h266-encoder-ip-202407166576681 |access-date=2024-07-17 |website=AFP.com |date=17 April 2012 |language=en |archive-date=17 July 2024 |archive-url=https://web.archive.org/web/20240717130657/https://www.afp.com/en/news/1313/allegro-dvt-launches-industrys-first-real-time-vvc/h266-encoder-ip-202407166576681 }}</ref><ref>{{Cite web |title=Allegro DVT Launches The Industry's First Real-Time VVC/H.266 Encoder IP |url=https://www.allegrodvt.com/news/allegro-dvt-industrys-real-time-vvc-h-266-encoder-ip/ |access-date=2024-07-17 |website=www.allegrodvt.com |language=en-US}}</ref>
|-
|-
|[[Company:Amlogic|Amlogic]]
|[[Company:Amlogic|Amlogic]]
Line 115: Line 119:
| rowspan="2" |iGPU
| rowspan="2" |iGPU
|
|
|<ref>{{Cite web |last=Bonshor |first=Gavin |title=Intel Unveils Lunar Lake Architecture: New P and E cores, Xe2-LPG Graphics, New NPU 4 Brings More AI Performance |url=https://www.anandtech.com/show/21425/intel-lunar-lake-architecture-deep-dive-lion-cove-xe2-and-npu4 |archive-url=https://web.archive.org/web/20240604032237/https://www.anandtech.com/show/21425/intel-lunar-lake-architecture-deep-dive-lion-cove-xe2-and-npu4 |url-status=dead |archive-date=4 June 2024 |access-date=2024-06-04 |website=www.anandtech.com}}</ref><ref>{{Cite web |last=M. (Intel) |first=Von |date=2025-06-26 |title=Arc B-series support VVC (H.266) decoding? |url=https://community.intel.com/t5/Graphics/Arc-B-series-support-VVC-H-266-decoding/m-p/1700117#M143408 |access-date=2025-08-22 |website=Intel Community |language=en-US}}</ref><ref>{{Cite web |date=2025-06-26 |title=Intel(R) Media Driver for VAAPI - README |url=https://github.com/intel/media-driver/blob/aa4aafccd9f58bb53c959faf453015dccdba8ca5/README.md |access-date=2025-08-22 |website=GitHub |publisher=Intel |language=en-US}}</ref>
|<ref>{{Cite web |last=Bonshor |first=Gavin |title=Intel Unveils Lunar Lake Architecture: New P and E cores, Xe2-LPG Graphics, New NPU 4 Brings More AI Performance |url=https://www.anandtech.com/show/21425/intel-lunar-lake-architecture-deep-dive-lion-cove-xe2-and-npu4 |archive-url=https://web.archive.org/web/20240604032237/https://www.anandtech.com/show/21425/intel-lunar-lake-architecture-deep-dive-lion-cove-xe2-and-npu4 |archive-date=4 June 2024 |access-date=2024-06-04 |website=www.anandtech.com}}</ref><ref>{{Cite web |last=M. (Intel) |first=Von |date=2025-06-26 |title=Arc B-series support VVC (H.266) decoding? |url=https://community.intel.com/t5/Graphics/Arc-B-series-support-VVC-H-266-decoding/m-p/1700117#M143408 |access-date=2025-08-22 |website=Intel Community |language=en-US}}</ref><ref>{{Cite web |date=2025-06-26 |title=Intel(R) Media Driver for VAAPI - README |url=https://github.com/intel/media-driver/blob/aa4aafccd9f58bb53c959faf453015dccdba8ca5/README.md |access-date=2025-08-22 |website=GitHub |publisher=Intel |language=en-US}}</ref>
|-
|-
|[[Intel Xe#Intel Xe 3|Xe3]]
|[[Intel Xe#Intel Xe 3|Xe3]]
|
|
|<ref>{{Cite web |last=Cunningham |first=Andrew |date=2025-10-09 |title=Intel’s next-generation Panther Lake laptop chips could be a return to form |url=https://arstechnica.com/gadgets/2025/10/intels-next-generation-panther-lake-laptop-chips-could-be-a-return-to-form/ |access-date=2025-10-09 |website=Ars Technica |language=en}}</ref>
|<ref>{{Cite web |last=Cunningham |first=Andrew |date=2025-10-09 |title=Intel's next-generation Panther Lake laptop chips could be a return to form |url=https://arstechnica.com/gadgets/2025/10/intels-next-generation-panther-lake-laptop-chips-could-be-a-return-to-form/ |access-date=2025-10-09 |website=Ars Technica |language=en}}</ref>
|-
|-
| rowspan="4" |[[Company:MediaTek|MediaTek]]
| rowspan="4" |[[Company:MediaTek|MediaTek]]
Line 141: Line 145:
|Set-top box [[System on a chip|SoC]]
|Set-top box [[System on a chip|SoC]]
|4K@60
|4K@60
|<ref>{{Cite web |date=2022-08-29 |title=Realtek Launches World's First 4K UHD Set-top Box SoC (RTD1319D) Supports VVC/H.266 Video Decoding, GPU with 10-bit Graphics, Multiple CAS, and HDMI 2.1a |url=https://www.realtek.com/en/press-room/news-releases/item/realtek-launches-world-s-first-4k-uhd-set-top-box-soc-rtd1319d|url-status=dead|archive-url=https://web.archive.org/web/20220905050125/https://www.realtek.com/en/press-room/news-releases/item/realtek-launches-world-s-first-4k-uhd-set-top-box-soc-rtd1319d|archive-date=2022-09-05 |access-date=2022-09-05 |website=Realtek}}</ref>
|<ref>{{Cite web |date=2022-08-29 |title=Realtek Launches World's First 4K UHD Set-top Box SoC (RTD1319D) Supports VVC/H.266 Video Decoding, GPU with 10-bit Graphics, Multiple CAS, and HDMI 2.1a |url=https://www.realtek.com/en/press-room/news-releases/item/realtek-launches-world-s-first-4k-uhd-set-top-box-soc-rtd1319d|archive-url=https://web.archive.org/web/20220905050125/https://www.realtek.com/en/press-room/news-releases/item/realtek-launches-world-s-first-4k-uhd-set-top-box-soc-rtd1319d|archive-date=2022-09-05 |access-date=2022-09-05 |website=Realtek}}</ref>
|-
|-
| rowspan="2" |VeriSilicon
| rowspan="2" |VeriSilicon
Line 154: Line 158:


=== Broadcast ===
=== Broadcast ===
The Brazilian SBTVD Forum adopted the MPEG-I VVC codec in broadcast television system, [[Engineering:ATSC 3.0|TV 3.0]], launched in August 2025.<ref>{{Cite web |date=2022-03-29 |title=Brazil adopts TV 3.0 with many component technologies described in the Ultra HD Forum’s Guidelines |url=https://ultrahdforum.org/brazil-adopts-tv-3-0-with-many-component-technologies-described-in-the-ultra-hd-forums-guidelines/ |access-date=2026-01-05 |website=Ultra HD Forum |language=en-US}}</ref><ref>{{Cite web |title=Fórum SBTVD {{!}} TV 3.0 Project |url=https://forumsbtvd.org.br/tv3_0/ |access-date=2026-01-05 |language=pt-BR}}</ref><ref>{{Cite web |last=266 |date=2025-08-25 |title=Brazil Broadcasting New Digital TV Standard |url=https://www.trade.gov/market-intelligence/brazil-broadcasting-new-digital-tv-standard |access-date=2026-01-05 |website=www.trade.gov |language=en}}</ref><ref>{{Cite web |last=V-Nova |date=2025-11-09 |title=Powering Brazil’s next-generation UHD with TV 3.0 |url=https://v-nova.com/whitepapers/powering-brazils-next-generation-uhd-with-tv-3-0/ |access-date=2026-01-05 |website=V-Nova |language=en-US}}</ref> It is used alongside [[LCEVC|MPEG-5 LCEVC]] as a video base layer encoder for broadcast and [[Engineering:Broadband|broadband]] delivery.<ref>{{cite web |url=https://www.digitalmediaworld.tv/broadcast/4118-brazilian-sbtvd-forum-selects-v-nova-lcevc-for-brazil-s-upcoming-tv-3-0|website=digitalmediaworld.tv|title=Brazilian SBTVD Forum Selects V-Nova LCEVC for Brazil's Upcoming TV 3.0|date=2022-01-13 }}</ref>
The Brazilian SBTVD Forum adopted the MPEG-I VVC codec in broadcast television system, [[Engineering:ATSC 3.0|TV 3.0]], launched in August 2025.<ref>{{Cite web |date=2022-03-29 |title=Brazil adopts TV 3.0 with many component technologies described in the Ultra HD Forum's Guidelines |url=https://ultrahdforum.org/brazil-adopts-tv-3-0-with-many-component-technologies-described-in-the-ultra-hd-forums-guidelines/ |access-date=2026-01-05 |website=Ultra HD Forum |language=en-US}}</ref><ref>{{Cite web |website=Fórum SBTVD |title=TV 3.0 Project |url=https://forumsbtvd.org.br/tv3_0/ |access-date=2026-01-05 |language=pt-BR}}</ref><ref>{{Cite web |date=2025-08-25 |title=Brazil Broadcasting New Digital TV Standard |url=https://www.trade.gov/market-intelligence/brazil-broadcasting-new-digital-tv-standard |access-date=2026-01-05 |website=International Trade Administration |language=en}}</ref><ref>{{Cite web |last=V-Nova |date=2025-11-09 |title=Powering Brazil's next-generation UHD with TV 3.0 |url=https://v-nova.com/whitepapers/powering-brazils-next-generation-uhd-with-tv-3-0/ |access-date=2026-01-05 |website=V-Nova |language=en-US}}</ref> It is used alongside [[LCEVC|MPEG-5 LCEVC]] as a video base layer encoder for broadcast and [[Engineering:Broadband|broadband]] delivery.<ref>{{cite web |url=https://www.digitalmediaworld.tv/broadcast/4118-brazilian-sbtvd-forum-selects-v-nova-lcevc-for-brazil-s-upcoming-tv-3-0|website=digitalmediaworld.tv|title=Brazilian SBTVD Forum Selects V-Nova LCEVC for Brazil's Upcoming TV 3.0|date=2022-01-13 }}</ref>


The European organization DVB Project, which governs [[Engineering:Digital television|digital television]] broadcasting [[Technical standard|standard]]s, announced 24 February 2022 that VVC was now part of its tools for broadcasting.<ref>{{cite web |url=https://www.avcaesar.com/news/1781/dvb-adds-the-vvc-h266-codec-to-its-video-standards-for-8k|title=DVB adds the VVC (H.266) codec to its video standards, for 8K?|date=2022-02-24 }}</ref>
The European organization DVB Project, which governs [[Engineering:Digital television|digital television]] broadcasting [[Technical standard|standard]]s, announced 24 February 2022 that VVC was now part of its tools for broadcasting.<ref>{{cite web |url=https://www.avcaesar.com/news/1781/dvb-adds-the-vvc-h266-codec-to-its-video-standards-for-8k|title=DVB adds the VVC (H.266) codec to its video standards, for 8K?|date=2022-02-24 }}</ref>
Line 161: Line 165:
== See also ==
== See also ==
* [[Software:AV1|AOMedia Video 1 (AV1)]]
* [[Software:AV1|AOMedia Video 1 (AV1)]]
* [[Engineering:AV2|AV2]]
* [[Layered coding|Scalable coding]]
* [[Layered coding|Scalable coding]]
* [[Essential Video Coding]]
* [[Essential Video Coding]]

Latest revision as of 00:54, 14 April 2026

Short description: Video compression standard
VVC / H.266 / MPEG-I Part 3
Versatile video coding
StatusIn force
Year started2017
First published2020
Latest version4th Edition[1]
13 January 2026
OrganizationITU-T, ISO, IEC
CommitteeSG16 (Secretary: Simao Campos) (VCEG), MPEG
Base standardsH.261, H.262, H.263, H.264, H.265, ISO/IEC 14496-2, MPEG-1
DomainVideo compression
LicenseRAND
Websitewww.itu.int/rec/T-REC-H.266

Versatile Video Coding (VVC), also known as H.266,[2] ISO/IEC 23090-3,[3] and MPEG-I Part 3, is a video compression standard finalized on 6 July 2020, by the Joint Video Experts Team (JVET)[4] of the VCEG working group of ITU-T Study Group 16 and the MPEG working group of ISO/IEC JTC 1/SC 29. It is the successor to High Efficiency Video Coding (HEVC, also known as ITU-T H.265 and MPEG-H Part 2). It was developed with two primary goals – improved compression performance and support for a very broad range of applications.[5][6][7]

Concept

In October 2015, the MPEG and VCEG formed the Joint Video Exploration Team (JVET) to evaluate available compression technologies and study the requirements for a next-generation video compression standard. The new standard has about 50% better compression rate for the same perceptual quality compared to HEVC,[8] with support for lossless and lossy compression. It supports resolutions ranging from very low resolution up to 4K and 16K as well as 360° videos. VVC supports YCbCr 4:4:4, 4:2:2 and 4:2:0 with 8–10 bits per component, BT.2100 wide color gamut and high dynamic range (HDR) of more than 16 stops (with peak brightness of 1,000, 4,000 and 10,000 nits),[clarification needed] auxiliary channels (for depth, transparency, etc.), variable and fractional frame rates from 0 to 120 Hz and higher, scalable video coding for temporal (frame rate), spatial (resolution), SNR, color gamut and dynamic range differences, stereo/multiview coding, panoramic formats, and still-picture coding. Work on high bit depth support (12 to 16 bits per component) started in October 2020[9] and was included in the second edition published in 2022. Encoding complexity of several times (up to ten times) that of HEVC is expected, depending on the quality of the encoding algorithm (which is outside the scope of the standard). The decoding complexity is about twice that of HEVC.

VVC development has been made using the VVC Test Model (VTM), a reference software codebase that was started with a minimal set of coding tools. Further coding tools have been added after being tested in Core Experiments (CEs). Its predecessor was the Joint Exploration Model (JEM), an experimental software codebase that was based on the reference software used for HEVC.

Like its predecessor, VVC uses motion-compensated DCT video coding. While HEVC supports integer discrete cosine transform (DCT) square block sizes between 4×4 and 32×32, VVC adds support for non-square DCT rectangular block sizes. VVC also introduces several intra-frame prediction modes based on these rectangular DCT blocks to provide improved motion compensation prediction.[10]

History

JVET issued a final Call for Proposals in October 2017, and the standardization process officially began in April 2018 when the first working draft of the standard was produced.[11][12]

At IBC 2018, a preliminary implementation based on VVC was demonstrated that was said to compress video 40% more efficiently than HEVC.[13]

The content of the final standard was approved on 6 July 2020.[8][14][15]

Schedule

  • October 2017: Call for proposals
  • April 2018: Evaluation of the proposals received and first draft of the standard[16]
  • July 2019: Ballot issued for committee draft
  • October 2019: Ballot issued for draft international standard
  • 6 July 2020: Completion of final standard

Licensing

To reduce the risk of the problems seen when licensing HEVC implementations, for VVC a new group called the Media Coding Industry Forum (MC-IF) was founded.[17][18] However, MC-IF had no power over the standardization process, which was based on technical merit as determined by consensus decisions of JVET.[19]

Four companies were initially vying to be patent pool administrators for VVC, in a situation similar to the previous AVC[20] and HEVC[21] codecs. Two companies later formed patent pools: Access Advance and MPEG LA (now known as Via-LA).[22]

Access Advance published their licensing fee in April 2021.[23] Via-LA published their licensing fee in January 2022.[24]

Companies known not to be a part of the Access Advance or Via-LA patent pools as of May 2025 are: Apple, Broadcom, Canon, Ericsson, Fraunhofer, Google, Huawei, Intel, Interdigital, LG, Maxell, Microsoft, Nokia, Oppo, Qualcomm, Samsung, Sharp and Sony.[25] Access Advance promotes a standalone VVC licensing program under the name of VVC Advance, while Via-LA is promoting a combined HEVC/VVC licensing program; until April 2024, Via-LA was licensing VVC standalone.[26]

In December 2025 Access Advance acquired Via Licensing Alliance's HEVC and VVC patent pools but that still doesn't resolve the licensing situation because multiple companies beyond the former two patent pools administrators hold patents for the codec.[27][28]

Adoption

Software

Operating Systems

  • Support for the stream format and MIME type was added to Android in version 17. However, the decoder implementation still needs to be added by an OEM.[29]

Encoders/decoders

Players

Hardware

Company Chip/architecture Type Throughput Ref
Allegro DVT AL-D320 Decoder IP core 8K@120 [47][48]
AL-E320 Encoder IP core [49][50]
Amlogic S905X5 Set-top box SoC 2x 4K@60 10 bit [51]
Chips&Media WAVE6 Gen2+ Decoder IP core 8K@30 [52]
Intel Xe2-LPG iGPU [53][54][55]
Xe3 [56]
MediaTek Pentonic 2000 SoC for TV sets 8K@120 [57]
Pentonic 1000 4K@144 [58]
Pentonic 800 [59]
Pentonic 700 [60]
Realtek RTD1319D Set-top box SoC 4K@60 [61]
VeriSilicon Hantro VC9000D Decoder 8K@120 [62]
Hantro VC9800D [63]

Broadcast

The Brazilian SBTVD Forum adopted the MPEG-I VVC codec in broadcast television system, TV 3.0, launched in August 2025.[64][65][66][67] It is used alongside MPEG-5 LCEVC as a video base layer encoder for broadcast and broadband delivery.[68]

The European organization DVB Project, which governs digital television broadcasting standards, announced 24 February 2022 that VVC was now part of its tools for broadcasting.[69] The DVB tuner specification used throughout Europe, Australia, and many other regions has been revised to support the VVC (H.266) video codec, the successor to HEVC.[70]

See also

Notes

  1. ↑ License withholds patent rights and is not OSI-approved.

References

  1. ↑ https://www.itu.int/rec/T-REC-H.266-202601-P/en
  2. ↑ "H.266: Versatile video coding". https://www.itu.int/rec/T-REC-H.266. 
  3. ↑ "Information technology — Coded representation of immersive media — Part 3: Versatile video coding" (in en). September 2022. https://www.iso.org/standard/83531.html. 
  4. ↑ "JVET - Joint Video Experts Team". https://www.itu.int/en/ITU-T/studygroups/2017-2020/16/Pages/video/jvet.aspx. 
  5. ↑ Bross, Benjamin; Chen, Jianle; Ohm, Jens-Rainer; Sullivan, Gary J.; Wang, Ye-Kui (September 2021). "Developments in International Video Coding Standardization After AVC, With an Overview of Versatile Video Coding (VVC)". Proceedings of the IEEE 109 (9): 1463–1493. doi:10.1109/JPROC.2020.3043399. 
  6. ↑ Bross, Benjamin; Wang, Ye-Kui; Ye, Yan; Liu, Shan; Sullivan, Gary J.; Ohm, Jens-Rainer (October 2021). "Overview of the Versatile Video Coding (VVC) Standard and its Applications". IEEE Transactions on Circuits and Systems for Video Technology 31 (10): 3736–3764. doi:10.1109/TCSVT.2021.3101953. Bibcode: 2021ITCSV..31.3736B. 
  7. ↑ Boyce, Jill M.; Chen, Jianle; Liu, Shan; Ohm, Jens-Rainer; Sullivan, Gary J.; Wiegand, Thomas; Ye, Yan; Zhu, Wenwu (October 2021). "Guest Editorial Introduction to the Special Section on the VVC Standard". IEEE Transactions on Circuits and Systems for Video Technology 31 (10): 3731–3735. doi:10.1109/TCSVT.2021.3111712. Bibcode: 2021ITCSV..31.3731B. 
  8. ↑ 8.0 8.1 "Fraunhofer HHI is proud to present the new state-of-the-art in global video coding: H.266/VVC brings video transmission to new speeds". July 6, 2020. https://newsletter.fraunhofer.de/-viewonline2/17386/465/11/14SHcBTt/V44RELLZBp/1. 
  9. ↑ "AHG12: VVC coding tool evaluation for high bit-depth coding". http://phenix.it-sudparis.eu/jvet/doc_end_user/current_document.php?id=10466. 
  10. ↑ Bailey, Donald G. (2023-08-14). Design for Embedded Image Processing on FPGAs. John Wiley & Sons. p. 359. ISBN 978-1-119-81979-0. https://books.google.com/books?id=4DHOEAAAQBAJ&pg=PA359. 
  11. ↑ "N17195, Joint Call for Proposals on Video Compression with Capability beyond HEVC". https://mpeg.chiariglione.org/standards/exploration/future-video-coding/n17195-joint-call-proposals-video-compression-capability. 
  12. ↑ "N17669, Working Draft 1 of Versatile Video Coding". https://mpeg.chiariglione.org/standards/mpeg-i/versatilevideo-coding/n17669-working-draft-1-versatile-video-coding. 
  13. ↑ Richter, Thomas (2018-09-12). "Fraunhofer Institut zeigt 50% besseren HEVC Nachfolger VVC auf der // IBC 2018" (in de). https://www.slashcam.de/news/single/Fraunhofer-Institut-zeigt-50--besseren-HEVC-Nachfo-14589.html. 
  14. ↑ "Versatile Video Coding | MPEG". https://mpeg.chiariglione.org/standards/mpeg-i/versatile-video-coding. 
  15. ↑ ITU (2018-04-27). "Beyond HEVC: Versatile Video Coding project starts strongly in Joint Video Experts Team" (in en). https://news.itu.int/versatile-video-coding-project-starts-strongly/. 
  16. ↑ "JVET-J1001: Versatile Video Coding (Draft 1)". April 2018. http://phenix.int-evry.fr/jvet/doc_end_user/current_document.php?id=3538. 
  17. ↑ Ozer, Jan (2019-01-13). "A Video Codec Licensing Update". http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=129386. 
  18. ↑ "MC-IF" (in en). http://www.mc-if.org/. 
  19. ↑ Feldman, Christian (7 May 2019). "Video Engineering Summit East 2019 – AV1/VVC Update". New York. http://streamingmedia.brightcovegallery.com/detail/videos/video-engineering-summit-east-2019/video/6036724771001/ves104.-av1-vvc-update. "No change to the standardization has been done, so it could theoretically happen that the same thing with HEVC happens again. No measures have been done to prevent that, unfortunately. Also, JVET is not directly responsible; they are just a technical committee. (…) There is the Media Coding Industry Forum (…), but they don't have any real power." 
  20. ↑ Siglin, Timothy (2009-02-12). "The H.264 Licensing Labyrinth" (in en-US). https://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=65403. 
  21. ↑ Ozer, Jan (2020-01-17). "Balance of Power Shifts Among HEVC Patent Pools" (in en-US). https://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=136123. 
  22. ↑ Ozer, Jan (28 January 2021). "VVC Patent Pools: And Then There Were Two" (in en). https://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=144949. 
  23. ↑ "access advance royalties". https://accessadvance.com/hevc-advance-patent-pool-detailed-royalty-rates/. 
  24. ↑ "via-la licensing fees". ViaLa. https://www.via-la.com/licensing-2/vvc/vvc-license-fees/. 
  25. ↑ "access advance companies". https://accessadvance.com/vvc-worldwide-patent-landscape/. 
  26. ↑ "Via LA Announces Extension of HEVC Patent Pool to Include VVC and Welcomes TCL Into Newly Formed Program". 2024-04-03. https://via-la.com/wp-content/uploads/2025/08/Via-LA-HEVC-VVC-Press-Release.pdf. 
  27. ↑ Hollander, Meredith (2025-12-15). "Access Advance and Via Licensing Alliance Announce HEVC/VVC Program Acquisition" (in en-US). https://accessadvance.com/2025/12/15/access-advance-and-via-licensing-alliance-announce-hevc-vvc-program-acquisition/. 
  28. ↑ "BREAKING: Access Advance acquires Via Licensing Alliance's HEVC, VVC patent pools – ip fray" (in en-US). 2025-12-15. https://ipfray.com/breaking-access-advance-acquires-via-licensing-alliances-hevc-vvc-patent-pools/. 
  29. ↑ Aufranc (CNXSoft), Jean-Luc (2026-02-14). "Android 17 Beta 1 released with H.266/VCC support, camera improvements, and more - CNX Software" (in en-US). https://www.cnx-software.com/2026/02/14/android-17-beta-1-released-with-h-266-vcc-support-camera-improvements-and-more/. 
  30. ↑ "Fraunhofer HHI has developed a software encoder that fully exploits the compression potential of VVC. Its source code is available on GitHub." (in en). https://www.hhi.fraunhofer.de/en/departments/vca/technologies-and-solutions/h266-vvc/fraunhofer-versatile-video-encoder-vvenc.html. 
  31. ↑ "Fraunhofer HHI has developed a resource efficient, multithreaded VVC software decoder that enables live decoding. Its source code is available on GitHub." (in en). https://www.hhi.fraunhofer.de/en/departments/vca/technologies-and-solutions/h266-vvc/fraunhofer-versatile-video-decoder-vvdec.html. 
  32. ↑ Tencent (2021-06-22). "High performance Real-time H.266/VVC decoder now available from Tencent Media Lab" (in en). Tencent. https://multimedia.tencent.com/news/202102011. 
  33. ↑ Tencent (2021-07-16). "Tencent Cloud Becomes First Cloud Service Provider to Support H.266/VVC Standard". https://intl.cloud.tencent.com/dynamic/news-details/100152. 
  34. ↑ TencentCloud/O266player, Tencent Cloud, 2026-03-20, https://github.com/TencentCloud/O266player, retrieved 2026-03-22 
  35. ↑ "FFmpeg". https://ffmpeg.org/index.html#news. 
  36. ↑ "git.videolan.org Git - ffmpeg.git/commitdiff". https://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=6df0c5f9f4c3261acf5b0efe43597b9eb765d6b6. 
  37. ↑ "HEAD/libavcodec/allcodecs.c". https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/HEAD:/libavcodec/allcodecs.c. 
  38. ↑ "Release 0.79 · Nevcairiel/LAVFilters" (in en). https://github.com/Nevcairiel/LAVFilters/releases/tag/0.79. 
  39. ↑ "Project" (in en-US). https://openvvc.github.io/. 
  40. ↑ OpenVVC/OpenVVC, OpenVVC, 2024-07-27, https://github.com/OpenVVC/OpenVVC, retrieved 2024-08-25 
  41. ↑ "Real-time VVC and HEVC Encoder | Spin Enc Live". https://spin-digital.com/products/spin_enc_live/. 
  42. ↑ "Spin Digital – 8K VVC Media Player (Spin Player VVC)" (in en-US). Spin Digital. https://spin-digital.com/products/spin-player-vvc/. 
  43. ↑ Rudd, Emilia. "Elmedia Player for Mac Version History | KB" (in en). https://help.electronic.us/support/solutions/articles/44002280353-elmedia-player-from-the-electronic-team-website. 
  44. ↑ "Release 2.2.0 · clsid2/mpc-hc" (in en). https://github.com/clsid2/mpc-hc/releases/tag/2.2.0. 
  45. ↑ "Release MPC-BE 1.7.0 · Aleksoid1978/MPC-BE" (in en). https://github.com/Aleksoid1978/MPC-BE/releases/tag/1.7.0. 
  46. ↑ "Steam :: Zoom Player Steam Edition :: Announcing Zoom Player v19 beta 6" (in en). 2024-04-12. https://store.steampowered.com/news/app/269550/view/5849687862875040134. 
  47. ↑ "IP Decoder AV1 8K IP Video Multiformats AV1 422 Scalable" (in en-US). Allegro DVT - Leading Video Compression Expertise. https://www.allegrodvt.com/video-ip-compliance-streams/video-silicon-ip-cores/ip-decoder-multi-formats-8k-d320/. 
  48. ↑ "First hardware VVC/H.266 video decoder IP core" (in en). 2021-07-01. https://www.eenewseurope.com/news/first-hardware-vvch266-video-decoder-ip-core. 
  49. ↑ "Allegro DVT Launches The Industry's First Real-Time VVC/H.266 Encoder IP" (in en). 17 April 2012. https://www.afp.com/en/news/1313/allegro-dvt-launches-industrys-first-real-time-vvc/h266-encoder-ip-202407166576681. 
  50. ↑ "Allegro DVT Launches The Industry's First Real-Time VVC/H.266 Encoder IP" (in en-US). https://www.allegrodvt.com/news/allegro-dvt-industrys-real-time-vvc-h-266-encoder-ip/. 
  51. ↑ Aufranc (CNXSoft), Jean-Luc (2023-09-18). "Amlogic S905X5 Armv9 TV Box SoC supports AV1, H.266, Ai-SR - CNX Software" (in en-US). https://www.cnx-software.com/2023/09/18/amlogic-s905x5-armv9-tv-box-soc-av1-h-266-ai-sr/. 
  52. ↑ "Silicon IP Provider, Chips&Media Unveils New Multi Video Codec IP, WAVE6 Gen2+". https://www.design-reuse.com/news/11590-silicon-ip-provider-chips-media-unveils-new-multi-video-codec-ip-wave6-gen2-/. 
  53. ↑ Bonshor, Gavin. "Intel Unveils Lunar Lake Architecture: New P and E cores, Xe2-LPG Graphics, New NPU 4 Brings More AI Performance". https://www.anandtech.com/show/21425/intel-lunar-lake-architecture-deep-dive-lion-cove-xe2-and-npu4. 
  54. ↑ M. (Intel), Von (2025-06-26). "Arc B-series support VVC (H.266) decoding?" (in en-US). https://community.intel.com/t5/Graphics/Arc-B-series-support-VVC-H-266-decoding/m-p/1700117#M143408. 
  55. ↑ "Intel(R) Media Driver for VAAPI - README" (in en-US). Intel. 2025-06-26. https://github.com/intel/media-driver/blob/aa4aafccd9f58bb53c959faf453015dccdba8ca5/README.md. 
  56. ↑ Cunningham, Andrew (2025-10-09). "Intel's next-generation Panther Lake laptop chips could be a return to form" (in en). https://arstechnica.com/gadgets/2025/10/intels-next-generation-panther-lake-laptop-chips-could-be-a-return-to-form/. 
  57. ↑ MediaTek. "MediaTek Announces New Pentonic Smart TV Family with New Pentonic 2000 for Flagship 8K 120Hz TVs". www.prnewswire.com (Press release). Retrieved 2021-11-20.
  58. ↑ de Looper, Christian (2022-11-10). "MediaTek wants to power next-generation TVs and Chromebooks". https://bgr.com/tech/mediatek-wants-to-power-your-next-tv/. 
  59. ↑ "MediaTek Kompanio 838 and Pentonic 800 chipsets announced". https://www.fonearena.com/blog/425496/mediatek-kompanio-838-pentonic-800-features.html. 
  60. ↑ Roy, Avik (2022-08-20). "MediaTek launches Pentonic 700 chip for 4K televisions". https://technosports.co.in/2022/08/20/mediatek-launches-pentonic-700/. 
  61. ↑ "Realtek Launches World's First 4K UHD Set-top Box SoC (RTD1319D) Supports VVC/H.266 Video Decoding, GPU with 10-bit Graphics, Multiple CAS, and HDMI 2.1a". 2022-08-29. https://www.realtek.com/en/press-room/news-releases/item/realtek-launches-world-s-first-4k-uhd-set-top-box-soc-rtd1319d. 
  62. ↑ "VeriSilicon delivered multi-format hardware video decoder Hantro VC9000D supporting 8K@120FPS VVC/H.266 to customers". https://www.verisilicon.com/en/PressRelease/HantroVC9000D. 
  63. ↑ "Hantro VC9800D". https://www.verisilicon.com/en/IPPortfolio/HantroVC9800D. 
  64. ↑ "Brazil adopts TV 3.0 with many component technologies described in the Ultra HD Forum's Guidelines" (in en-US). 2022-03-29. https://ultrahdforum.org/brazil-adopts-tv-3-0-with-many-component-technologies-described-in-the-ultra-hd-forums-guidelines/. 
  65. ↑ "TV 3.0 Project" (in pt-BR). https://forumsbtvd.org.br/tv3_0/. 
  66. ↑ "Brazil Broadcasting New Digital TV Standard" (in en). 2025-08-25. https://www.trade.gov/market-intelligence/brazil-broadcasting-new-digital-tv-standard. 
  67. ↑ V-Nova (2025-11-09). "Powering Brazil's next-generation UHD with TV 3.0" (in en-US). https://v-nova.com/whitepapers/powering-brazils-next-generation-uhd-with-tv-3-0/. 
  68. ↑ "Brazilian SBTVD Forum Selects V-Nova LCEVC for Brazil's Upcoming TV 3.0". 2022-01-13. https://www.digitalmediaworld.tv/broadcast/4118-brazilian-sbtvd-forum-selects-v-nova-lcevc-for-brazil-s-upcoming-tv-3-0. 
  69. ↑ "DVB adds the VVC (H.266) codec to its video standards, for 8K?". 2022-02-24. https://www.avcaesar.com/news/1781/dvb-adds-the-vvc-h266-codec-to-its-video-standards-for-8k. 
  70. ↑ "Next-gen video codec VVC (H.266) added to DVB tuner specification". 2022-02-28. https://www.flatpanelshd.com/news.php?subaction=showfull&id=1646046959. 

Further reading



Retrieved from "https://handwiki.org/wiki/index.php?title=Versatile_Video_Coding&oldid=4296288"