Hello,
nightly avidemuxLinux_GLIBC_2.36_amd64_250323_1106.app
as in topic, setting swsResize or VA-API Resize, apparently any resolution (locked proportions) and av1 encoding results in a core dump.
Setting a multiple by 16 resolution did not help. I tried several *.ts files from dvb-T, I did not try anything else.
Dump seems to occur at random times within the first 5-7 minutes of encoded file.
Anyone else experiencing this?
$./avidemuxLinux_GLIBC_2.36_amd64_250323_1106.app 2>&1 | tee avidemux.log
https://paste.debian.net/hidden/9321f0e6/
I observed this crash, seems to be reproducible in some rare circumstances. Presumably an upstream libaom issue.
I confirm 250516 is also affected. I can reproduce this every time, at least with the files I'm using.
The last working version seems to be 241212 nigthly.
I know this probably does not depend on Avidemux, just reporting.
We're talking about libaom of course.
Of course it is affected – it uses the same libaom version.
This was a hilariously stupid snafu: packaging a stock, ancient libaom from Debian while building against a recent libaom in /usr/local. Should be fixed now, solving the problem with crashes. Please try a future nightly. I'm sorry for inconvenience.
However, the OpenGL breakage in appImage is real, please make sure OpenGL is disabled.
I can confirm 250524 nightly completes libaom av1 + resize with no errors, intel av1 still not working, log in the other thread.
Quote from: upwithav1 on May 25, 2025, 09:10:03 AMI can confirm 250524 nightly completes libaom av1 + resize with no errors
Thank you for verifying the fix.
Quote from: upwithav1 on May 25, 2025, 09:10:03 AMintel av1 still not working
Fully expected, no changes in that area.