Closed Selur closed 3 years ago
I'm unable to reproduce this issue with a random file. Does this happen with only this specific file or with other files also?
The encoding log looks weird because if the input truly has 416 frames why is there 417th frame (POC 416) in the log? You said that the decoding works fine, so does the video look normal up to the 400th frame?
Anyways could you provide the original video, the broken Kvazaar encoded file, and the version of FFmpeg used?
Ok, didn't see your edit about the input having 429 frames, which would explain the encoding log.
Does this happen with only this specific file or with other files also?
The exitcode: -1073741784 happens with all files here.
Anyways could you provide the original video, the broken Kvazaar encoded file, and the version of FFmpeg use
Uploaded the files used to https://drive.google.com/drive/folders/1Cc3LkTrl3IKw46yWvL506OQ1GoTtnkzW?usp=sharing
In case it is relevant: Kvazaar and ffmpeg were both compiled using MBAS (https://github.com/m-ab-s/media-autobuild_suite),
Sorry for not answering sooner but I've been busy with other stuff.
I could reproduce this issue with the MABS compiled Kvazaar. Only thing I could figure out that there is something in the MBAS environment that causes this issue. Manually compiling Kvazaar using mingw64
works as expected, i.e., running ./autogen.sh && ./configure --disable-shared --enable-static && make
in the mingw64
shell should work.
I'll try to get somebody else to further investigate and hopefully fix this.
I'll try to get somebody else to further investigate and hopefully fix this.
Any luck finding someone to fix this?
Hi Selur,
Unfortunately people have been very busy with all kinds of tasks lately. We will have another discussion about this with the team but we're not able to promise fixing this quickly, to be honest.
Based on your discussion (https://forum.selur.net/showthread.php?tid=1667) it seems at least v1.3 should work fine. I guess it is time someone starts bisecting to find the commit introducing this problem...
And once again, thanks for reporting.
This issue should be fixed now. The problem was in a thread exit call which caused problems with the pthreads which the MABS compilation environment uses.
Nice, I'll try it tomorrow. :) Thanks!
Works fine! Thanks for fixing this!
using:
(on Windows 10) and calling:
Kvazar outputs
while the input has 429 frames and then exists with exitcode: -1073741784 and exitStatus: 1
The decoding call works fine, so it must be something with kvazaar. (works fine when used with other encoders like x264, x264, vpxenc,...)
-> Any idea what is the cause of the problem and how I could fix it? (assuming it's not a bug)
Same command line with release v2.0.0 works fine and outputs:
with the expected exitcode 0.