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 133897 - Internal GStreamer error: seek problem
Internal GStreamer error: seek problem
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.7.4
Other FreeBSD
: Normal normal
: 0.8.2
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-02-09 15:49 UTC by Joel
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description Joel 2004-02-09 15:49:50 UTC 
A select number of my MP3s refuse to play in rhythmbox, but play fine
through gst-launch-ext.  Rhythmbox complains with: Internal GStreamer
error: seek problem. File a bug.  
When I run the pipeline listed in the rhythmbox README I get this:
>gst-launch gnomevfssrc location=./opeth-patterns.mp3 ! spider ! volume !
osssink
RUNNING pipeline ...
ERROR: from element /pipeline0/spider0/id3tag1: Internal GStreamer error:
seek problem.  File a bug.
Additional debug info:
gstid3tag.c(892): gst_id3_tag_chain: /pipeline0/spider0/id3tag1:
can't seek back to beginning from reading ID3v1 tag
Execution ended after 29 iterations (sum 44247000 ns, average 1525758 ns,
min 41000 ns, max 15571000 ns).

I've posted one of the mp3s that have this behavior at:
http://homepage.mac.com/joeldiaz/freebsd/opeth-patterns.mp3

iTunes reports the ID3 tag as version 2.3.

Thanks,
Joel
Comment 1 Joel 2004-02-09 23:41:34 UTC 
I also thought I might add that I'm running libmad-0.15.0b and
libid3tag-0.15.0b.

Joel
Comment 2 Benjamin Otte (Company) 2004-02-12 16:09:59 UTC 
Yeah, gst-launch can't differentiate between tagged and untagged 
mp3s while spider can do that...

Anyway, the problem is that you have 2 ID3 tags at the beginning of 
the file which is something id3tag can't cope with.
Comment 3 Joel 2004-02-12 22:46:53 UTC 
So is this considered a bug?  Do I forward this along to someone else (the group 
responsible for libid3tag)?
Comment 4 Benjamin Otte (Company) 2004-02-17 17:53:34 UTC 
It's a bug with the GStreamer id3tag element.
Sorry if that wasn't clear :)
Comment 5 Benjamin Otte (Company) 2004-04-29 00:13:34 UTC 
this is fixed in current cvs