Avidemux Forum

Quote from: eumagga0x2a on December 17, 2025, 05:16:47 PM

Quote from: Faiakes on December 17, 2025, 04:07:05 PMI go this and a crash from, I suspect, a malformed video file.

This is entirely possible as the size of a compressed frame is supplied by the demuxer used to load the specific file. If the size calculated by the demuxer doesn't fit into the allocated buffer, we safely call it quit.

It might be interesting to analyze the presumably malformed file to understand whether we should have rejected opening it in the first place, but, in general, a safe termination of the application is likely to be the second most sensible way to deal with such an issue.

Well, idiot me I deleted the file but I think I can find it again.
Would you want me to?
(It was an old foreign language film. I have found a different version, so I don't need anything per se)

Thank you, maybe not this time.

Quote from: eumagga0x2a on December 20, 2025, 04:06:13 PMThank you, maybe not this time.

OK, thanks.

Hi

vapoursynth removes recently the support for VSScript API3 https://github.com/vapoursynth/vapoursynth/commit/ae7fa51078eacc75f0a6fba16eb4de9c21c6a80e

this means avidemux stop build due missing file in https://github.com/mean00/avidemux2/blob/master/avidemux_plugins/ADM_demuxers/VapourSynth/ADM_vsProxy.h#L20

needs fix for use to "new" API v4

greetings

Quote from: sl1pkn07 on December 30, 2025, 12:39:55 AMneeds fix for use to "new" API v4

Ideally, yes. Disabling VapourSynth >= 73 to fix build for now: https://github.com/mean00/avidemux2/commit/23b1d8fb1e931660a1a8f1f3cab20186a7b74eb0

Thank you for the heads-up.