When will H.266 be added?

[Hello]

Will H.266 aka vvc (versatile video codec) be added in VLC media player and if so, when? Does anyone know how long it takes about FFmpeg? I guess 1.5 years.

[Rémi Denis-Courmont]

Not until the bit stream is frozen.

[Hello]

How can I see or assess this?

[Rémi Denis-Courmont]

Not through this forum for sure.

[Sirchwe]

Not until the bit stream is frozen.

I suppose it has been already frozen:




How to compile VVC H266 MPEGi Versalite Video Coding DeCoder for Linux for VideoLan usage?
Full Version 1.0.1 is avaible as Open Source:
https://github.com/fraunhoferhhi/vvdec

There are even:
VLCReader.cpp
VLCReader.h

in:
tree/master/source/Lib/DecoderLib
https://github.com/fraunhoferhhi/vvdec/ ... DecoderLib

I have heard it can be compiled even for running on:
iPhone 12pro Soc ( Apple A14 SoC)

results:
FHD: 53fps (RA and LB)
UHD: 32fps (RA)

https://arxiv.org/abs/2103.03612




This plugin for VideoLan only runs Annex B byte order streams:
https://github.com/TencentCloud/O266player
(Tencent O266dec plugin is a plugin for VLC player that enables VLC to play H.266 Annex B bit streams)

[Rémi Denis-Courmont]

FHG is a research institute. The fact that they have published a decoder means that they are, or have been, researching. It does not necessarily imply that the bitstream is frozen.

I'd expect that we'd see some major announcements whenever the baseline specification is ready. Not that I'd know.

With that said, if you need H.266 for research purposes, you should probably not wait until H.266 is merged into the official VLC. As a general rule, VLC does purposefully not accept work-in-progress codecs and format bindings, to discourage deploying incompatible draft versions.

If you need H.266 for consumer or production usage, then you can wait.

[Sirchwe]

You may be deceived and confused by lack of interest of the overall / general media.
And media are not as much interested to spread the news about technologies which could make TV market entry point 2x cheaper in compering to mpegH,
or 4x cheaper when compering to mpeg4, or even 2³x = 8x cheaper when compering to mpeg2 TV broadcast.
And combined with LC EVC = mpeg5 part2 it can even make TV broadcast entry point more than 16x cheaper compering to just mpeg2 !
Whereas they fighting for or gain commercial viability by capturing audience in numbers of 1‰-1% of total TV viewership.

In July 2020 VVC = H266 = MPEGi was finalized
in October 2020 Mpeg5 part 1 = EVC, Mpeg5 part2 = LC EVC was finalized.

VTM reference software for Versatile Video Coding Test Model was published still in Spring of 2020.

I've noticed working Decoder code being Publish quite some time.
But now it is Final Version, notice numeration:
1.0.1 of working decoder, not just reference software for VVC Test Model,
encoder is still not published as final.
it is still just 0.3.1

And They have announced finalization / completion of hardware by: June 2021.
I know it will be only designed hardware to be completed.
Producing this Chips as hardware is about 6month,
as that is the standard waiting time for this industry.


And VideoLan will not be able to incorporate VVC code into its code.
As you will do with x266.
This software is Open Source, as was objective / aim of Future Video Coding as it was once named.
However it is not Free Software by any means.


However you could make some guidance, how to compile this code.
Even for android or linux enigma2 dvb-s2 dvb-t2 receivers.

There can be just software to be made to facilitate that by with only one button for newbie user.

And there will be created 4 switchable patent pools for H266 MPEGi Versatile Video Coding.
So no single company will be able to prevent and halt VVC usage, as was the case for HEVC = mpegH = H265.


I suppose dvb / ATSC Specification would need some agreement on specification on how to handle certain Transport Streams and ascribe some Code Numbers for VVC presence in .ts packet of TV Broadcast.
(But it could have been already done).



For comparison that is VVC VTM reference software:
https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM
and they are planning that final Working version of encoder will be 70x faster than reference software:
https://github.com/fraunhoferhhi/vvenc
But It is still just 0.3.1.0 version of encoder.
Final Working Version of decoder 1.0.1:
https://github.com/fraunhoferhhi/vvdec

[Rémi Denis-Courmont]

The FHHI codec does not look license-compatible with VLC, so then it can't be used, except for people who make their own private builds... which I guess is what Tencent is doing...

[Sirchwe]

The FHHI codec does not look license-compatible with VLC, so then it can't be used, except for people who make their own private builds... which I guess is what Tencent is doing...

I agree, However we can publish on forum Scripts and GuideLines for even newbie how to do it fast and without any problems.
Just like there is plenty software on wine, that needs to be installed manually by user himself.
And it is done, simple by click on one of a few the buttons.

It is known address of github, how to fetch data from that,
and how to compile.
It can be done by single script Run from every single user himself (herself).
And user does not need to be author of such script.


It is not fundamental meaning of added.
But it is fundamental meaning of H266.

Because I suppose only x266 will be really incorporated into VLC.


