Re: [Rosegarden-user] Res: Audio software crisis in Linux? Or am I doing something wrong?

[Fabricio R. <roc...@ya...>]

Heheh, I thought that Audacity had a little more prestige among Linux audio users! :)

Actually, I used Audacity because:

1) I already knew how to use it, which was not the case of Ardour (I'm trying to learn it now, doing some good progress).

2) Because it worked, even if somehow buggy. Previously, I had used Rosegarden for doing all my music, audio included, but now I could not have it working without sudden stops.

3) I have done very simple, mono direct recording from the mixer in some of my band's rehearsals, so a simple recorder was enough (Audacity, AFAIK, can do multitrack as well, but I really did not need it for recording rehearsals).

4) I tried ReZound some years ago and it was really, really buggy back then. Maybe it's time for a new attempt...

	My soundcard is a simple SoundBlaster Audigy 2 ZS, not a FireWire one. I am not sure about the hardware but it seems to be OK. But I might tell that I constantly get some "codec_read" errors during boot, and I don't know exactly where do they come from. Looks like an ACPI-support problem, but I really don't know.


Thanks to everyone!

Fabricio Rocha
Brasilia, Brasil


Tomasz Grzelak escreveu:
> I would rather ask 'why not Rezound instead of Audacity'? Try Rezound to 
> see if you still get xruns.
> Another question - are you sure everything's fine with your hardware? 
> besides, IRQs and their priorities are really important thing, so it's 
> another case you should focus on.
> And do you have an internal soundcard (on a pci) or a firewire one? In 
> the second case, some firewire chipsets are known to not behave well, 
> and such problems are quite common when using such hardware (afaik they 
> are via chipsets)
> 
> 2009/11/6 Christopher Cherrett <st...@tr... 
> <mailto:st...@tr...>>
> 
>     -------- Original Message  --------
>     Subject: [Rosegarden-user] Res: Audio software crisis in Linux? Or
>     am I    doing something wrong?
>     From: Fabricio Rocha <roc...@ya...
>     <mailto:roc...@ya...>>
>     To: Tomasz Grzelak <tgr...@gm... <mailto:tgr...@gm...>>
>     Cc: lin...@li...
>     <mailto:lin...@li...>,
>     ard...@li...
>     <mailto:ard...@li...>,
>     ros...@li...
>     <mailto:ros...@li...>
>     Date: 11/05/09 20:31
> 
>         Updates to everyone who tried to help:
> 
>         I have compiled kernel 2.6.29.6 with the famous Ingo Molnar -rt
>         patch (I have been using the vanilla realtime, "preemptible
>         kernel" option for a while, thinking that it was already all the
>         realtime stuff officially integrated to the kernel). But the
>         problems persisted and I did not knew what else to do. There is
>         also no sign of news in JACK world, nor something too old, so it
>         seemed to me that if there was a real bug in JACK, I would not
>         be the only one to complain.
> 
>         Playing around with the configurations, I was able to surpass
>         the problem I had with Hydrogen segfaulting at start when JACK
>         is running. Starting Hydrogen from console I could see lots of
>         ALSA Midi errors prior to the segfault. Went to Hydrogen's
>         Preferences dialog, MIDI System tab and changed the "Input"
>         combobox to "QJackCtl". Also, I found that I had QJackCtl
>         configured with the "MIDI driver" combobox set to "seq". After
>         changing this to "none", Hydrogen was able to start correctly
>         under JACK. But I am still unaware of what exactly did these
>         changes mean and the consequences of them on running Hydrogen
>         with other softwares...
> 
>         Also, I have to tell that after these changes I was also able to
>         normally record audio in Ardour while Hydrogen was playing
>         along. I could also record the Hydrogen output as a track.
>         Cheers. A small step for an amateur musician, an even smaller
>         step for the music humanity! :)
> 
>         I tried to downgrade ALSA to 1.0.17 and test Audacity while JACK
>         was running. The problem persists whatever I do: while loading
>         Audacity, I get lots of xruns until JACK and QJackCtl are
>         automatically killed (sometimes Audacity dies as well). Starting
>         Audacity from console, I got these messages:
> 
>         Expression 'err != ETIMEDOUT' failed in
>         'src/hostapi/jack/pa_jack.c', line: 1009
>         Expression 'result' failed in 'src/hostapi/jack/pa_jack.c',
>         line: 1029
>         Expression 'AddStream( stream )' failed in
>         'src/hostapi/jack/pa_jack.c', line: 1305
>         Expression 'err != ETIMEDOUT' failed in
>         'src/hostapi/jack/pa_jack.c', line: 1009
>         Expression 'result' failed in 'src/hostapi/jack/pa_jack.c',
>         line: 1029
>         Expression 'AddStream( stream )' failed in
>         'src/hostapi/jack/pa_jack.c', line: 1305
> 
>         It seems that there is a bug in Audacity, isn't it?
> 
> 
>         Thanks to everyone!
> 
>         Fabricio Rocha
>         Brasilia, Brasil
> 
> 
>     Not to be a jerk, but why audacity? Why not use ardour?
> 
>