Qt for Python (PySide/Shiboken)

And maybe an even older version might be available

Can use this for mtk client tool?

Can you let us know what mtk client tool is? I don't know it. And by "use this" you mean pyside?

Hey guys, I noticed something on this page: https://doc.qt.io/qtforpython-6/PySide6/QtQml/QmlSingleton.html It says: "The order of the decorators matters; QmlSingleton needs to be preceded by QmlElement." But in all the examples, the decorator order is shown the other way around.

No, the examples show exactly what the text describes?

You're correct. Sorry. Currently facing an issue regarding testing QML while exposing a Singleton from Python and I thought changing that order fixed it. But it was not the case. And yes, documentation is correct.

You wrote this?! https://github.com/bkerler/mtkclient

Really useful :-) some many offtopic questions here ;-)

Why does QLocale("C").timeFormat(QtCore.QLocale.FormatType.NarrowFormat) contain seconds, whereas timeFormat for a real locale (e.g., QLocale("en_US")) does not?

Search in bugreports.qt.io for this (not exactly sure what search criteria you'd use, but you can look), and if you don't find, open a ticket for it. :D For category, it would be under Qt Core.

Hi, im trying to combine video stream from 2 capturesessions. What’s the best way to do that? I used GrabToImage and used opencv videoWriter to combine them. But somehow some frames are missing, ie, video duration is shorter than expected

I'd Google if ffmpeg can do it out of the box, whatever the combine means. But it's off topic.

combine means having one video frame to be inside another main video frame, not sure what's the term here.

If this is rendered in a qml scene, and this isn't two native windows overlayed, but it's combined and rendered on the same surface (we're getting on the edge of my understanding of how the Scene Graph and Qt RHI works, so this may not be completely accurate), you may be able to copy the contents of the surface to an offscreen surface and QOpenGLFramebufferObject, and from that get the pixel result... But, getting this in Python is definitely going to need some C++.

after futher debugging, I have a better idea on the problem.. so what I did was to use "streamingVideoOutput.grabToImage(...)" that is ran every 33ms using qml Timer. just with a simple console.log, I can see that normally this will be called 30 times/second, (30fps). But, when I move around the app window, it can go down to 18-20 times/second. Is this a bug with QML's timer or my mistake? or simply Timer runs on UI thread