Can't play/record, "GStreamer general stream error"

[Pietro Battiston]

When trying to record or to play a track (from file) I get errors (and Jokosher doesn't record/play). In particular:
- when I try to record I get MESSAGE 1 in a pop-up window and MESSAGE 3 on terminal
- when I try to play I get MESSAGE 1 and, immediately after, MESSAGE 2 in pop-up windows, and MESSAGE 4 in terminal.

I'm running Jokosher from the "Jokosher0.2runscript" (that apparently worked smoothly, and apt-get ), on an Ubuntu 6.10 Edgy Eft, 64 bit version.

##########MESSAGE 1##################
Argh! Something went wrong and a serious error occurred:

The stream is in the wrong format.

gstbasesrc.c(1833): gst_base_src_start (): /timeline/playbackbin/clickbin/click:
Check your filtered caps, if any

It is recommended that you report this to the Jokosher developers or get help at http://www.jokosher.org/forums/
##########MESSAGE 1 END##################

##########MESSAGE 2##################
 Argh! Something went wrong and a serious error occurred:

 GStreamer encountered a general stream error.

 gstbasesrc.c(1610): gst_base_src_loop ():
 /timeline/playbackbin/Instrument_0/gnlcomposition0/gnlsource0/audiotestsrc1:
 streaming task paused, reason not-linked (-1)

 It is recommended that you report this to the Jokosher developers or get help at http://www.jokosher.org/forums/
##########MESSAGE 2 END##################

##########MESSAGE 3##################
0:00:39.987293000 28148 0x794cf0 ERROR basesrc gstbasesrc.c:1934:gst_base_src_activate_push:<click> Failed to start in push mode
##########MESSAGE 3 END##################

##########MESSAGE 4##################
0:00:43.182616000 28043 0x8e5030 ERROR basesrc gstbasesrc.c:1934:gst_base_src_activate_push:<click> Failed to start in push mode
Traceback (most recent call last):
  File "/home/pietro/Jokosher0.2checkout/jokosher/Jokosher/Project.py", line 679, in newPad
    pad.link(convpad)
gst.LinkError: <enum GST_PAD_LINK_NOFORMAT of type GstPadLinkReturn>
##########MESSAGE 4 END##################

I can give any additional information that's needed, and do some Python testing, but am not quite skilled in Pyhton to start understanding something about Jokosher code in a reasonable time.

[Laszlo Pandy (laszlok)]

We've seen this before but I still don't know what causes it, and it always seems to go away on its own. Can you reproduce it reliably? Also if you want to come into #jokosher on freenode, we can give you instructions on how to get Jokosher trunk running with the install script, so we can see if this still happens on the latest Jokosher.

[Pietro Battiston (toobaz)]

I'm adding the complete log of this situation:

1) I open jokosher
2) I add an Instrument
3) I import an audio wav file
4) i press "play"
5) Jokosher pops up the errors
6) I close Jokosher

(notice that the errors happen EVERY time I try to record or play)

[Dave Morley (davmor2)]

This is still a problem in Feisty. Plenty of errors and no music. I have a niggling feeling that this is a gstreamer or python (64bit) issue and should be reported to them. This same issue is not in effect on my 32bit laptop.

[Dave Morley (davmor2)]

This is fixed if you install a fresh copy of ubuntu feisty post 19/01/07 yeah it works in 64bit. :)

[Edward Hervey (bilboed) (bilboed-deactivatedaccount)]

This this extremely similar to the issue which is now fixed in gnonlin cvs (release today if everything goes well).

[Vivianne Langdon (vivicat)]

I am still getting this problem. I haven't tried to PLAY audio, but I get that when recording.

[Vivianne Langdon (vivicat)]

I have 0.9 and the latest gstreamer, by the way

[Pietro Battiston (toobaz)]

Trying a Jokosher 0.9 on my Feisty, I'm finally noticing that I can actually load files an play.

But recording still doesn't work. Now the error it gives is different:

gstbasesrc.c(1865): gst_base_src_start (): /timeline/bin4/alsasrc3:
Check your filtered caps, if any

and, when I click "stop":

Could not determine type of stream.

gsttypefindelement.c(737): gst_type_find_element_activate (): /pipeline1/decodebin3/typefind

Honestly I'm wondering about the "incomplete" and "undecided" tags. This bug makes Jokosher quite useless. If some info/testing is needed, just write me: toobaz AT email DOT it. I will be proud to help.

