You should post the corresponding stack trace.

It seems remarkable to me that the QMediaPlayer can know whether I'm playing back audio with 1, 2, or more channels, but I cannot get that information from it, but I guess that's just the way it is? It seems like some people can get this to work, and others can't, so I wonder if this is another issue of platform differences? (For reference, this is playback either via a wired connection to an MFi device, or directly on an iPad/iPhone, so iOS under the hood.) Anyway, I've given up on displaying mono/stereo channel information in our implementation. (The player will fail to play back audio with three or more channels, so I can at least flag that. It'd be nice to label, but it's not required.) I'll report a bug if I get the time at some point.

Hey, Sorry for late answer. Yes everything seemed fine. No error report at least. But I'm guessing that this might not actually be linked with this topic anymore. So I'll just look into this issue on my own from there. Anyway, thanks a lot for the support ! Best regards, TomHat

Hi @SGaist , Thanks for your response. Just wanted to know for sure if there was a way to do it with Qt itself. Will start looking at other options. Thanks.

Thank you for the greeting. The file is working fine with the other players (VLC, Windows 10 player).

Here is pretty much the commands I use to deploy the app: qmake videoplayer/videoplayer.pro -o build/MakeFile -r -spec win32-msvc2010 -nocache jom -f Makefile -s windeployqt --release release

Hi @gsharma , I see you solved your problem. I have similar problem. I use qt-5.10 and IP camera. I want to stream with rtsp. Also want to see at QMediaPlayer. Could you please help me. How did you solve problem. Also do you know tutorial about this.

IIRC, the two builds are not using the same backend.

Glad you found out and thanks for the feedback !

You can take a look at that article.

@SGaist New output (after getting logged out): https://pastebin.com/yJK4tFeQ Output of diff dmesgOutputBeforeLogout.txt dmesgOutputAfterLogout.txt: https://pastebin.com/5jGtEiUd (differences between two outputs)

Problem solved. It was bug in Inno setup, which corruped Qt5Multimedia.dll somehow.

Solved, gstreamer-0.10-ffmpeg was missing. sudo add-apt-repository ppa:mc3man/gstffmpeg-keep sudo apt-get update sudo apt-get install gstreamer0.10-ffmpeg UPDATE: Not really solved, using this plugin breaks GStreamer: $ export GST_DEBUG=2 $ ./RPIStreamer 0:00:01.232878440 29169 0x7f0414007320 WARN qtdemux qtdemux_types.c:191:qtdemux_type_get: unknown QuickTime node type iods 0:00:01.233010807 29169 0x7f0414007320 WARN qtdemux qtdemux_types.c:191:qtdemux_type_get: unknown QuickTime node type avc1 0:00:01.233055875 29169 0x7f0414007320 WARN qtdemux qtdemux_types.c:191:qtdemux_type_get: unknown QuickTime node type avcC 0:00:01.233095592 29169 0x7f0414007320 WARN qtdemux qtdemux_types.c:191:qtdemux_type_get: unknown QuickTime node type btrt 0:00:01.235499777 29169 0x7f0414007320 WARN qtdemux qtdemux.c:6006:qtdemux_parse_segments:<qtdemux0> streaming; discarding edit list segments 0:00:01.235563181 29169 0x7f0414007320 WARN qtdemux qtdemux.c:7044:qtdemux_parse_trak:<qtdemux0> unknown version 00000000 0:00:01.236318578 29169 0x7f0414007320 WARN qtdemux qtdemux.c:6006:qtdemux_parse_segments:<qtdemux0> streaming; discarding edit list segments 0:00:01.264479125 29169 0x7f0414007680 WARN playsinkconvertbin gstplaysinkconvertbin.c:481:gst_play_sink_convert_bin_cache_converter_caps:<GstPlaySinkAudioConvert@0x7f03f801a050> No conversion elements 0:00:01.290541635 29169 0x7f04140071e0 WARN ffmpeg gstffmpegdec.c:2299:gst_ffmpegdec_frame:<ffdec_h2640> ffdec_h264: decoding error (len: -1, have_data: 0) 0:00:01.297533958 29169 0xba4d40 WARN basesrc gstbasesrc.c:2625:gst_base_src_loop:<source> error: Internal data flow error. 0:00:01.297562286 29169 0xba4d40 WARN basesrc gstbasesrc.c:2625:gst_base_src_loop:<source> error: streaming task paused, reason not-negotiated (-4) Error: "Internal data flow error."

[SOLVED] MainWindow::MainWindow(QWidget *parent) : QMainWindow(parent), ui(new Ui::MainWindow) { //… display = new QLabel(this); display->setGeometry(4,4,88,23); display->setText("00:00:00"); //… player = new QMediaPlayer; connect(player, SIGNAL(mediaStatusChanged(QMediaPlayer::MediaStatus)), this, SLOT(playerOnMediaStatusChanged(QMediaPlayer::MediaStatus))); //… timer = new QTimer; timer->setTimerType(Qt::PreciseTimer); connect(timer, SIGNAL(timeout()), this, SLOT(timerSlot())); //… } void MainWindow::playerOnMediaStatusChanged(QMediaPlayer::MediaStatus status) { if (status == QMediaPlayer::BufferedMedia) { pos = -1; //int pos declared on .h file timer->start(1000); } } void MainWindow::timerSlot() { pos = pos + 1; QTime time((pos/3600)%60, (pos/60)%60, pos%60); display->setText(time.toString("hh:mm:ss")); }

[SOLVED] I had to resort to the help of TagLibs library. And since the documentation available how to build this library to make it interact with Qt are very confusing and outdated, I proceeded to make available the library that I managed, with great difficulty, to compile by my hand: http://www.unitscan.org/archives/301 I hope will be usefull

[SOLVED] To make thumb slider jump directly at mouse click, use this subclass: header file: https://nopaste.me/view/c38f6570 source file: https://nopaste.me/view/ee7b9450 EDIT: line 4 in .cpp file is useless, you can delete this

Hi and welcome to devnet ! Thanks for sharing the report link ! It has been marked as solved for Qt 5.7.1. So please mark this thread as solved using the "Topic Tools" button so other forum users may know a solution has been found :)

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

Thank you for tip..I will check it..

@hariny , @onek24 Since this thread was not resolved; the buffer is not open !!! your are missing two lines of code: buffer->open(QIODevice::ReadOnly); buffer->seek(0);

Hi and welcome to devnet, QtMultimedia uses Apple's Media Foundation for it's OS X backend so the format supported depends on what Media Foundation can support. Can you try the same application using the latest version of Qt ?

Hi, Usually, to play sound effect, the QSoundEffect class is used. Wouldn't that fill your need ?

Hi and welcome to devnet, If you want the internal details you should check QtMultimedia's source code.

I'm not sure what happened with the code, but now it's finally giving me an error signal. The error and error string are QMediaPlayer::FormatError "Failed to load media" The media I'm attempting to load uses the file ending ".mp4". I finally thought of opening the media in Quicktime and, lo and behold, it won't open the file. It appears I'm dealing with a "Not a real operating system" error. EDIT: It appears that what happened was that I was trying to open a 0 byte file. Opening an .mp4 file with actual content still causes the MediaPlayer to get stuck in the LoadingMedia status.

Yes it's clearer. Then you should indeed do the synchronization at the source, it will be cleaner and easier.

This is happening to random videos or same videos for everytime? Perhaps you can try this in a different OS (Windows may be) to see if this is a platform specific issue.

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

@Xicor I have no idea, sorry. Maybe someone else knows that.

Yep, thank you but that is what I've talking about, in release about 40 ms on full HD frame. Better to find a way to get RGB frames, not YUV, but I don't know how that all works exactly.

I have opened the bug ticket https://bugreports.qt.io/browse/QTBUG-50460. Perhaps it is really a bug and will get fixed in the future ;D