Difference between official version and "build your source"

[paulhiggs]

There seems to be some functional differences between the Official MediaInfo version shipped and the binary from Visual Studio

First, they start differently
Official version

versus Build From Source version

Second, the official version can open and show the 'Level 10' details of my 55MB clip, but the Build From Source version results in a "Not Responding...:" state

[JeromeMartinez]

There seems to be some functional differences between the Official MediaInfo version shipped and the binary from Visual Studio

On Windows we use the C++ Builder version (in Project/BCB directory).
Note that we have currently 3 different GUIs on windows (C++ Builder, Qt, Wx), and the current discussion is to move at some point form the closed source C++ Builder version to Qt versio on Windows, and on Linux we plan to move from Wx version to Qt version, on macOS we stay with the macOS specific UI toolkit.

[JeromeMartinez]

Second, the official version can open and show the 'Level 10' details of my 55MB clip, but the Build From Source version results in a "Not Responding...:" state

I use the Wx version every day on Windows (there is a tree mode feature for details not yet in the C++ Builder version) and don't see any freeze. Please share the file making a freeze (privately if needed).

[paulhiggs]

Please share the file making a freeze (privately if needed).

This DVB V&V file look good in the official release version - DVB AVS3 VaV 2160P50 PQ10 Three DMI

I can try with other DVB V&V sequences later

[JeromeMartinez]

This DVB V&V file look good in the official release version - DVB AVS3 VaV 2160P50 PQ10 Three DMI

This file works with the Wx version, but is super slow with the default view (Tree view), select the text view and you get a speed similar compared to the C++ Builder version.

Generally speaking, the trace for a TS file is too verbose and we need to reduce it (not loading all in one shot), but not a priority (I personally love the trace feature but no sponsor is interested so I use it with such limitation, usually I just truncate the TS file and it is enough for me).

[paulhiggs]

When I select "Trace Level 10" in the Official release, and open the file (DVB_AVS3_VaV_2160P50_PQ10_Three_DMI.ts) the result is shown in 15 seconds.

In the Windows|x64|Release Build Form Source version (MediaInfo-Gui.exe in MediaInfo\Project\MSVC2022\x64\Release), I select "Debug -> Details" and Open the same file (DVB_AVS3_VaV_2160P50_PQ10_Three_DMI.ts) and after 8 seconds the app is shown as "Not Responding"

After 5 minutes, I give up although Task Manager shows that CPU cycles are being consumed

Note that watching Task Manager one sees the "Memory" increase to over 3GB before dropping into the 700MB level

[JeromeMartinez]

"Debug -> Details" and Open the same file (DVB_AVS3_VaV_2160P50_PQ10_Three_DMI.ts)

So you have the tree view selected, and I said that it is too slow for sure when it is with this default view.

"Debug -> Details" then "View -> Text" then Open the same file (DVB_AVS3_VaV_2160P50_PQ10_Three_DMI.ts) , you'll have after ~10 seconds (7 seconds on my machine, see the bottom of the UI):