After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 754463 - Gstreamer ERROR: Playing wav, mp3, ogg, vox file format
Gstreamer ERROR: Playing wav, mp3, ogg, vox file format
Status: RESOLVED DUPLICATE of bug 754462
Product: GStreamer
Classification: Platform
Component: dont know
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-09-02 14:47 UTC by raj
Modified: 2015-09-03 09:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description raj 2015-09-02 14:47:53 UTC 
Hi all, 

I have couple of questions here.

1. when I trying to play ogg file through the pipeline, getting the following error.
Got message: error

ERROR: Internal data flow error.

Debug details: gstbasesrc.c(2943): gst_base_src_loop (): /GstPipeline:audio_pipeline/GstBin:bin_playback/GstFileSrc:filesource:
streaming task paused, reason error (-5)


2. 
gst-launch-1.0 filesrc location=music.ogg ! oggdemux ! vorbisdec ! audioconvert ! audioresample ! alsasink
Setting pipeline to PAUSED ...
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstAlsaSink:alsasink0: Could not open audio device for playback.
Additional debug info:
gstalsasink.c(863): gst_alsasink_open (): /GstPipeline:pipeline0/GstAlsaSink:alsasink0:
Playback open error on device 'default': No such file or directory
Setting pipeline to NULL ...
Freeing pipeline ...

Even this will not play for mp3, wav, vox, and ogg file.

Please any one can help me on this, and your help much appriciated.


Regards, Rajkumar
Comment 1 Marcin Kolny (IRC: loganek) 2015-09-03 08:59:11 UTC 
It's not mm-related bug. I'm setting "product" to GStreamer.
Comment 2 Tim-Philipp Müller 2015-09-03 09:16:43 UTC 

*** This bug has been marked as a duplicate of bug 754462 ***