audacity sometimes won't start when devices change

[steve]

Should I?

If you do, then you can tell me if you get the same Segmentation fault error that I'm currently getting when recording a second track with Overdub enabled using ALSA for playback.

Audacity is working sweetly with Jack, but I'm having major problems with PulseAudio and ALSA.

[bgravato]

steve, which wxwidgets version do you recommend? Should the 2.8.10.1 be fine?

[steve]

I'm using 2.8.11.0 from the Ubuntu repository.
I think 2.8.10 should also be fine.

[bgravato]

I just compiled the svn version (with wxwidgets 2.8.10.1 from debian's rep.).

I see no different behaviour from 1.3.12-beta in debian's rep.

Regarding my problem it still fails to start when it can't find the playing/recording devices.
BTW, can you help me testing this one too? Please edit your ~/.audacity-data/audacity.cfg file and look for these lines:

Code: Select all

[AudioIO]
PlaybackDevice=JACK Audio Connection Kit: system
RecordingDevice=JACK Audio Connection Kit: system

Change it to:

Code: Select all

[AudioIO]
PlaybackDevice=
RecordingDevice=

Start audacity... Does it start? Or does it crash?

Regarding your problem, it crashes when I select ALSA: default for playback, but that also happens with 1.3.12-beta (with jackd running in both cases and with jackplug configured in asoundrc to handle default pcm playback, if that matters...).

[bgravato]

I was just thinking about my last post... and it might contain the answer to my problem...
While testing ALSA on your request I found that audacity crashes when selecting ALSA: default, so what probably is happening is that when it fails to open the device in the config file it will probably default to "ALSA: default" and that causes it to crash...

Edit: just to add that the reason why it crashes on "ALSA: default" is probably due to my .asoundrc config which redirects alsa's pcm to jack through jackplug... At least this is my most recent guess about it...