[gareth (gareth-redhat-bugs)]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6

Description of problem:
I had recording working fine with Jokosher and FC7, however, since the last gstreamer update came through Yum it has stopped working.

I arm an instrument, and press record, the time line starts to fill up for a second, then stops. Jokosher still responds and behaves as though recording is going ahead.

I can press the record button again after this point to stop it. Then, an error message dialog appears, its gstreamer type stuff, but basically its telling me that it can't find the track it thinks it just recorded.

Version-Release number of selected component (if applicable):
latest

How reproducible:
Always

Steps to Reproduce:
1. Install Jokosher
2. Try to record something
3.

Actual Results:
Recording fails

Expected Results:
Recording works as it used to

Additional info:
Working on a laptop with FC7, all updates from Yum (stable), and an external USB sound card (TASCAM US122). I doubt this has anything to do with the sound card it, worked fine for ages.

[Christopher (christopher-redhat-bugs)]

Thanks for tackling bugzilla and filing the bug report Gareth.

In order for me to peer further into it, I need the gstreamer info. It should be
easily copiable from the dialog box. Any other info would be appreciated -
gstreamer version (I'm assuming 10.13).

Cheers
Chris

[gareth (gareth-redhat-bugs)]

gstreamer-0.10.13-0.1.fc7

[Christopher (christopher-redhat-bugs)]

Sorry, I wasn't clear enough. I need the debugging output you mentioned. As in:

"Then, an error message dialog appears, its gstreamer type stuff,..."

Cheers
Chris

[gareth (gareth-redhat-bugs)]

Error loading file: None

Please make sure the file exists, and the appropriate plugin is installed.

Could not determine type of stream.

gsttypefindelement.c(737): gst_type_find_element_activate ():
/pipeline2/decodebin5/typefind

[gareth (gareth-redhat-bugs)]

Okay, I banged that info in there quick this time, last time, I took a few
moments while the dialog was still on screen and the whole machine locked up.

I noticed the HDD light was flashing away as responsiveness slipped away. I
wonder if something is sat in a loop allocating memory?

[Christopher (christopher-redhat-bugs)]

(In reply to comment #5)
> Okay, I banged that info in there quick this time, last time, I took a few
> moments while the dialog was still on screen and the whole machine locked up.

Yuck.

> I noticed the HDD light was flashing away as responsiveness slipped away. I
> wonder if something is sat in a loop allocating memory?

I'd be inclined to re-file for gstreamer, might be a dupe of:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=251556

Could you run through gdb and post output? I am (fortunately by the sounds of
it) unable to reproduce here.

Cheers
Chris

[gareth (gareth-redhat-bugs)]

Hmm, won't crash again, GDB or no.

I didn't see anything useful sticking python through GDB tbh.

I also tried this without using my external sound card for a laugh, same story
with the on board one.

[Christopher (christopher-redhat-bugs)]

Could you try the following:

http://snecker.fedorapeople.org/jokosher-0.9-5.fc7.noarch.rpm

It is the latest svn snapshot, pretty much RC for jokosher 1.0 so all the usual
caveats apply.

Cheers
Chris

[Christopher (christopher-redhat-bugs)]

(In reply to comment #7)
> Hmm, won't crash again, GDB or no.
>
> I didn't see anything useful sticking python through GDB tbh.

No and I have no idea why I asked you to do this. Maybe I meant Pdb :/

> I also tried this without using my external sound card for a laugh, same story
> with the on board one.

Okay, will need to nail this down to gstreamer or python or possibly gnonlin. I
have copied this to the upstream bugtracker as it looks like a regular issue:

https://bugs.launchpad.net/fedora/+source/jokosher/+bug/76047

Might need to appoint you as chief Fedora debugger if that is okay as I can't
reproduce at the moment.

Cheers
Chris

[gareth (gareth-redhat-bugs)]

I really want to try that out, but was out all last night, and probably will be
tonight.

I'm off on holls tomorrow, but if I get chance, I'll try it out tonight. If not,
it'll be a week before I can.

[John (john-redhat-bugs)]

your package doesn't work. I get the same errors.

Error dialog:

Error loading file: None

Please make sure the file exists, and the appropriate plugin is installed.

Could not determine type of stream.

gsttypefindelement.c(737): gst_type_find_element_activate ():
/pipeline0/decodebin1/typefind

Output of jokosher -d:

Filling LADSPA Registry
         0 LADSPA effects loaded
        Reading in presets...
        ...done.
Cannot find "lame" plugin, disabling encoder: "lame"
Loading extensions:
        importing extension APIConsole-0.1-py2.4.egg
                ...failed.
No module named Globals
        importing extension jokosher-dbus.py
        importing extension GNOMEAudioProfiles.py
        importing extension Minimal-0.9-py2.4.egg
        importing extension ExtensionConsole-0.2-py2.5.egg
        importing extension SetTempo-0.1-py2.4.egg
        importing extension FreesoundSearch-0.2-py2.4.egg
        importing extension InstrumentTypeManager-0.2-py2.4.egg
        importing extension PidginExtension-0.1-py2.5.egg
Attempting to open: /home/quinticent/we/we.jokosher
Using autoaudiosink for audio output
added project playback bin to the pipeline
added adder0 to project playbackbin
added levelcaps to project playbackbin
added MasterLevel to project playbackbin
added autoaudiosink0 to project playbackbin
Loading project file version 0.9
added instrument playbackbin to adder playbackbin 0
linked instrument playbackbin to adder (project)
LOG COMMAND: ('P', 'DeleteInstrument', [0]) from 148775564
can record
pre-record state: GST_STATE_NULL
unlinked instrument playbackbin from adder
removed instrument playbackbin from project playbackbin
create file source
Using pipeline: alsasrc device=hw:0 ! audio/x-raw-int,rate=44100 ! audioconvert
! level name=recordlevel interval=10000000 ! audioconvert ! flacenc ! filesink
location=/home/quinticent/we/audio/Vocal_0_1188924821.ogg
Recording in single-input mode
Using input track: 0
adding recordingbin
play() in Project.py
current state: GST_STATE_NULL
Preparing the controller
FADE POINT: time(0.00) vol(0.99)
FADE POINT: time(0.00) vol(0.99)
Set extra zero fade point
just set state to PAUSED
STATE CHANGED
-- status: GST_STATE_CHANGE_NO_PREROLL
-- pending: GST_STATE_VOID_PENDING
-- new: GST_STATE_PAUSED
Stop pressed, about to set state to READY
current state: GST_STATE_PAUSED
LOG COMMAND: ('I0', 'DeleteEvent', [1]) from 148736556
Terminating recording.
State just set to READY
Removing recordingEvents bin
set state to NULL
added instrument playbackbin to adder playbackbin 0
linked instrument playbackbin to adder (project)
Event bus error: Could not determine type of stream. gsttypefindelement.c(737):
gst_type_find_element_activate (): /pipeline0/decodebin1/typefind
LOG COMMAND: ('I0', 'ResurrectEvent', [1]) from 148810380
Stop pressed, about to set state to READY
current state: GST_STATE_READY
Terminating recording.
State just set to READY

[Christopher (christopher-redhat-bugs)]

(In reply to comment #11)
> your package doesn't work. I get the same errors.

Cool, thanks for the debugging info John. This is upstream (has been for a
while) and is one of the main blockers for the 1.0 release. I've started pulling
occasional svn snapshots for F8 though it isn't fixed yet so don't get too
optimistic. A little investigation shows its a suspected API breakage so pulling
gstreamer 0.10.14 might resolve it. I'm unable to reproduce at the moment as it
seems happy with my basic laptop sound card hardware.

I'm changing this to verified and will keep a beady eye on upstream.

Cheers
Chris

[Laszlo Pandy (laszlok)]

If this is confirmed, then its critical. Although it might have already been fixed by the awesome gstreamer folks. More investigation is needed tomorrow at the hackfest.

[Pietro Battiston (toobaz)]

I can confirm it with a just compiled CVS Gstreamer.

[Laszlo Pandy (laszlok)]

No way I can reproduce this. If someone can please add a comment.

[Christopher Brown (snecklifter)]

Appears to be fixed in gstreamer 0.10.14 - please test and report.

[Christopher (christopher-redhat-bugs)]

Folks,

Kindly pull gstreamer 0.10.14 from the development repositories and test as
discussion with the jokosher developers indicates this is now fixed. Alternately
test in F8. I'll give it a week or so and if I hear nothing will re-assign to
gstreamer or close.

Cheers
Chris

[John Green (john-thegreens)]

Looking at the Red Hat bug thread attached to this it appears to actually be bug #85793 which is fixed in gstreamer CVS currently (checkout on 2007-09-12 works). gstreamer 0.10.14 still gives the error. I don't know if gstreamer people are planning a bug fix release in time for the next round of distro upgrades. Here's hoping.

[Pietro Battiston (toobaz)]

Tested yesterday in cvs gstreamer - I still can't record.

[gareth (gareth-redhat-bugs)]

I'd love to test this (I'm on the verge of forgetting another batch of nice
riffs), but its not in testing yet, and there are too many deps for me to risk
the F8 version (I think).

[gareth (gareth-redhat-bugs)]

Urgh! F8 isn't out for 2 months odd, will this actually make F7?

[Christopher (christopher-redhat-bugs)]

(In reply to comment #14)
> I'd love to test this (I'm on the verge of forgetting another batch of nice
> riffs), but its not in testing yet, and there are too many deps for me to risk
> the F8 version (I think).

"The power of the riff compels me"

No chance will gstreamer-0.10.14 make F7. We went through this for F6 as well
I'm afraid.

Option 1)

foo@bar $ yum update gstreamer* --enablerepo=development

Option 2)

Fedora 8 Test 2

Option 3)

