@sgaist The problem was the QGuiApplication in my main.cpp , i turned it to QApplication and it works fine.

And lastly what should i do to use my applicationwindow as my videowidget. I want my video to play on my app like normal mediaplayers, not to open another window for it. Thanks for your kind effort.

@onurcevik Did you ever figure the solution for this? Working on it now

thank you for the tip, I will try this in another project since I currently have a lot of problems getting qmediaplayer or qcamera working on the RaspberryPi. I wrote my code on amd64 on which everything worked fine but on the actual device (RPi) a LOT of problems came in (qt-gstreamer-v4l2-bcm2835-v4l2,MMAL, w.t.h.) but thats worth another thread.

Don't think this is solved, uninstalling gst-plugins-vaapi is a workaround at best.

Bug:
Qt Multimedia GStreamer backend doesn't support HW-accelerated video decoding
https://bugreports.qt.io/browse/QTBUG-23761

Thanks @jsulm

I am assuming that problem is in video drivers, I use fbdev by default (/etc/X11/xorg.conf)

The same situation with HTML5 video

It will be a good place to start- see if all gstreamer plugins are installed in your device. You can also try ldd and make sure no links are broken.

@Lazar-Urosevic Yes, you can have two QVideoWidgets at the same time. Why should one of them block? And why not just try it?

@mrjj
Yeah it is Qt 5.5, on ubuntu 14.04.
I saw one of the earlier bug reports that was closed (user submitted multiple bugs in one report), so I was hoping it was a something wrong on my end and that it had been fixed.
Thanks you for pointing me to the current bug report though.

Hi and welcome to devnet,

QNX support is an Enterprise feature, you should contact the Qt Company through your Qt Account Support Center.

I'm not sure for the zip source package, but at least for the sources installed from the online installer the headers of QtMultimedia are placed next to qbase directory, not inside it.
Also, to make your life easier you should use a prefix in your configure step and after compilation call 'nmake install' i.e.

configure -prefix "C:\Some path\" ... nmake nmake install

This would build Qt in the current directory and then copy over everything needed in their right places to the prefix directory. You can then safely delete the build directory and save a lot of space, since it contains all the intermediate build artifacts that you don't need. All the includes would be placed in a single <prefix dir>\include directory for you, such as they are in the precompiled packages.

The original author was asked to split the report so, if you don't' find anything then go on, create your new report with as much details and minimal compilable example

I did not make any changes at the example at all, so it should be as provided but Qt.