HumanDynamo

My personal feedback : cmake port from qmake is incomplete. Use qmake in all cases. I'm sure : as QtAV development is stopped since february, i fork the project in...

Note: my port to Qt6 is complete. QtAV original code port to Qt6 was partial. Look weel the README, i explain well all tasks done over QtAV source code.

I already fixed the problem: https://invent.kde.org/graphics/digikam/-/blob/master/core/libs/video/qtav/src/filter/X11FilterContext.cpp#L236 Gilles Caulier

yes, with digiKam , we don't use QML code in favor of C++, for speed reasons, and to be homogeneous, as digiKam is more than 1.5 M C++ code lines....

Hi, For digiKam project we use QtAv to play video in application. We have started to port digiKam to Qt6. Of course QtAv need to compile with Qt6. I just...

Hi, digiKam do not use QML as it fully based on C++. No need to increase a large code complexity with this stuff. C++ is always optimum than QML. To...

Wang, I think you mix subject here. The lag is not a problem about audio support. The audio support under Linux and Windows was been solved few days ago following...

I ask for a runtime debug trace in bug #374355. Do you want a QtAv configure/compilation trace with MXE ? Gilles Caulier

This is the MXE part of QtAv configuration stage for Windows 32 bits (64 bits version is mostly the same) : -- Build files have been written to: /mnt/devel/GIT/5.x/project/bundles/mxe/temp.build ==...

yes. sound like the ffmpeg codec need a latency to be re-used for another stream to play. Gilles Caulier