Audacity Forum

I am using Audacity 2.0.5 on OpenSuSE 13.1 on a Lenovo laptop X200s

The build comes from packman

Starting recently audacity has becone useless. When I start it I get many messages such as
(process:21806): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised
repeated 4 times followed by

ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1733
Expression 'AlsaOpen( &alsaApi->baseHostApiRep, params, streamDir, &self->pcm )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1900
Expression 'PaAlsaStreamComponent_Initialize( &self->capture, alsaApi, inParams,
StreamDirection_In, NULL != callback )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2167
Expression 'PaAlsaStream_Initialize( stream, alsaHostApi, inputParameters, output
Parameters, sampleRate, framesPerBuffer, callback, streamFlags, userData )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2836

and then 101 lines all saying
ALSA lib pcm_dsnoop.c:618:(snd_pcm_dsnoop_open) unable to open slave
and then other stuff like
(Audacity:21806): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed
repeated many times

I could live with that although irritating but when I play a wave file I get about 5 seconds of sound followed by hundreds of
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred

and then it freezes. Needs ^c to get control back.

On my desk machine I get similar messages but not the underruns.

Wht can I do?

jpff wrote:I am using Audacity 2.0.5 on OpenSuSE 13.1 on a Lenovo laptop X200s

The build comes from packman

Starting recently audacity has becone useless. When I start it I get many messages

GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised

This seems a common warning but is widely regarded as harmless.

jpff wrote:ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
Expression 'AlsaOpen( &alsaApi->baseHostApiRep, params, streamDir, &self->pcm )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1900
Expression 'PaAlsaStreamComponent_Initialize( &self->capture, alsaApi, inParams,
StreamDirection_In, NULL != callback )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2167
Expression 'PaAlsaStream_Initialize( stream, alsaHostApi, inputParameters, output
Parameters, sampleRate, framesPerBuffer, callback, streamFlags, userData )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2836

Those are regarded as "normal".

jpff wrote:and then 101 lines all saying
ALSA lib pcm_dsnoop.c:618:(snd_pcm_dsnoop_open) unable to open slave

These are usually fixed by using a later version of ALSA. These messages were prominent on earlier versions of Ubuntu.

jpff wrote:and then other stuff like
(Audacity:21806): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed
repeated many times

This seems to be a problem specific to OpenSUSE/Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=924683 . I suggest you complain directly to OpenSUSE.

jpff wrote:I could live with that although irritating but when I play a wave file I get about 5 seconds of sound followed by hundreds of
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred

and then it freezes. Needs ^c to get control back.

On my desk machine I get similar messages but not the underruns.

Have you tried adjusting "Audio to buffer" in Audacity 's Recording Preferences?

Are you choosing pulse in Device Toolbar ? You can make Audacity bypass PulseAudio and use ALSA directly. To do this, select the appropriate "hw" devices in Device Toolbar.

Using ALSA directly does create some limitations. Because you are now trying to access the device directly through ALSA, if any other program is accessing the device then it will not be available for Audacity. Also this denies exclusive access of a device to PulseAudio, so other programs using PulseAudio will not be able to use that device. Also it may be more difficult to record computer playback.

Obviously if you don't want to see all the messages, you could just double click on Audacity from its folder to execute it, or install it and access it that way.


Gale

[Have you tried adjusting "Audio to buffer" in Audacity 's Recording Preferences?

No; and what has recording got to do with it? I never use audaciy to record. Anyway it says 1000

Are you choosing pulse in Device Toolbar ? You can make Audacity bypass PulseAudio and use ALSA directly. To do this, select the appropriate "hw" devices in Device Toolbar.

No pulse, just ALSA. If I take default it fails; just tried hw(0,0) and it seems better

Using ALSA directly does create some limitations. Because you are now trying to access the device directly through ALSA, if any other program is accessing the device then it will not be available for Audacity. Also this denies exclusive access of a device to PulseAudio, so other programs using PulseAudio will not be able to use that device. Also it may be more difficult to record computer playback.

No other programs accessing sound -- I am the only user and this is how Ihave worked for years

Obviously if you don't want to see all the messages, you could just double click on Audacity from its folder to execute it, or install it and access it that way.

Double click? What is that? I run udacity from the command line like all other programs exceot emacs. I suppose I should have added, no Gnome, no KDE, no desktop, no dashtops or icons. I run fvwm on X11 -- I know this is old-fashioned but it has been this way for decades.

Still seems poor software to produce so many meaningless "normal" messages

jpff wrote:

[Have you tried adjusting "Audio to buffer" in Audacity 's Recording Preferences?

No; and what has recording got to do with it? I never use audaciy to record.

Because it controls playback buffer as well as recording. Set it to 10 ms and see if you can play.

jpff wrote: Anyway it says 1000

The default is 100. Try 200 or experiment. It may help.

jpff wrote:

Obviously if you don't want to see all the messages, you could just double click on Audacity from its folder to execute it, or install it and access it that way.

Double click? What is that? I run udacity from the command line like all other programs exceot emacs. I suppose I should have added, no Gnome, no KDE, no desktop, no dashtops or icons. I run fvwm on X11 -- I know this is old-fashioned but it has been this way for decades.

Yes you should have added. OpenSUSE 11.0 or higher uses pulseaudio for GNOME installations, so we had to assume you used pulse.

jpff wrote:Still seems poor software to produce so many meaningless "normal" messages

As stated, if you update ALSAlib the dsnoop messages should go away. It's an ALSA bug.

"assertion 'GTK_IS_WIDGET" is an OpenSUSE issue with GTK apps. Please report it to OpenSUSE.


Gale