http://www.jokosher.org/setting-up-cvs-gstreamer

Sorry gareth, I wish I had better news.

Regards
Chris

[Pietro Battiston (toobaz)]

I also have to say that, looking to the bug #85793
<https://bugs.launchpad.net/bugs/85793> description, that to me it
really doesn't seem the same bug. I just can't record even the first
time, and adding another instrument doesn't help.

[Pēteris Krišjānis (pecisk-gmail)]

I can suggest that that could be already known problems with sound card capacities; you also should check if output for soundcard is blocked via other media players, etc. because first error suggests that Jokosher can't play click track.

Anyway, this should be tested again with Autoselect setting for Recording Sample Rate and reported again here.

[Pietro Battiston (toobaz)]

Done. I finally could record. The error comes with both 44000 and 48000,
but not with "autodetect".

Great job.

[gareth (gareth-redhat-bugs)]

Hello from F8 Test 2. Still don't work. Urgh.

# rpm -q gstreamer
gstreamer-0.10.14-3.fc8

[Christopher (christopher-redhat-bugs)]

Hi Gareth,

I've just kicked off a Koji build:

http://koji.fedoraproject.org/koji/taskinfo?taskID=178560

Rather than wait until it finds its way you could d/l from there and see if it
helps at all. I'm _really_ tempted to re-assign this to the gstreamer bods
though as they might be able to carry a patch for F-7 and F-8 which resolves
this. I'm waiting to see if one particular patch can be identified however.

