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 136962 - crc error when decoding flac with typefind and threads
crc error when decoding flac with typefind and threads
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.7.6
Other Linux
: Normal normal
: 0.8.6
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-03-12 07:30 UTC by Andy Hanton
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andy Hanton 2004-03-12 07:30:03 UTC
When I try to run a simple flac player that uses the typefind element and 
threads, it plays for 5 to 15 seconds and then stops.  Sometimes it gives
an error message and other times it consumes 100% cpu and hangs.  I tried
about 8 different flac files ripped from different albums and the problem
occured with all of them.  I am running gstreamer 0.7.6.  The command that
fails is:

gst-launch-0.8 \{ filesrc location=test.flac \} ! \{ queue ! typefind !
flacdec ! audioconvert ! osssink \}
RUNNING pipeline ...
ERROR: from element /pipeline0/thread1/flacdec0: Could not decode stream.
Additional debug info:
gstflacdec.c(308): gst_flacdec_error_callback: /pipeline0/thread1/flacdec0:
lost sync
ERROR: from element /pipeline0/thread1/flacdec0: Could not decode stream.
Additional debug info:
gstflacdec.c(308): gst_flacdec_error_callback: /pipeline0/thread1/flacdec0:
CRC mismatch


these commands work fine:
gst-launch-0.8 \{ filesrc location=test.flac \} ! \{ queue ! flacdec !
audioconvert ! osssink \}

gst-launch-0.8 filesrc location=test.flac ! typefind ! flacdec !
audioconvert ! osssink
Comment 1 Ronald Bultje 2004-10-01 12:44:32 UTC
Typefind used to send a non-sensical discont event. I removed that, which should
fix this. Please retest and reopen if it is still buggy.