Jokosher fails to record

[Jono Bacon]

 * Add a new instrument - hit record, it works.
 * After recording, hit record again, and this error happens:

    Resource busy or not available.

    gstalsasrc.c(608): gst_alsasrc_open (): /timeline/bin4/alsasrc3:
    Device 'hw:0' is busy

 * This problem is repeatable (after the previous bug, close Jokosher and restart the steps) for a while and then we get this happen the first time you try to record.

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

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

[John Green (john-thegreens)]

I get this too. What seems to happen on my system is that if audio output is left to default then I get 'hw:0 busy' on the second record. If I alter (Edit>Preferences) audio output to ALSA and then select the right card then I get the 'Pipeline cannot operate with selected clock' most of the time. However if I clear the error box and then press stop and clear the two error boxes after that, then press record again and repeat the cycle several times it eventually starts recording.

I also found that adding a second instrument (and not using it) *always* clears the error and recording works normally so I can use this as a workaround for now.

======= setup ================
jokosher: svn r1335
gstreamer: version 0.10.11
gnonlin: 0.10.7
soundcard: CM8738
os: ubuntu edgy
===========================

I have a feisty installation running under vmware and I have absolutely no recording issues at all although this probably uses some software emulation rather than a real sound card.

[Onkar Shinde (onkarshinde)]

Confirmed on feisty with latest updates and jokosher svn.

[Kevin_Jim (zeuslinux)]

I also get the same error on Feisty with all the updates and Jokosher svn ( updated ).

[Jono Bacon (jonobacon)]

I don't get this on a recent build of GStreamer. Could other people please test.

[Jono Bacon (jonobacon)]

Further testing on this from John and Laszlo suggests this bug is fixed in GStreamer.

[Kevin Smith (thirdwiggin)]

I see the "Pipeline cannot operate" error immediately upon my first attempt at recording. I have a brand new checkout of Jokosher from Gutsy.

[bojo42 (bojo42)]

I can confirm the bug on Gutsy with Jokosher from universe:

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

[Brady Merriweather (brady-merriweather)]

Can duplicate here's step by step:
============= error =====================
Argh! Something went wrong and a serious error occurred:

Resource busy or not available.

gstalsasrc.c(596): gst_alsasrc_open (): /timeline/bin3/alsasrc5:
Device 'hw:0' is busy

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

[artemis (demonicartist)]

I am running in the same problem............here is the error log:

1. With audio output pluggin set to "AutoDetect"
********************************************
Argh! Something went wrong and a serious error occurred:

Resource busy or not available.

gstalsasrc.c(596): gst_alsasrc_open (): /timeline/bin10/alsasrc14:
Device 'hw:0' is busy

It is recommended that you report this to the Jokosher developers or get help at http://www.jokosher.org/forums/
**********************************************************************8
2. When ALSA is selected as the audio output plugign

+++++++++++++++++++++++++++++++++++++++++++
Argh! Something went wrong and a serious error occurred:

Could not open resource for writing.

gstalsasink.c(626): gst_alsasink_open (): /timeline/playbackbin/alsasink1:
Playback open error on device 'value': No such file or directory

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

Is there a solution for this problem ?

[Laszlo Pandy (laszlok)]

@artemis

1. This looks like this bug. Notice it is failing to open the alsasrc (ALSA *input*), thus it fails to record, as the title of this bug describes.
2. This is entirely different. Notice that it is failing open alsasink (ALSA *output*). This is a problem with playback and it not related to this recording bug.

However I do have a solution for the 2nd problem. It is trying to set the device to "value" which used to be the default in preferences unless you chose a device. I think your config file might be keeping it from when you used an older version of Jokosher. To fix it just open ~/.jokosher/config with your favourite text editor and under the heading "[Playback]" change "device = value" to "device = default".

[artemis (demonicartist)]

 "[Playback]" had "device = default" but still, jokosher failed to do any playback. Then, I also modified the /etc/modprobe.d/alsa-base by changing the "install sound-slot-0 /sbin/modprobe snd-card-0" to
"install sound-slot-o /sbin/modprobe snd_hda_intel"........... After these two modifications, playback is fine.
Thanks Laszlo.

But still fails to do any recording. I still get the same errors as before. Has anyone found a solution yet ?

[bojo42 (bojo42)]

i tried the latest svn right now on an uptodate Ubuntu 7.10 with default gstreamer and guess what ;)

gstalsasrc.c(596): gst_alsasrc_open (): /timeline/bin3/alsasrc1:
Device 'hw:0' is busy

@Jono & Laszlo: what gstreamer version do you both use, since you don't suffer from this bug? is the gutsy one too old?

[aimdeey (aimdeey)]

When I'm trying to record, it says:

-----
Ocurrió el siguiente error grave:

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

Es recomendable que reporte este fallo a los desarrolladores de Jokosher o busque ayuda en http://www.jokosher.org/forums/
-----

And when I stop recording:

-----
Error cargando el archivo: None

Por favor asegúrese que el archivo existe, y el plugin apropiado está instalado.

No se pudo determinar el tipo de flujo.

gsttypefindelement.c(735): gst_type_find_element_activate (): /pipeline2/decodebin5/typefind
-----

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

bojo42: this is seperate bug because something (I guess esound daemon) blocks your sound card. You can try to switch it off (System => Preferences => Sound => Sounds => Activate ESD), and try again.

aimless.destiny: it is known issue when your device can't provide bitrate/sample rate combination you request. This will be dealed with in futher releases.

[Andrea Grandi (andreagrandi)]

The bug is still present in Ubuntu Hardy 8.04....... how long does it take to fix it :( ???

[Laszlo Pandy (laszlok)]

Re:Andrea Grandi
Unfortunately for this bug "fixed" isn't as straightforward as your comment would suggest. Recording with or without other instruments playing in the background has worked for a long time for me. I just tested it now and it still works. So for some people this bug is fixed. This is a recording bug, and recording performance largely depends on what sound card you are using.

If you could give us some more helpful information such a better description and the error messages that you get in the gui and the terminal, maybe we can find out what the problem with your recording is.

[kenden (kenden)]

I get this error in jokosher 0.10.1 on Ubuntu 8.10 (x86)
I try using ALSA or Autodetect but get the same error.
Note: recording works fine with the Sound Recorder (gnome-sound-recorder 2.24.0.1).
Sound device used: Intel 82801DB-ICH4 on Dell Latitude D400.

When pressing Record, I get the error:

Argh! Something went wrong and a serious error occurred:

Resource busy or not available.

gstalsasrc.c(630): gst_alsasrc_open (): /GstPipeline:timeline/GstBin:bin3/GstAlsaSrc:alsasrc1:
Device 'hw:1' is busy

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

And in the console:

media@umedia:~$ jokosher
*Project Error*
Code: 4, Domain: gst-resource-error-quark
Message: Could not open audio device for recording. Device is being used by another application.

Any other log I can provide please let me know!