Cheers
Chris

[gareth (gareth-redhat-bugs)]

Hmm,

Old project that I opened did the same old thing when I tried to record.

A new one gives me this instead ...

Argh! Something went wrong and a serious error occurred:

Internal GStreamer error: clock problem. Please file a bug at
http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.

gstpipeline.c(568): gst_pipeline_change_state (): /timeline:
Pipeline cannot operate with selected clock

It is recommended that you report this to the Jokosher developers or get help at
http://www.jokosher.org/forums/

[Christopher (christopher-redhat-bugs)]

(In reply to comment #19)

> Internal GStreamer error: clock problem. Please file a bug at
> http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.

Okay, re-assigning then. Lets see what they have to say.

[gareth (gareth-redhat-bugs)]

This is still rumbling on, afaik, Fedora will need 0.10.15 to get Jokosher
working again.

Will this update will be included?

[Christopher (christopher-redhat-bugs)]

(In reply to comment #21)
> This is still rumbling on, afaik, Fedora will need 0.10.15 to get Jokosher
> working again.
>
> Will this update will be included?

Fedora 8 now has gstreamer 0.10.15 - are you still on Fedora 7 or have you upgraded?

[gareth (gareth-redhat-bugs)]

I've packed in using Jokosher, Ardour wipes the floor with it, sadly for GStreamer.

[Christopher (christopher-redhat-bugs)]

Sorry to hear it Gareth but understandable given how long this bug has been
running on for now. Closing INSUFFICIENT_DATA - not that we didn't get enough
from you but because we're not going to be able to get any more. Thanks anyway
for taking the time to report this.