In theory you can create a franken-appimage mixing and matching from both by extracting them, making the changes, then repacking the result ā¦ in practice, that could get a little messy if not all the deps are compatible and you might need to move more than just melt, but itās probably the quickest and easiest way to isolate the component actually at fault if it works.
Youāll need appimagetool installed, then:
To unpack it, just run kdenlive<version>.AppImage --appimage-extract
and that should put the contents in a modifiable squashfs-root directory.
Once youāve copied what you want into that, appimagetool squashfs-root will create a new appimage from the contents and metadata files in it.
Itās not impossible that this is a problem introduced by a change in the compiler toolchain, so testing the existing appimage binaries that are known to (not)work takes that variable out of the loop.
If itās not an ultimately āobviousā change in one of those, then rebuilding both with the same toolchain will let us confirm itās the toolchain - but rebuilding cleanly with all the historically same dependencies isnāt quite as trivial a job (though it might be something that could easily be triggered on the kdenlive appimage build farm by someone to make some test images if it gets narrowed down to that point?)
And melt has relatively few (dynamic) dependencies:
$ ldd melt-7
linux-vdso.so.1 (0x00007ffc9e3e5000)
libmlt-7.so.7 => /tmp/.mount_kdenliJUx4k5/usr/bin/./../lib/libmlt-7.so.7 (0x00007f50a2f94000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f50a2f75000)
libSDL2-2.0.so.0 => /tmp/.mount_kdenliJUx4k5/usr/bin/./../lib/libSDL2-2.0.so.0 (0x00007f50a2da5000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f50a2bc4000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f50a2ae5000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f50a2ade000)
libiconv.so.2 => /tmp/.mount_kdenliJUx4k5/usr/bin/./../lib/./libiconv.so.2 (0x00007f50a29f8000)
/lib64/ld-linux-x86-64.so.2 (0x00007f50a2fdd000)
so if itās not a point release change in it, the build toolchain does start to get the spotlight ā¦ Do we know if the build farm was updated between those two releases?
hmm, I guess itās not impossible that itās a change in ffmpeg too, and how it handles the raw frames mlt passes it (especially if itās rescaling that) - but we should rule out the things closer to this sphere of influence first.