Thanks for your answers,
Unfortunately I cannot reproduce the issue here, and at the user end the
problem is now fixed. I don't even know which codec was missing or
wrong. I was just asking for a way to eventually programmatically avoid
the crash and prompt the user. Needless to say there are hundreds of
users with Windows 10 and this is the first time we face this case.
I am aware QT5 is EOL, porting to QT6 is something we need to do.
--Philippe
Le 24-06-2025 22:01, Thiago Macieira a écrit :
On Tuesday, 24 June 2025 11:54:38 Pacific Daylight Time Axel Spoerl via
Interest wrote:
massive changes and improvements have been made in Qt 6 / QMultiMedia,
logging and error handling included. Since Qt 5.15 is EOL, it's maybe
a
good time to upgrade to Qt 6.
In your application code, you can use the errorString() methods to
bring
backend messages forward. In addition you can set the environment
variable
QT_LOGGING_RULES="qt.multimedia.*=true" and inspect the logging
output.
I am not sure for 5.15. But for Qt 6, you'll also get warnings about
missing
codecs this way.
One shouldn't get warnings. There should be a way for the application
to
programmatically get the error condition so it can display to the user.
However, Philippe hasn't provided enough information for us to know
where the
crash is happening. We need a working Qt 6.8+ application that
reproduces the
problem.
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
