News:

--

Main Menu

x265 missing, 'null' is in its place

Started by chairman.faust, August 21, 2019, 01:49:50 PM

Previous topic - Next topic

dipswitch

Quote from: eumagga0x2a on August 24, 2019, 10:25:06 PM
Quote from: dipswitch on August 24, 2019, 03:26:05 PM
I really have no idea

Neither do I  :(

QuoteOnly thing i know is that the overnight build gives me hevc output.

That nightly is a MinGW build, right? Builds which exhibit the problem are VC++ builds.

This is correct.What i didnt understand: i'm using avidemux for some time now. Suddenly the installer has vc++ in its name. Didnt actually new what was going on. Now i seem to guess there is something changing in the way avidemux runs? it ran in a mingw environment and this now is shifting to microsoft visual c++? Was mingw no good?

eumagga0x2a

Official release builds were moved to Visual Studio between releases 2.7.1 and 2.7.2 because MinGW builds are (almost) impossible to debug.

eumagga0x2a

There is a new VC++ nightly build with some (unrelated) changes in the build environment --> https://avidemux.org/nightly/vsWin64/Avidemux_2.7.4%20VC++%2064bits%20190826.exe

Could you please try it and report back whether the x265 encoder plugin in this build loads or not?

eumagga0x2a

By the way, we have verified with TO that the checksum for the plugin DLL matches, but we haven't checked libx265.dll itself. Could you please check that the libx265.dll the HEVC encoder plugin needs to load has MD5 equal

cdbea182ddf9a35cb4164eafcd9eee09 ?

If you have installed Avidemux VC++ to C:\Program Files\Avidemux 2.7 - 64 bits, then please execute

cd /d "C:\Program Files\Avidemux 2.7 - 64 bits"
certutil -hashfile libx265.dll MD5

dipswitch

Who are you asking this? Me or @chairman.faust  ?

eumagga0x2a

#35
You (though it wouldn't matter if the TO responds too). It is about excluding the option that libx265.dll is corrupted.

Have you already tried the new nightly? (libx265.dll there is exactly the same as in the release, but as we don't know what is causing the problem, trying should not do at least any harm).

eumagga0x2a

@dipswitch: It would be really desirable to know for sure whether libx265.dll from the Avidemux VC++ install directory on a system, where the HEVC encoder plugin is missing, is undamaged, i.e. whether the checksum for this file matches. This is IMHO even more important than to try the nightly which fixes PNG decoder in the internal ffmpeg missing (libx265.dll in this nightly is exactly the same as in the 2.7.4 release).

Of course, should libx265.dll turn out to be damanged, this would imply something very selectively messing up the extraction of the 7z archives with all the components of Avidemux stored within the QtIFW installer file.

dipswitch

Quote from: eumagga0x2a on August 26, 2019, 08:42:27 PM
By the way, we have verified with TO that the checksum for the plugin DLL matches, but we haven't checked libx265.dll itself. Could you please check that the libx265.dll the HEVC encoder plugin needs to load has MD5 equal

cdbea182ddf9a35cb4164eafcd9eee09 ?

If you have installed Avidemux VC++ to C:\Program Files\Avidemux 2.7 - 64 bits, then please execute

cd /d "C:\Program Files\Avidemux 2.7 - 64 bits"
certutil -hashfile libx265.dll MD5


On the machine with no hevc output, avidemux 2.7.4 was installed in C:\Program Files\Avidemux 2.7 VC++ 64bits

The MD5 checksum of libx265.dll is f9b31d6a0e526efbd048b1073f795373     (i checked twice).

dipswitch

Quote from: eumagga0x2a on August 26, 2019, 06:53:47 PM
There is a new VC++ nightly build with some (unrelated) changes in the build environment --> https://avidemux.org/nightly/vsWin64/Avidemux_2.7.4%20VC++%2064bits%20190826.exe

Could you please try it and report back whether the x265 encoder plugin in this build loads or not?

I installed it and there still is no hevc output on this nightly build.

The md5 checksum for libx265.dll on this build is f9b31d6a0e526efbd048b1073f795373 . Seems something is really messing up the x265 dll.

dipswitch

Strangly enough, the not working libx265.dll is exactly the same size as a working one: 6.065.152 bytes.

But things get weirder, the md5 checksum for libx265.dll on the working 2.6.4 install on another machine is also:

f9b31d6a0e526efbd048b1073f795373

And when i copy libx265.dll from a working install on another machine to the not working avidemux, it still doesnt work, i still dont get hevc output.

I'm lost.

eumagga0x2a

Thank you for checking this, one more possible reason for the issue ruled out.

eumagga0x2a

Probably a completely bogus idea, but is there any other software installed which has libx265.dll bundled?

(bogus because usually the application install dir is searched for libs first)

dipswitch

i've searched the entire hdd for libx265.dll, only the one from avidemux is there.

eumagga0x2a

Okay, thanks. I could only suggest to try the following: uninstall 2.7.4 VC++, install 2.7.3 VC++, make a copy of its older libx265.dll, uninstall 2.7.3 VC++, install 2.7.4 VC++ (release or better nightly as the latest nightly has the PNG decoder which is missing in the release), replace the newer libx265.dll with the older copy. Does it work?

dipswitch

Quote from: eumagga0x2a on August 27, 2019, 10:08:27 PM
Okay, thanks. I could only suggest to try the following: uninstall 2.7.4 VC++, install 2.7.3 VC++, make a copy of its older libx265.dll, uninstall 2.7.3 VC++, install 2.7.4 VC++ (release or better nightly as the latest nightly has the PNG decoder which is missing in the release), replace the newer libx265.dll with the older copy. Does it work?

Did you read my previous post, where i explained that the libx265.dll from the working avidemux has exactly the same md5 checksum and size as the non working installation? strangely enough the md5 checksum doesnt match the one you provided, how is this possible?