Can't open AV1 webm file
LazyGeniusMan opened this issue · comments
Hi, I tried to open AV1 webm file but it won't open. MP4 and MKV is working fine.
Console Log:
PS C:\Users\LazyGeniusMan\Downloads\video-compare-20211127-win10-x86_64> ./video-compare 1.webm 2.webm
terminate called after throwing an instance of 'ffmpeg::Error'
The file mediainfo:
General
Complete name : 1.webm
Format : WebM
Format version : Version 4
Overall bit rate : 6 978 b/s
Writing application : Lavf58.65.101
Writing library : Lavf58.65.101
IsTruncated : Yes
Video
ID : 1
Format : AV1
Format/Info : AOMedia Video 1
Format profile : Main@L4.0
Codec ID : V_AV1
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Writing library : Lavc58.119.100 libaom-av1
Default : Yes
Forced : No
Color range : Limited
Audio
ID : 2
Format : Opus
Codec ID : A_OPUS
Bit rate : 192 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 32 bits
Compression mode : Lossy
Writing library : Lavc58.119.100 libopus
Language : Japanese
Default : Yes
Forced : No
MPV stat:
Thanks
EDIT: I tried running video with ffplay command and it's working fine, so the problem isn't on FFmpeg installed on my PC. Does this app using built-in FFmpeg in the releases?
EDIT2: I'm using latest ffmpeg nightly build
Hi @LazyGeniusMan,
Thanks for reporting this.
So the problem is that the Windows 10 build is linked statically against an older version of the FFmpeg libs which does not include decoding support for AV1.
I'll update the libs and release a new version soon.
Have a good one!
So the problem is that the Windows 10 build is linked statically against an older version of the FFmpeg libs which does not include decoding support for AV1.
I'll update the libs and release a new version soon.
Is it possible to use shared ffmpeg instead of static one for Windows build? (so you don't need to release a new build everytime FFmpeg have major update)
So the problem is that the Windows 10 build is linked statically against an older version of the FFmpeg libs which does not include decoding support for AV1.
I'll update the libs and release a new version soon.Is it possible to use shared ffmpeg instead of static one for Windows build? (so you don't need to release a new build everytime FFmpeg have major update)
Good call! I've created a new release which includes FFmpeg 4.4.1 DLLs (with support for AV1).
Merry X-Mas!
I've created a new release which includes FFmpeg 4.4.1 DLLs
Thanks for the new release, now av1 is working.
I have some questions, does the app target specific DLLs? because when I replace the DLLs with the latest nightly build and delete the old one that have a little bit different name, then the app wont run.
Also is it possible to use shared FFmpeg installed and stored by scoop? so it's kinda like using dependency, maybe it will be different build/release, full release (include ffmpeg DLLs) and slim release (exclude ffmpeg DLLs)
That's what I meant by not needed to update everytime FFmpeg release a new feature (support new thing), sorry if it's sound dumb, I'm not really familiar with this kind of thing.
Merry X-Mas!
Thanks, you too.
OK, so I forgot to explain that I got the included prebuilt DLLs from Gyan Doshi's website: https://www.gyan.dev/ffmpeg/builds/ (check out his releases page on GitHub, as well: https://github.com/GyanD/codexffmpeg/releases)
If you want to use DLLs from nightly builds you will either have to recompile the app yourself or you can try renaming the DLLs to have the same names as in the video-compare distro (however, but there is a no guarantee the DLLs are actually compatible and that the program will be able to start and run as intended).
Ah I see, thanks