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 573772 - MP3 file import fails
MP3 file import fails
Status: RESOLVED FIXED
Product: pitivi
Classification: Other
Component: General
Git
Other Linux
: Normal major
: 0.13.1
Assigned To: Alessandro Decina
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-02 15:25 UTC by Jean-François Fortin Tam
Modified: 2009-04-30 08:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
output of PITIVI_DEBUG=*:5 GST_DEBUG=2 bin/pitivi > log 2>&1 (19.10 KB, application/octet-stream)
2009-03-02 15:26 UTC, Jean-François Fortin Tam
Details
sample (518.20 KB, audio/mpeg)
2009-03-02 15:32 UTC, Jean-François Fortin Tam
Details

Description Jean-François Fortin Tam 2009-03-02 15:25:09 UTC
I have the fluendo mp3 plugin (as well as good/bad/ugly), and trying to import any mp3 file fails with the following information:

URI:/home/jeff/2.mp3
Problem:An internal error occured while analyzing this file: Erreur interne de flux de données.
Extra information:gstbasesrc.c(2234): gst_base_src_loop (): /GstPipeline:Discoverer-file:///home/jeff/2.mp3/GstFileSrc:src-file:///home/jeff/2.mp3:
streaming task paused, reason not-linked (-1)


Importing ogg vorbis files works fine.
Importing flac files works, but they cannot be seeked in the timeline.
Comment 1 Jean-François Fortin Tam 2009-03-02 15:26:02 UTC
Created attachment 129858 [details]
output of PITIVI_DEBUG=*:5 GST_DEBUG=2 bin/pitivi > log 2>&1
Comment 2 Jean-François Fortin Tam 2009-03-02 15:32:40 UTC
Created attachment 129860 [details]
sample
Comment 3 Alessandro Decina 2009-03-11 12:25:26 UTC
this was fixed in master (5770a89452bd332f6339b9c33e0e2cf1f0557c61)
Comment 4 Edward Hervey 2009-03-11 21:58:37 UTC
still fails
Comment 5 Alessandro Decina 2009-03-12 16:18:59 UTC
had a closer look at this, 4cb4e62ba2c429bb103d7f5b96ec28bed4dc380a and d5cbac4c3434e3eef0dd183cc57347c7863b4a1f (in master) hopefully fix it.
Please try again?
Comment 6 Jean-François Fortin Tam 2009-03-19 15:00:49 UTC
it seems to work if you remove all fluendo plugins and use the good/bad/ugly. How should this be handled then? Maybe detect them and warn the user about it in a meaningful manner?
Comment 7 Alessandro Decina 2009-03-25 14:45:31 UTC
if 3rd party plugins are broken we can't really do much
Comment 8 Jean-François Fortin Tam 2009-03-25 21:06:12 UTC
Can't you just check for the presence of those plugins and ignore them, and use gst bad/ugly specifically? Or at least an error message that is meaningful so that the user knows that the blame is on those third party plugins?