GNOME Bugzilla – Bug 319340
[cdparanoia] uncorrected-error signal never fired
Last modified: 2006-02-17 16:15:41 UTC
When ripping CDs using the cdparanoia plugin in a gst-python program, the exposed uncorrected-error and smilie-change signals never seem to be fired, even when the CD is unreadable. This means it's impossible to know if the track was ripped successfully without listening to the resulting file.
Not sure how easy it is to fix that given that there isn't really an easy way to find our element object from within the paranoia_callback function (as far as I can tell, at least).
On second thought, we could serialise the cdparanoia_read() calls for all cdparanoiasrc instances that have the NEVERSKIP flag set via a global lock and then set a global variable to the currently reading element, but that seems rather ugly to me ...
amazing... serializing would be ugly but certainly possible.
Let's do that then. Got a patch for that somewhere, I'll see if I can find it.
2006-02-17 Tim-Philipp Müller <tim at centricular dot net> * ext/cdparanoia/gstcdparanoiasrc.c: (gst_cd_paranoia_src_class_init), (gst_cd_paranoia_dummy_callback), (gst_cd_paranoia_paranoia_callback), (gst_cd_paranoia_src_signal_is_being_watched), (gst_cd_paranoia_src_read_sector): * ext/cdparanoia/gstcdparanoiasrc.h: Add back 'transport-error' and 'uncorrected-error' signals and make them actually be fired when bad stuff happens (#319340).