New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

could not initialize audio. RESULT = 0 when starting server in supercollider #312

Open
ionakathryn opened this Issue Dec 3, 2017 · 3 comments

Comments

Projects
None yet
4 participants
@ionakathryn

ionakathryn commented Dec 3, 2017

Hi I'm trying to play some audio with supercollider and when running:
Server.local.boot;
getting the error message below:

JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
could not initialize audio.
RESULT = 0

The image shows my jackd settings.
screenshot from 2017-12-03 16-28-43

Hopefully someone can help, thanks

@dvzrv

This comment has been minimized.

Contributor

dvzrv commented Dec 17, 2017

Is this using jack2 or jack1?

I usually start jack2 beforehand and then connect to it with SuperCollider.
However it should work from any jack client requesting the start of the audio server.
So this is not really a SuperCollider specific problem.

Are you able to start JACK with qjackctl, which you have opened in the picture, that you attached?

@FedericoCapaldo

This comment has been minimized.

FedericoCapaldo commented Jan 9, 2018

A possible solution

TL;DR

Stop your sound system daemon (e.g. pulseaudio) so that jackd can use the playback device when starting the supercollider server.
Command to kill pulseaudio on Command Line pulseaudio -k. Then try to start supercollider server.

Longer version

I had exactely the same erros when trying to start the server on supercollider with s.boot.

when trying to start supercollider server, it uses the JACK Audio Connection Kit sound server (i.e. jackd or jack1 etc..) to output audio.

I tried to see start jackd manually from the CLI with the command jackd -r -d alsa and it gave me the following error.

Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

could not open driver .so '/usr/lib/jack/jack_net.so': libcelt0.so.2: cannot open shared object file: No such file or directory

could not open driver .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory

JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit


ATTENTION: The playback device "hw:0" is already in use. Please stop the application using it and run JACK again
cannot load driver module alsa

Note at the end that hw:0 is ALREADY IN USE.

My solution and idea was that the playback device is already being used by your sound system. In my linux version is pulseaudio. By killing its daemon with pulseaudio -k, then I was able to start the the supercollider server.

@ZeCraum

This comment has been minimized.

ZeCraum commented May 21, 2018

I had the same problem, but I solved it installing and initializing jack audiolike this:

jackd1 -r -d alsa -r 44100
jackd2 -r -d alsa -r 44100

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment