sound playback does not work with gtk-play apparently because the visualizations do not work. Generally speaking sound does work: e.g. gst-play is fine. Currently bug 11311 prevents accelerated video playback but even after fixing that (poky-contrib jku/gst-vaapi-fix branch) this keeps happening. gtk-play works if visualizations are disabled in the code. We really need better qa during multimedia stack upgrades :( I'll try to get a useful log...
Created attachment 3751 [details] GST_DEBUG=3 gtk-play a2002011001-e02.wav
Created attachment 3752 [details] GST_DEBUG_DUMP_DOT_DIR (final state)
This works: gst-launch-1.0 filesrc location=file.wav ! decodebin ! goom ! videoconvert ! xvimagesink Something goes wrong in playbin -- possibly where goom ends up adding "pixel-aspect-ratio 0/1" to props...
This works on debian (plays sound, shows visualization): gst-launch playbin uri=<audio-uri> vis-plugin=goom It plays on yocto as well but the visualization never ends up in the pipeline (I can see how the Playbin has a "vis-plugin=(GstGoom)goom0" property but the pipeline doesn't have the display branch at all). On debian the same pipeline has branches into audio and video playback... Not sure if this really is the same issue.
(In reply to comment #4) > This works on debian (plays sound, shows visualization): > gst-launch playbin uri=<audio-uri> vis-plugin=goom oops, forget that: debian defaults to gst-launch-0.10 ! The visualization is not included on debian either with 1.0
After looking at this for the day: My suggestion is we disable the visualizations. We can enable them later if they're seen as useful for something: so far (over a couple of years) they've just been easy to break and a hindrance to getting audio playback properly QAd. The only real drawback here is that the trivial fix is _very_ ugly: doing gst_player_set_visualizations_enabled(player, FALSE) leaves us with a drawingarea that nothing draws on: with matchbox that means the window is there for clicking but it's never updated and you see the window content below -- or whatever was the last thing on screen before the player window opened.
Also tested on the Intel NUC D54250WYK - sound doesn't work when we enable Visualizations in gtk-play.
Everything works on qemu btw (slowly but still). The only differences in the pipeline between qemu and the nuc: * pixel-aspect-ratio on qemu is "1/1" instead of "0/1" * the final videosink is XImagesink instead of VaapiImageSink
Created attachment 3754 [details] GST_DEBUG=3 gst-launch-1.0 audiotestsrc ! goom ! videoconvert ! vaapisink vaapisink doesn't behave as expected with audio visualisation elements (goom and synaescope)
Created attachment 3755 [details] GST_DEBUG=3 gst-launch-1.0 audiotestsrc ! synaescope ! videoconvert ! vaapisink
vaapisink works fine with videotestsrc. # gst-launch-1.0 videotestsrc ! vaapisink Also xvimagesink, ximagesink and glimagesink works well with audio visualization elements ( xvimagesink doesn't use the fullscreen though ) eg: # gst-launch-1.0 audiotestsrc ! goom ! videoconvert ! ximagesink works as expected.
Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=781759
I'm marking this fixed with commit 1565a2491847370939b87f6fd0c281b7f317ab1c Author: Jussi Kukkonen <jussi.kukkonen@intel.com> Date: Fri Apr 28 14:54:34 2017 +0300 gst-player: Disable visualizations as workaround Audio playback in gtk-play is broken with vaapi because the visualizations do not work: disable visualizations as workaround. This should be reverted as soon as [YOCTO #11410] is fixed. (From OE-Core rev: 1092a8d4bc78a53f60ad0137aeb08b31853db9eb) I've filed bug 11437 as the "root cause issue"