HEVC successor: Versatile Video Coding

[Jamaika]

Originally Posted by FranceBB

so, again, they're working on it, but we can't see it yet, so all we have is the encoder_app.exe reference encoder

There is actually something, but I don't know what it is.
For sure gcc won't compile.
What language will it be in? It is not known.
The creator dreams of x266, but currently works in vvc.
I don't know what single file x266.cpp files are. There is probably some assembler.
https://github.com/chenm001/x266
https://github.com/fraunhoferhhi/vvd...uthor=chenm001
The ?266's RISC-V NON-Standard Vector Extension ONLY compile and disassembly by ?266 project modified llvm suite. You may build bu yourself or please contract to get prebuilt Centos-6 binary package.

[FranceBB]

Well, I contacted Multicoreware anyway with my Sky email, asking them for some info.
Let's see if they reply.

[ksec]

Originally Posted by birdie

ffmpeg hasn't even begun adding support for VVC. That looks weird, the codec uptake seems to be extremely slow.

The spec is barely out. Finalised last August, but profiles were still not set then. VTM Reference Software was barely catching up in October and VTM 11.0 only released two days ago. Conformance test wasn't finalised either.

I mean normally these sort of "cleaning up" takes up to a year. So I think they are doing well so far.

[MeteorRain]

Cutting edge technologies take time to be implemented.
22.2 channel aac audio spec was released years ago, and we barely just had a preliminary support in the latest version, implemented by jeeb.
Sometimes you have to be patient ;)

[Jamaika]

ffplay's humble beginnings
https://github.com/FFmpeg/FFmpeg/com...ee630d53c30d3f

[FranceBB]

Originally Posted by Jamaika

ffplay's humble beginnings
https://github.com/FFmpeg/FFmpeg/com...ee630d53c30d3f

That is indeed something!
Having a decoder is basically the first thing you want when supporting a codec, so those commits are more than welcomed.

[FranceBB]

Originally Posted by Jamaika

https://github.com/fraunhoferhhi/vvdec
https://github.com/fraunhoferhhi/vvenc
plus my fix
I have added codecs and compilation issues in my threads

I'm clearly doing something wrong.

Selecting Windows SDK version 10.0.18362.0 to target Windows 10.0.19042.
The C compiler identification is MSVC 19.27.29112.0
The CXX compiler identification is MSVC 19.27.29112.0
Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.27.29110/bin/Hostx64/x64/cl.exe
Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.27.29110/bin/Hostx64/x64/cl.exe - works
Detecting C compiler ABI info
Detecting C compiler ABI info - done
Detecting C compile features
Detecting C compile features - done
Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.27.29110/bin/Hostx64/x64/cl.exe
Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.27.29110/bin/Hostx64/x64/cl.exe - works
Detecting CXX compiler ABI info
Detecting CXX compiler ABI info - done
Detecting CXX compile features
Detecting CXX compile features - done
CMAKE_MODULE_PATH: updating module path to: C:/Users/Frank/Desktop/vvenc-master/cmake/modules
Looking for pthread.h
Looking for pthread.h - not found
Found Threads: TRUE  
Configuring done
Generating done