[gstreamer-bugs] [Bug 349902] [LADSPA] implement sources

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=349902
  GStreamer | gst-plugins-bad | git

--- Comment #6 from Jon Nordby <jononor at gmail.com> 2009-12-05 23:34:45 UTC ---
gst-launch-0.10 ladspa-logistic ! audioconvert ! alsasink
gst-launch-0.10 ladspa-analogueOsc ! audioconvert ! alsasink
gst-launch-0.10 ladspa-sinCos ! audioconvert ! alsasink

All end being stuck in PREROLLING:
[jon at jon-laptop jonnors-mypaint-clone]$ gst-launch-0.10 ladspa-analogueOsc !
audioconvert ! alsasink
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
^CCaught interrupt -- handling interrupt.
Interrupt: Stopping pipeline ...
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
Freeing pipeline ...

I'm thought I tried adding can-activate-pull=TRUE to alsasink and it gave the
same result. But now I'm getting a segfault on each invokation. Sometimes it
reaches "Pipeline is PREROLLING" and sometimes it doesnt:

[jon at jon-laptop ~]$ gst-launch-0.10 ladspa-sinCos ! audioconvert ! alsasink
can-activate-pull=TRUE
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...

** (gst-launch-0.10:17964): CRITICAL **: gst_signal_processor_prepare:
assertion `GST_SIGNAL_PROCESSOR_IS_RUNNING (self)' failed
Caught SIGSEGV accessing address 0x38
Spinning.  Please run 'gdb gst-launch 17964' to continue debugging, Ctrl-C to
quit, or Ctrl-\ to dump core.
^CCaught interrupt -- handling interrupt.
Interrupt: Stopping pipeline ...
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
^C
[jon at jon-laptop ~]$ gst-launch-0.10 ladspa-sinCos ! audioconvert ! alsasink
can-activate-pull=TRUE
Setting pipeline to PAUSED ...

** (gst-launch-0.10:17985): CRITICAL **: gst_signal_processor_prepare:
assertion `GST_SIGNAL_PROCESSOR_IS_RUNNING (self)' failed
Caught SIGSEGV accessing address 0x38

This is on current stable of gstreamer and plugins (bad+good+base).
I will try to see if the issue persists in git version and file a new bug if
that is the case.

-- 
Configure bugmail: https://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.