[gstreamer-bugs] [Bug 350006] New: [LADSPA] after changing state from PLAYING to READY/NULL, going back to PLAYING doesn't work
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Fri Aug 4 17:52:01 PDT 2006
Do not reply to this via email (we are currently unable to handle email
responses and they get discarded). You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=350006
GStreamer | gst-plugins-good | Ver: HEAD CVS
Summary: [LADSPA] after changing state from PLAYING to
READY/NULL, going back to PLAYING doesn't work
Product: GStreamer
Version: HEAD CVS
Platform: Other
OS/Version: All
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: gst-plugins-good
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: gnome at jonobacon.org
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: 2.13/2.14
GNOME milestone: Unspecified
Please describe the problem:
Attached is a sample script that demonstrates this bug. I basically create
pipeline which feeds an ogg file through a LADSPA effect. I set the state to
PLAYING, and it plays fine, complete with the expected effect output. I then
switch to READY or NULL, which is fine, but when I set the state back to
PLAYING, things go horribly wrong.
I get different errors, depending on whether we go from READY or NULL. This is
after I have played it once. So, I first go from NULL to PLAYING, and it works,
and then I either set it to READY or NULL, and when I go to PLAYING I get
different errors:
>> From READY to PLAYING <<
** (ladspabug.py:9754): CRITICAL **: gst_signal_processor_setup: assertion
`self->state == GST_SIGNAL_PROCESSOR_STATE_NULL' failed
** (ladspabug.py:9754): CRITICAL **: gst_signal_processor_setup: assertion
`self->state == GST_SIGNAL_PROCESSOR_STATE_NULL' failed
** (ladspabug.py:9754): CRITICAL **: gst_signal_processor_setup: assertion
`self->state == GST_SIGNAL_PROCESSOR_STATE_NULL' failed
** (ladspabug.py:9754): CRITICAL **: gst_signal_processor_setup: assertion
`self->state == GST_SIGNAL_PROCESSOR_STATE_NULL' failed
** (ladspabug.py:9754): CRITICAL **: gst_signal_processor_setup: assertion
`self->state == GST_SIGNAL_PROCESSOR_STATE_NULL' failed
** (ladspabug.py:9754): CRITICAL **: gst_signal_processor_setup: assertion
`self->state == GST_SIGNAL_PROCESSOR_STATE_NULL' failed
** (ladspabug.py:9754): CRITICAL **: gst_signal_processor_setup: assertion
`self->state == GST_SIGNAL_PROCESSOR_STATE_NULL' failed
** (ladspabug.py:9754): CRITICAL **: gst_signal_processor_setup: assertion
`self->state == GST_SIGNAL_PROCESSOR_STATE_NULL' failed
** (ladspabug.py:9754): CRITICAL **: gst_signal_processor_setup: assertion
`self->state == GST_SIGNAL_PROCESSOR_STATE_NULL' failed
** (ladspabug.py:9754): CRITICAL **: gst_signal_processor_setup: assertion
`self->state == GST_SIGNAL_PROCESSOR_STATE_NULL' failed
I also check the error bus:
GStreamer encountered a general stream error.
gstoggdemux.c(2852): gst_ogg_demux_loop ():
/mixer/mycomposition1/audio1/internal-decodebin/oggdemux1:
stream stopped, reason not-negotiated
>> From NULL to PLAYING <<
** (ladspabug.py:9829): CRITICAL **: gst_signal_processor_process: assertion
`self->pending_out == 0' failed
** (ladspabug.py:9829): WARNING **: Unexpectedly empty buffer pen for pad
effect1:Output
** (ladspabug.py:9829): CRITICAL **: Something wierd happened...
** (ladspabug.py:9829): CRITICAL **: gst_signal_processor_process: assertion
`self->pending_out == 0' failed
** (ladspabug.py:9829): WARNING **: Unexpectedly empty buffer pen for pad
effect1:Output
** (ladspabug.py:9829): CRITICAL **: Something wierd happened...
** (ladspabug.py:9829): CRITICAL **: gst_signal_processor_process: assertion
`self->pending_out == 0' failed
** (ladspabug.py:9829): WARNING **: Unexpectedly empty buffer pen for pad
effect1:Output
** (ladspabug.py:9829): CRITICAL **: Something wierd happened...
** (ladspabug.py:9829): CRITICAL **: gst_signal_processor_process: assertion
`self->pending_out == 0' failed
** (ladspabug.py:9829): WARNING **: Unexpectedly empty buffer pen for pad
effect1:Output
** (ladspabug.py:9829): CRITICAL **: Something wierd happened...
** (ladspabug.py:9829): CRITICAL **: gst_signal_processor_process: assertion
`self->pending_out == 0' failed
** (ladspabug.py:9829): WARNING **: Unexpectedly empty buffer pen for pad
effect1:Output
** (ladspabug.py:9829): CRITICAL **: Something wierd happened...
** (ladspabug.py:9829): CRITICAL **: gst_signal_processor_process: assertion
`self->pending_out == 0' failed
** (ladspabug.py:9829): WARNING **: Unexpectedly empty buffer pen for pad
effect1:Output
** (ladspabug.py:9829): CRITICAL **: Something wierd happened...
** (ladspabug.py:9829): CRITICAL **: gst_signal_processor_process: assertion
`self->pending_out == 0' failed
** (ladspabug.py:9829): WARNING **: Unexpectedly empty buffer pen for pad
effect1:Output
** (ladspabug.py:9829): CRITICAL **: Something wierd happened...
** (ladspabug.py:9829): CRITICAL **: gst_signal_processor_process: assertion
`self->pending_out == 0' failed
** (ladspabug.py:9829): WARNING **: Unexpectedly empty buffer pen for pad
effect1:Output
** (ladspabug.py:9829): CRITICAL **: Something wierd happened...
** (ladspabug.py:9829): CRITICAL **: gst_signal_processor_process: assertion
`self->pending_out == 0' failed
** (ladspabug.py:9829): WARNING **: Unexpectedly empty buffer pen for pad
effect1:Output
** (ladspabug.py:9829): CRITICAL **: Something wierd happened...
** (ladspabug.py:9829): CRITICAL **: gst_signal_processor_process: assertion
`self->pending_out == 0' failed
** (ladspabug.py:9829): WARNING **: Unexpectedly empty buffer pen for pad
effect1:Output
** (ladspabug.py:9829): CRITICAL **: Something wierd happened...
I also check the error bus:
GStreamer encountered a general stream error.
gstoggdemux.c(2852): gst_ogg_demux_loop ():
/mixer/mycomposition1/audio1/internal-decodebin/oggdemux1:
stream stopped, reason error
Steps to reproduce:
1.
2.
3.
Actual results:
Expected results:
Does this happen every time?
Other information:
--
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the Gstreamer-bugs
mailing list