I am newbie.
I do not know if the:
VLCReader.cpp
VLCReader.h
need to compiled together with VLC source,
are if they can be compiled alone just with VLC source present.
I do not know how to handle result of compilation.

The authors of H266: HHI, they used VLC player for playback of TV Broadcast Test from Astra 28.2°E.


And I suppose in VideoLan community it exist knowledge how to make such guidelines for newbies.

I suppose such scripts can be pretty simple for Linux.
And they can be done even for Windows or MacOs, or iPhone, or android.

People use Flash Linux installers for pendrives and SD cards.
Do it from live boot CDs & DVDs.
Without any special knowledge of themselves.

[Hardcore Games]

I was looking at the standard and so far no open source reference code seems to be available for everyone to integrate into FFMPEG etc

[Rémi Denis-Courmont]

I agree, However we can publish on forum Scripts and GuideLines for even newbie how to do it fast and without any problems.

Knock yourself out...

I don't know what you want to write guidelines for though.

[Rémi Denis-Courmont]

I was looking at the standard and so far no open source reference code seems to be available for everyone to integrate into FFMPEG etc

At least the Tencent patchset depends on an external Tencent H266 decoder library which does not seem to be open-source, or even publicly available.

[Sirchwe]

I agree, However we can publish on forum Scripts and GuideLines for even newbie how to do it fast and without any problems.

Knock yourself out...

I don't know what you want to write guidelines for though.

Congratulations, you kinda coulda read what I have written:

The FHHI codec does not look license-compatible with VLC, so then it can't be used, except for people who make their own private builds... which I guess is what Tencent is doing...

I am newbie.
I do not know if the:
VLCReader.cpp
VLCReader.h
need to compiled together with VLC source,
are if they can be compiled alone just with VLC source present.
I do not know how to handle result of compilation.

The authors of H266: HHI, they used VLC player for playback of TV Broadcast Test from Astra 28.2°E.


And I suppose in VideoLan community it exist knowledge how to make such guidelines for newbies.

I suppose such scripts can be pretty simple for Linux.
And they can be done even for Windows or MacOs, or iPhone, or android.

People use Flash Linux installers for pendrives and SD cards.
Do it from live boot CDs & DVDs.
Without any special knowledge of themselves.

VLCReader.cpp
VLCReader.h
I suppose files need to be placed togather with VideoLan Source Code, which is open.
Then, after compliation of H266, the only thing needed is to compile VideoLan.
However compilation of VideoLan Source Code may be considered simple.
There is need to properly address those to files from VVC = H266 project!
I suppose they need to be placed somewhere on directory tree of VideoLan,
and eventually added by adding their names to other files in proper places.
and some (I am guessing) #include clause or import calling may be needed.

I suppose that for Software Engineer from VideoLan Player project it may be more trivial to show this,
than to read and evaluate License Agreement of Versatile Video Coding = H266!
I am more just in fear, that files like:
VLCReader.cpp
VLCReader.h
and in case of encoder (which is still in progress: version 0.3.1.0):
VLCWriter.cpp
VLCWriter.cpp
Could be removed from official site, in case of such guidelines were gaining too much publicity.

The thing is not even 1h work for guy, who know the code of VLC Player!
Once again:
Put files in proper places, add few #include/import statements.
I suppose at least 4-8 such entries in proper places in proper manner.

And just hit compile button!
(or enter public known CLi command for compilation!)



I suppose someone could even make such thing in form of plugin or firmware for Linux Enigma dvbS2T2 ATSC3 itsc receivers!

[elm]

I agree, However we can publish on forum Scripts and GuideLines for even newbie how to do it fast and without any problems.

Knock yourself out...

I don't know what you want to write guidelines for though.

Congratulations, you kinda coulda read what I have written:

The FHHI codec does not look license-compatible with VLC, so then it can't be used, except for people who make their own private builds... which I guess is what Tencent is doing...

I am newbie.
I do not know if the:
VLCReader.cpp
VLCReader.h
need to compiled together with VLC source,
are if they can be compiled alone just with VLC source present.
I do not know how to handle result of compilation.

The authors of H266: HHI, they used VLC player for playback of TV Broadcast Test from Astra 28.2°E.


And I suppose in VideoLan community it exist knowledge how to make such guidelines for newbies.

I suppose such scripts can be pretty simple for Linux.
And they can be done even for Windows or MacOs, or iPhone, or android.

People use Flash Linux installers for pendrives and SD cards.
Do it from live boot CDs & DVDs.
Without any special knowledge of themselves.

VLCReader.cpp
VLCReader.h
I suppose files need to be placed togather with VideoLan Source Code, which is open.
Then, after compliation of H266, the only thing needed is to compile VideoLan.
However compilation of VideoLan Source Code may be considered simple.
There is need to properly address those to files from VVC = H266 project!
I suppose they need to be placed somewhere on directory tree of VideoLan,
and eventually added by adding their names to other files in proper places.
and some (I am guessing) #include clause or import calling may be needed.

