@BigBen
Yes, you always need to write a new class which derives from the base class if you need to override a virtual method, as QWidget::paintEvent().

The Analog Clock Example illustrates overriding paintEvent(). There will be hundreds of other examples online.

This is because of virtualbox 3d acceleration support opengl version 2.0
it looks like qt multimedia(6.2) need opengl at least 3.0 version

Below was how to know it.
mesa log enable and log like below

Mesa: glGenTextures 1
Mesa: glBindTexture GL_TEXTURE_2D 2
Mesa: FLUSH_VERTICES in bind_texture_object
Mesa: FLUSH_VERTICES in teximage
Mesa: glTexImage2D GL_TEXTURE_2D 0 GL_R8 960 360 1 0 GL_RED GL_UNSIGNED_BYTE (nil)
Mesa debug output: GL_INVALID_VALUE in glTexImage2D(internalFormat=GL_R8)

GL_R8 variable is available upper than opengl 3.0

That's why we have to see green screen in virtualbox 3d acceleration

Never mind. I had to set the surface format version to 3.0 in main, at the top.

int main(int argc, char *argv[]) { QSurfaceFormat f; f.setVersion(3,0); QGuiApplication app(argc, argv); //... }

@Sai-Raul Start here: https://doc.qt.io/qt-5/videooverview.html

How did you get the taken picture from the camera?

@domo93 You clearly haven't read the Qt documentation or looked at the examples, because everything you asked for is there.

https://doc.qt.io/qt-5/android.html
https://doc.qt.io/qtcreator/creator-deploying-android.html

@Jarenward said in Fresh app development:

which Qt is for me?

There is only one Qt :-)
PyQt is a Python binding for Qt and still requires Qt libraries (binaries). So, even if you use PyQt you will need to have Qt libraries which you are using.
If I understood you correctly you need your UI on a computer (not Pi), right? This part is simple - just install the latest stable Qt version an start coding :-)
For the other part you can either directly develop on Pi (using Raspbian you can easily install Qt with apt) or you have to cross compile Qt to develop on your PC. You don't have to cross compile everything, just what you need. See https://wiki.qt.io/Raspberry_Pi_Beginners_Guide

Ok.
I have found a solution

QImage imageToReturn = QImage((uchar*)converted_image.data, converted_image.cols, converted_image.rows, QImage::Format_RGB888); imageToReturn.convertToFormat(QImage::Format_RGB32);

I have found that when i started to compare metadata between QImage constructed from cv::Mat data and QImage constructed as in second example

@Cleiton-Bueno thanks for your suggestion. I have disabled audio in my kernel completely now. Now I get the message CameraBin warning: "Could not open audio device for recording." which shows, that I really removed audio support.
Unfortunately, this still doesn't solve my basic issue, which is a extremely sluggish video output when the videoRecorder property is enabled in the Camera. That means, the audio encoding was not causing this problem at all.

Thx, Jens

Hi @YenZi
A little bit late, but could using a Loader and settings its asynchronous property to true work?
http://doc.qt.io/qt-5/qml-qtquick-loader.html#asynchronous-prop

For example: QCameraImageProcessing

Hi,

To add to @raven-worx, there's also the QtGStreamer project that might be of interest.

@gsharma Ok, I forgot to mention my test environment, sorry about that.
Well, maybe it's a good reason to update your Qt version...
Best regards.

Solved problem by stopping/starting camera while tab switching.

Hi,

Are you running them from Qt Creator ?
If not did you deploy the QtMultimedia plugins for your second application ?