cjee21

I think it is meant to remain as host-*. If I rename host-qmake.bat to qmake.bat, Qt Creator no longer detects that ARM64 is available. Unless there's some other config telling...

Okay, I see qmake path pointing to host-qmake.bat in Tools/sdktool/share/qtcreator/QtProject/qtcreator/qtversion.xml so Qt Creator probably picked up the filename from here.

Agree with 1. That should make it easy to use same build scripts for local builds and GitHub actions for example as well. I'll likely not bother with 2 since...

@tsteven4 yeah I just changed `--qtpaths` that I passed to `windeployqt` from `qtpaths.bat` to `host-qtpaths.bat`. I see that `icuuc.dll` is new. It wasn't there when I deployed with some previous...

I think `icuuc.dll` was copied from `Windows\System32` (that's why it is only x64 when cross-compiling) and it is not supposed to be deployed. The description says `ICU Common Forwarder DLL...

> maybe you can reproduce the warning with my test case [deploy.zip](https://github.com/user-attachments/files/23661519/deploy.zip) and qt installed by the maintenance tool Yes, it can be reproduced without any changes to your test...

`DTS:X – All Around Us` demo from 2016 is showing as IMAX by MediaInfo and FFmpeg. It is unlikely to be IMAX since it is from before IMAX Enhanced was...

> This is off-topic: doesn't my receiver display the decoder? From my understanding, DTS:X Pro is not a decoder in the sense of DTS-HD vs DTS:X and also not an...

> Well, if a DTS:X Pro can not detect DTS:X Pro, there is an issue somewhere... Does your decoder show DTS:X Pro with some streams, or is it just always...

Just discovered that this file (https://drive.google.com/file/d/1IRbjvvd2OGb-ZP6XHsbvaucYCFJ3QEhl/view) from the trinnov blog post linked above is in DTS:X (confirmed with a Denon AVR) but is not detected as such by both MediaInfo...