I suppose that for Software Engineer from VideoLan Player project it may be more trivial to show this,
than to read and evaluate License Agreement of Versatile Video Coding = H266!
I am more just in fear, that files like:
VLCReader.cpp
VLCReader.h
and in case of encoder (which is still in progress: version 0.3.1.0):
VLCWriter.cpp
VLCWriter.cpp
Could be removed from official site, in case of such guidelines were gaining too much publicity.

The thing is not even 1h work for guy, who know the code of VLC Player!
Once again:
Put files in proper places, add few #include/import statements.
I suppose at least 4-8 such entries in proper places in proper manner.

And just hit compile button!
(or enter public known CLi command for compilation!)



I suppose someone could even make such thing in form of plugin or firmware for Linux Enigma dvbS2T2 ATSC3 itsc receivers!

Please stop writing stuff about ready to go code for the VLC Player just because some files has the VLC letters in it.
VLCReader is a part of a codec that does the Variable Length Coding.
That has nothing to do with the VLC player.
It´s not only 1 hour to integrate it into the software .
It´s only 5 minutes to look into the VLCReader.c/.h code to assure that this stuff has nothing to do with the VLC player.

[Hello]

The bitstream is now ready. To come back to my question: When will H.266 be added?

[InTheWings]

The bitstream is now ready. To come back to my question: When will H.266 be added?

We already have it working internally.
There's just no use for now, no mapping outside of raw content, and -open- decoder isn't stable

[Sirchwe]

When will H.266 be added?

We already have it working internally.
There's just no use for now, no mapping outside of raw content, and -open- decoder isn't stable

MX Player application and Indian Web Video On Demand Streaming Service uses it.
So I suppose: There is already a place to test it

By The Way,
starting Satellite TV in VVC = MPEGi = H266 in SD @512Kb/s cost only 50'000 (€uro or $) per year of Satellite Bandwith Technical Cost (or you can even find 2x cheaper satellite operator),
Plus Limiting (that is Corrupt in my humble opinion) Licensing Fee, but that is just Tax Cost,
if You Live in really free country, there should not be any additional Licensing cost.
Any Free Citizen Should be allowed to start a TV Channel, It should be just Like VideoOnDemand Or YT channel.

There has been Version 1.0.0 of VVdeC since III2021, and Version 1.0.0 of VVenC since V2021.

and since there are already Sat>ip devices, Wi.Tv Boxes
if you can install on Android TV Box or Linux TV Box, or just Android TV
M3U playing VideoLan with VVC = MPEGi = H266
or Mpeg5 = EVC + LC EVC capabilities
you can watch TV Broadcasted from Satellite in newest: VVC = MPEGi = H266.

And There is no sense in paying for such Broadcast if there is none to watch.
I understand also Logic:
if there is no broadcast Or content there is not much point to make VVC = MPEGi = H266 enabled VideoLan Android, or VideoLan Linux Player publicly available.

So there is: Feedback Loop,
and I suppose it is Unintended infinite Endless Looping,
stuck in Proceeding within Endless Cycles.

There is no support nor even guidance for already existing software solutions or there is no hardware, because there is no content,
and there is no content, because there is no support nor even guidance for already existing software solutions.

[InTheWings]

MX Player application and Indian Web Video On Demand Streaming Service uses it.
So I suppose: There is already a place to test it

Provide content. We're not in India

[Sirchwe]

MX Player application and Indian Web Video On Demand Streaming Service uses it.
So I suppose: There is already a place to test it

We're not in India

It does not fly as Excuse:
1)in Plural: We
2)in English,
3)in European Union, where:
GeoLocking is Frown upon,
and GeoLocking News Sites is illegal:
and We Have all access to The Onion Network and Tor Browser
(I know corrupt government in USA prosecutes for bypassing GeoLocking, but corrupt governments in EU does not do it)

and I write from Corrupted EU
mxplayer.in/browse/live-tv/news-live-channels


BTW:
We may be within reach of India's Satellite TV broadcast

[Rémi Denis-Courmont]

You're not making much sense. And please take your political rants elsewhere.

There's no known mapping at this time, we need sample files.

[InTheWings]

and I write from Corrupted EU
mxplayer.in/browse/live-tv/news-live-channels

ok, good

[InTheWings]

and I write from Corrupted EU
mxplayer.in/browse/live-tv/news-live-channels

Provide URL as all I see is H264 streams

[Lotesdelere]

https://code.videolan.org/videolan/vlc/-/issues/27055

[zipdox]

vvdec is not free software, and is not open source under the definition. Its license expressly withholds patent rights. This means it will never get used in VLC or FFmpeg, or at least it will never get distributed with it.

[Rémi Denis-Courmont]

Indeed, but since the source code exists, it should be possible for those interested to compile it for their own internal use.

The problem remains as I wrote a few months ago: patches are necessary to MP4 demuxer, MKV demuxer, MPEG-TS demuxer or whatever, inside VLC to recognise VVC video tracks. With only external modules, only raw ES video files and RTP streams can be supported.

But apparently nobody cares to write those patches and submit them to the VLC project. IMO, people need to stop asking for stuff and start actually doing stuff, if they want VVC.