Audio qjackctl does not start

Questions about applications and software
Forum rules
Before you post please read how to get help
deepakdeshp
Level 17
Level 17
Posts: 7488
Joined: Sun Aug 09, 2015 10:00 am

Re: Audio qjackctl does not start

Post by deepakdeshp »

MrEen wrote:
Fri Nov 22, 2019 3:21 pm
Well I went ahead and installed and ran it. On my 18.3 Xfce system, I got the 2.9 version of sonic-pi.

Thank you for trying it and you are lucky. I will try your suggestions. I am getting SP version 2.1 for Cinnamon 19.2.
How did you install SP? Which packages with apt install commands?
I wonder how do I get to install the 18.3 Mate packages to install just for SP. I will have to point to the 18.3 repositories temporarily after I purge SP from my machine.
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help, and keeps the forum clean.
Regards,
Deepak

I am using Mint 19.3 Cinnamon 64 bit with AMD A8/7410 processor . Memory 8GB

User avatar
MrEen
Level 19
Level 19
Posts: 9535
Joined: Mon Jun 12, 2017 8:39 pm

Re: Audio qjackctl does not start

Post by MrEen »

I used the Software Manager. I only selected sonic-pi, but added a ton of other files/packages. I'll find the list:

Code: Select all

Start-Date: 2019-11-21  23:45:27
Commandline: aptdaemon role='role-install-packages' sender=':1.238'
Install: ruby-ttfunk:amd64 (1.4.0-1, automatic), 
librtaudio4v5:amd64 (4.1.1~ds0-4, automatic), 
ruby-oj:amd64 (2.12.10-4build1, automatic), 
ruby-rugged:amd64 (0.24.0+ds1-2, automatic), 
ruby-kramdown:amd64 (1.10.0-1, automatic),
 ruby-i18n:amd64 (0.7.0-2, automatic), 
 ruby-thread-safe:amd64 (0.3.5-3, automatic), 
 ruby-afm:amd64 (0.2.2-1, automatic), 
 ruby-pdf-reader:amd64 (1.4.0-1, automatic), 
 ruby-wavefile:amd64 (0.6.0-2, automatic), 
 sonic-pi:amd64 (2.9.0~repack-6), 
 libstk-4.5.0:amd64 (4.5.0-3, automatic), 
 ruby-prawn-table:amd64 (0.2.1-1, automatic), 
 ruby-prawn:amd64 (2.0.2+dfsg-1, automatic), 
 librtmidi2v5:amd64 (2.1.0~ds0-4, automatic), 
 libscsynth1:amd64 (1:3.6.6~repack-2-2, automatic), 
 libqt5scintilla2-l10n:amd64 (2.9.1+dfsg-4build1, automatic), 
 ruby-pdf-core:amd64 (0.5.1-1, automatic), 
 libhttp-parser2.1:amd64 (2.1-2, automatic), 
 sonic-pi-samples:amd64 (2.9.0~repack-6, automatic), 
 ruby-rc4:amd64 (0.1.5-3, automatic), 
 ruby-coderay:amd64 (1.1.1-1, automatic), 
 ruby-multi-json:amd64 (1.11.2-3, automatic), 
 libqt5scintilla2-12v5:amd64 (2.9.1+dfsg-4build1, automatic), 
 ruby-hashery:amd64 (2.1.1-2, automatic), 
 ruby-rouge:amd64 (1.10.1-1, automatic), 
 ruby-concurrent:amd64 (1.0.0-1, automatic), 
 ruby-atomic:amd64 (1.1.16-2build5, automatic), 
 sc3-plugins-server:amd64 (3.7.0~beta+git20151221.f978dc2~repack-7, automatic), 
 sonic-pi-server:amd64 (2.9.0~repack-6, automatic), 
 ruby-stringex:amd64 (2.5.2-3, automatic), 
 ruby-hamster:amd64 (3.0.0-1, automatic), 
 ruby-tzinfo:amd64 (1.2.2-1, automatic), 
 libgit2-24:amd64 (0.24.1-2ubuntu0.2, automatic), 
 supercollider-server:amd64 (1:3.6.6~repack-2-2, automatic), 
 ruby-activesupport:amd64 (2:4.2.6-1, automatic), 
 ruby-ascii85:amd64 (1.0.2-3, automatic)
End-Date: 2019-11-21  23:45:56
That's from running cat /var/log/apt/history.log and I tried to split each name onto its own line.

deepakdeshp
Level 17
Level 17
Posts: 7488
Joined: Sun Aug 09, 2015 10:00 am

Re: Audio qjackctl does not start

Post by deepakdeshp »

MrEen wrote:
Fri Nov 22, 2019 9:28 pm
I used the Software Manager. I only selected sonic-pi, but added a ton of other files/packages. I'll find the list:

Code: Select all

Start-Date: 2019-11-21  23:45:27
Commandline: aptdaemon role='role-install-packages' sender=':1.238'
Install: ruby-ttfunk:amd64 (1.4.0-1, automatic), 
librtaudio4v5:amd64 (4.1.1~ds0-4, automatic), 
ruby-oj:amd64 (2.12.10-4build1, automatic), 
ruby-rugged:amd64 (0.24.0+ds1-2, automatic), 
ruby-kramdown:amd64 (1.10.0-1, automatic),
 ruby-i18n:amd64 (0.7.0-2, automatic), 
 ruby-thread-safe:amd64 (0.3.5-3, automatic), 
 ruby-afm:amd64 (0.2.2-1, automatic), 
 ruby-pdf-reader:amd64 (1.4.0-1, automatic), 
 ruby-wavefile:amd64 (0.6.0-2, automatic), 
 sonic-pi:amd64 (2.9.0~repack-6), 
 libstk-4.5.0:amd64 (4.5.0-3, automatic), 
 ruby-prawn-table:amd64 (0.2.1-1, automatic), 
 ruby-prawn:amd64 (2.0.2+dfsg-1, automatic), 
 librtmidi2v5:amd64 (2.1.0~ds0-4, automatic), 
 libscsynth1:amd64 (1:3.6.6~repack-2-2, automatic), 
 libqt5scintilla2-l10n:amd64 (2.9.1+dfsg-4build1, automatic), 
 ruby-pdf-core:amd64 (0.5.1-1, automatic), 
 libhttp-parser2.1:amd64 (2.1-2, automatic), 
 sonic-pi-samples:amd64 (2.9.0~repack-6, automatic), 
 ruby-rc4:amd64 (0.1.5-3, automatic), 
 ruby-coderay:amd64 (1.1.1-1, automatic), 
 ruby-multi-json:amd64 (1.11.2-3, automatic), 
 libqt5scintilla2-12v5:amd64 (2.9.1+dfsg-4build1, automatic), 
 ruby-hashery:amd64 (2.1.1-2, automatic), 
 ruby-rouge:amd64 (1.10.1-1, automatic), 
 ruby-concurrent:amd64 (1.0.0-1, automatic), 
 ruby-atomic:amd64 (1.1.16-2build5, automatic), 
 sc3-plugins-server:amd64 (3.7.0~beta+git20151221.f978dc2~repack-7, automatic), 
 sonic-pi-server:amd64 (2.9.0~repack-6, automatic), 
 ruby-stringex:amd64 (2.5.2-3, automatic), 
 ruby-hamster:amd64 (3.0.0-1, automatic), 
 ruby-tzinfo:amd64 (1.2.2-1, automatic), 
 libgit2-24:amd64 (0.24.1-2ubuntu0.2, automatic), 
 supercollider-server:amd64 (1:3.6.6~repack-2-2, automatic), 
 ruby-activesupport:amd64 (2:4.2.6-1, automatic), 
 ruby-ascii85:amd64 (1.0.2-3, automatic)
End-Date: 2019-11-21  23:45:56
That's from running cat /var/log/apt/history.log and I tried to split each name onto its own line.
Did you add all these packages manually? I guess they got added when you installed sonic-pi.
Please see the help section. There are tutorials and examples.you will find them interesting. There are other materials on the web for Pi too.
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help, and keeps the forum clean.
Regards,
Deepak

I am using Mint 19.3 Cinnamon 64 bit with AMD A8/7410 processor . Memory 8GB

User avatar
MrEen
Level 19
Level 19
Posts: 9535
Joined: Mon Jun 12, 2017 8:39 pm

Re: Audio qjackctl does not start

Post by MrEen »

When I clicked Install, I got the popup telling me additional files would be installed. That's how all that happened.

I'll play with it some this weekend. Thanks for bringing the subject up. :D

One note, you could click on Messages in QJackCtl to see if there's any issue there, but I'm betting not. And you do need to wait several seconds after clicking on Start, ubtil it's fully started. Watch the titlebar to see it change to Started at the end.

deepakdeshp
Level 17
Level 17
Posts: 7488
Joined: Sun Aug 09, 2015 10:00 am

Re: Audio qjackctl does not start

Post by deepakdeshp »

MrEen wrote:
Fri Nov 22, 2019 10:40 pm


One note, you could click on Messages in QJackCtl to see if there's any issue there, but I'm betting not. And you do need to wait several seconds after clicking on Start, ubtil it's fully started. Watch the titlebar to see it change to Started at the end.
Yes I waited till qjackctl showed as running.qjackctl messages show some errors. I have no idea what they mean or how to resolve them.

Code: Select all

18:14:50.509 JACK was stopped
18:14:51.803 JACK is starting...
18:14:51.806 /usr/bin/jackd -dalsa -dhw:0 -r44100 -p1024 -n2 -D -Chw:Generic
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
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
no message buffer overruns
no message buffer overruns
no message buffer overruns
jackdmp 1.9.12
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2017 Filipe Coelho.
jackdmp 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
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
18:14:51.935 JACK was started with PID=9688.
audio_reservation_init
Acquire audio card Audio1
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:Generic|1024|2|44100|0|0|nomon|swmeter|-|32bit
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for captur
The best bet is to install the 18.3 sonic-pi version to my Mint 19.2. Again you run Mate and me Cinnamon.
I purged the package and reinstalled it with the same result, failure.I have opened a new thread for this. viewtopic.php?f=47&t=305947&p=1718640#p1718640
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help, and keeps the forum clean.
Regards,
Deepak

I am using Mint 19.3 Cinnamon 64 bit with AMD A8/7410 processor . Memory 8GB

User avatar
MrEen
Level 19
Level 19
Posts: 9535
Joined: Mon Jun 12, 2017 8:39 pm

Re: Audio qjackctl does not start

Post by MrEen »

As I said in the other thread, I'm thinking the issue lies more with JACK.

When I open QJackCtl, and immediately look at Messages, it shows this:

Code: Select all

11:39:42.464 Statistics reset.
11:39:42.475 ALSA connection change.
11:39:42.479 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
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
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
11:39:42.580 ALSA connection graph change.
That D-BUS might be the important line.

Then clicking on Start, messages added are below:

Code: Select all

11:42:04.608 D-BUS: JACK server is starting...
Sat Nov 23 11:42:04 2019: Starting jack server...
Sat Nov 23 11:42:04 2019: JACK server starting in realtime mode with priority 10
Sat Nov 23 11:42:04 2019: self-connect-mode is "Don't restrict self connect requests"
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
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
11:42:04.675 D-BUS: JACK server was started (org.jackaudio.service aka jackdbus).
Sat Nov 23 11:42:04 2019: Acquired audio card Audio2
Sat Nov 23 11:42:04 2019: creating alsa driver ... hw:Generic|hw:Generic|1024|2|44100|0|0|nomon|swmeter|-|32bit
Sat Nov 23 11:42:04 2019: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
Sat Nov 23 11:42:04 2019: ALSA: final selected sample format for capture: 32bit integer little-endian
Sat Nov 23 11:42:04 2019: ALSA: use 2 periods for capture
Sat Nov 23 11:42:04 2019: ALSA: final selected sample format for playback: 32bit integer little-endian
Sat Nov 23 11:42:04 2019: ALSA: use 2 periods for playback
Sat Nov 23 11:42:04 2019: graph reorder: new port 'system:capture_1'
Sat Nov 23 11:42:04 2019: New client 'system' with PID 0
Sat Nov 23 11:42:04 2019: graph reorder: new port 'system:capture_2'
Sat Nov 23 11:42:04 2019: graph reorder: new port 'system:playback_1'
Sat Nov 23 11:42:04 2019: graph reorder: new port 'system:playback_2'
Sat Nov 23 11:42:04 2019: New client 'PulseAudio JACK Sink' with PID 2122
Sat Nov 23 11:42:04 2019: Connecting 'PulseAudio JACK Sink:front-left' to 'system:playback_1'
Sat Nov 23 11:42:04 2019: Connecting 'PulseAudio JACK Sink:front-right' to 'system:playback_2'
Sat Nov 23 11:42:04 2019: New client 'PulseAudio JACK Source' with PID 2122
Sat Nov 23 11:42:04 2019: Connecting 'system:capture_1' to 'PulseAudio JACK Source:front-left'
Sat Nov 23 11:42:04 2019: Connecting 'system:capture_2' to 'PulseAudio JACK Source:front-right'
Sat Nov 23 11:42:06 2019: Saving settings to "/home/scott/.config/jack/conf.xml" ...
11:42:06.923 JACK connection change.
11:42:06.925 Server configuration saved to "/home/scott/.jackdrc".
11:42:06.925 Statistics reset.
11:42:06.956 Client activated.
11:42:06.957 Patchbay deactivated.
11:42:06.958 Post-startup script...
11:42:06.959 a2jmidid -e &
11:42:06.997 JACK connection graph change.
JACK MIDI <-> ALSA sequencer MIDI bridge, version 8 (7383d268c4bfe85df9f10df6351677659211d1ca) built on Wed Dec 31 19:00:00 1969
Copyright 2006,2007 Dmitry S. Baikov
Copyright 2007,2008,2009,2011,2012 Nedko Arnaudov
Bridge starting...
Using JACK server 'default'
Hardware ports will be exported.
11:42:07.187 ALSA connection graph change.
Bridge started
Press ctrl-c to stop the bridge
port created: Midi Through [14] (capture): Midi Through Port-0
port created: Midi Through [14] (playback): Midi Through Port-0
port created: Midi Through [14] (capture): Midi Through Port-1
port created: Midi Through [14] (playback): Midi Through Port-1
port created: Midi Through [14] (capture): Midi Through Port-2
port created: Midi Through [14] (playback): Midi Through Port-2
port created: Midi Through [14] (capture): Midi Through Port-3
port created: Midi Through [14] (playback): Midi Through Port-3
port created: AKM320 [28] (capture): AKM320 MIDI 1
port created: AKM320 [28] (playback): AKM320 MIDI 1
11:42:07.365 Post-startup script terminated successfully.
11:42:07.367 JACK connection change.
Sat Nov 23 11:42:06 2019: New client 'qjackctl' with PID 1162
Sat Nov 23 11:42:07 2019: New client 'a2j' with PID 1206
Some suggestions I would try if I were in this position:

1. Check for and fix any permissions issues with sudo chown -Rc $USER:$USER $HOME then test sonic-pi if you saw any mention of dbus in the output.

2. Look in Software Manager to see which editions of Jackd are installed. I have Jackd and Jackd2, but not Jackd1. If you have the first and third, uninstall Jackd1 and install Jackd2 then see if sonic-pi behaves.

3. Click on Connect in QJackCtl before starting sonic-pi. Mine looks like this:
Image

4. View the Connect screen after starting sonic-pi. Mine looks like this:
Image

I hope you find one of these useful.

deepakdeshp
Level 17
Level 17
Posts: 7488
Joined: Sun Aug 09, 2015 10:00 am

Re: Audio qjackctl does not start

Post by deepakdeshp »

Thank you. I will try the qjackd suggestions. I found a real good book. https://magpi.raspberrypi.org/books/ess ... onic-pi-v1 Please try and enjoy.
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help, and keeps the forum clean.
Regards,
Deepak

I am using Mint 19.3 Cinnamon 64 bit with AMD A8/7410 processor . Memory 8GB

deepakdeshp
Level 17
Level 17
Posts: 7488
Joined: Sun Aug 09, 2015 10:00 am

Re: Audio qjackctl does not start

Post by deepakdeshp »

MrEen wrote:
Sat Nov 23, 2019 1:14 pm
As I said in the other thread, I'm thinking the issue lies more with JACK.

When I open QJackCtl, and immediately look at Messages, it shows this:


1. Check for and fix any permissions issues with sudo chown -Rc $USER:$USER $HOME then test sonic-pi if you saw any mention of dbus in the output.

2. Look in Software Manager to see which editions of Jackd are installed. I have Jackd and Jackd2, but not Jackd1. If you have the first and third, uninstall Jackd1 and install Jackd2 then see if sonic-pi behaves.

3. Click on Connect in QJackCtl before starting sonic-pi. Mine looks like this:
Image

4. View the Connect screen after starting sonic-pi. Mine looks like this:
Image

I hope you find one of these useful.
Thank you once again.
I purged sonic-pi, installed Sonic Pi for Ubuntu 16.04 which you had pointed to in the other thread

1. I ran the chmod command
2. I also have Jackd and Jackd2
3. Clicked the connect in Qjackctl.
4. Started Supercollider server.
5. Started sonic-pi

The logs

Code: Select all

   Sonic Pi Boot Error Report
==================


System Information
----------------

* Sonic Pi version: 2.10.0
* OS: Linux Mint 19.2


GUI Log
-------

**/home/uma/.sonic-pi/log/gui.log**
```
[GUI] - using default editor colours
[GUI] - shutting down any old audio servers...
[GUI] - starting UDP OSC Server on port 4558...
[GUI] - UDP OSC Server ready and listening
[GUI] - booting live coding server
[GUI] - waiting for server to boot...
................................[GUI] - server failed to start with this error message: 
      > Server Exception:
 Boot - Unable to connect to SuperCollider
............................
[GUI] - Critical error! Could not boot server.

```


Server Errors
-------------

**/home/uma/.sonic-pi/log/server-errors.log**
```
Failed to start server: Boot - Unable to connect to SuperCollider
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/scsynthexternal.rb:292:in `boot_and_wait'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/scsynthexternal.rb:392:in `boot_server_linux'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/scsynthexternal.rb:181:in `boot'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/scsynthexternal.rb:29:in `initialize'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/server.rb:73:in `new'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/server.rb:73:in `initialize'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/studio.rb:102:in `new'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/studio.rb:102:in `init_studio'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/studio.rb:43:in `initialize'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/lang/sound.rb:123:in `new'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/lang/sound.rb:123:in `block (2 levels) in included'
/usr/lib/sonic-pi/server/bin/sonic-pi-server.rb:99:in `new'
/usr/lib/sonic-pi/server/bin/sonic-pi-server.rb:99:in `<main>'

```


Server Output
-------------

**/home/uma/.sonic-pi/log/server-output.log**
```
Sonic Pi server booting...
Using protocol: udp
Server is exiting.
Shutting down GUI...
Goodbye :-)

```


Scsynth Output
--------------

**/home/uma/.sonic-pi/log/scsynth.log**
```
# Starting SuperCollider 2019-11-24 00:58:25
Found 0 LADSPA plugins
JackDriver: client name is 'SuperCollider-01'
SC_AudioDriver: sample rate = 44100.000000, driver's block size = 1024
SuperCollider 3 server ready.

```
 
What looks important seems to be from the logs above
Failed to start server: Boot - Unable to connect to SuperCollider
Yet there is no joy. I think I will give up and be contented with the Windows version, for which I was able to find the 3.1 installer. It works.

I thank you once again.
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help, and keeps the forum clean.
Regards,
Deepak

I am using Mint 19.3 Cinnamon 64 bit with AMD A8/7410 processor . Memory 8GB

User avatar
MrEen
Level 19
Level 19
Posts: 9535
Joined: Mon Jun 12, 2017 8:39 pm

Re: Audio qjackctl does not start

Post by MrEen »

One last test if you still have it installed. Run apt install swh-plugins, then start QJackCtl, then run sonic-pi.

This line made me think of that:

Code: Select all

Found 0 LADSPA plugins

deepakdeshp
Level 17
Level 17
Posts: 7488
Joined: Sun Aug 09, 2015 10:00 am

Re: Audio qjackctl does not start

Post by deepakdeshp »

MrEen wrote:
Sat Nov 23, 2019 4:01 pm
One last test if you still have it installed. Run apt install swh-plugins, then start QJackCtl, then run sonic-pi.

This line made me think of that:

Code: Select all

Found 0 LADSPA plugins
I have it installed, even if I didnt it is easy to re-install. I did it but no success.
I installes swh-plugins
started djackctl
started supercollider server
started sonic pi.
Server boot errors

Code: Select all

Sonic Pi Boot Error Report
==================


System Information
----------------

* Sonic Pi version: 2.10.0
* OS: Linux Mint 19.2


GUI Log
-------

**/home/uma/.sonic-pi/log/gui.log**
```
[GUI] - using default editor colours
[GUI] - shutting down any old audio servers...
[GUI] - starting UDP OSC Server on port 4558...
[GUI] - UDP OSC Server ready and listening
[GUI] - booting live coding server
[GUI] - waiting for server to boot...
...................................[GUI] - server failed to start with this error message: 
      > Server Exception:
 Boot - Unable to connect to SuperCollider
.........................
[GUI] - Critical error! Could not boot server.

```


Server Errors
-------------

**/home/uma/.sonic-pi/log/server-errors.log**
```
Failed to start server: Boot - Unable to connect to SuperCollider
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/scsynthexternal.rb:292:in `boot_and_wait'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/scsynthexternal.rb:392:in `boot_server_linux'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/scsynthexternal.rb:181:in `boot'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/scsynthexternal.rb:29:in `initialize'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/server.rb:73:in `new'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/server.rb:73:in `initialize'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/studio.rb:102:in `new'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/studio.rb:102:in `init_studio'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/studio.rb:43:in `initialize'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/lang/sound.rb:123:in `new'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/lang/sound.rb:123:in `block (2 levels) in included'
/usr/lib/sonic-pi/server/bin/sonic-pi-server.rb:99:in `new'
/usr/lib/sonic-pi/server/bin/sonic-pi-server.rb:99:in `<main>'

```


Server Output
-------------

**/home/uma/.sonic-pi/log/server-output.log**
```
Sonic Pi server booting...
Using protocol: udp
Server is exiting.
Shutting down GUI...
Goodbye :-)

```


Scsynth Output
--------------

**/home/uma/.sonic-pi/log/scsynth.log**
```
# Starting SuperCollider 2019-11-24 08:41:57
Found 109 LADSPA plugins
JackDriver: client name is 'SuperCollider-01'
SC_AudioDriver: sample rate = 44100.000000, driver's block size = 1024
SuperCollider 3 server ready.

```
   
qjackctl messages

Code: Select all

08:39:55.078 Statistics reset.
08:39:55.140 ALSA connection change.
08:39:55.169 JACK is starting...
08:39:55.170 /usr/bin/jackd -dalsa -dhw:0 -r44100 -p1024 -n2 -D -Chw:Generic
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
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
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
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
08:39:55.294 JACK was started with PID=5442.
no message buffer overruns
no message buffer overruns
no message buffer overruns
jackdmp 1.9.12
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2017 Filipe Coelho.
jackdmp 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
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio1
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:Generic|1024|2|44100|0|0|nomon|swmeter|-|32bit
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
08:39:57.478 JACK connection change.
08:39:57.479 Server configuration saved to "/home/uma/.jackdrc".
08:39:57.479 Statistics reset.
08:39:57.484 Client activated.
08:39:57.484 Patchbay deactivated.
08:39:57.602 JACK connection graph change.
08:40:29.878 JACK connection graph change.
08:40:30.058 JACK connection change.
08:41:57.842 JACK connection graph change.
08:41:58.178 JACK connection graph change.
08:41:58.266 JACK connection change.
08:42:08.096 XRUN callback (1).
JackEngine::XRun: client = SuperCollider-01 was not finished, state = Running
JackAudioDriver::ProcessGraphAsyncMaster: Process error
08:42:28.204 JACK connection graph change.
08:42:28.400 JACK connection change.
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help, and keeps the forum clean.
Regards,
Deepak

I am using Mint 19.3 Cinnamon 64 bit with AMD A8/7410 processor . Memory 8GB

User avatar
MrEen
Level 19
Level 19
Posts: 9535
Joined: Mon Jun 12, 2017 8:39 pm

Re: Audio qjackctl does not start

Post by MrEen »

Damn! I'm at a loss. I'm suspecting this:

Code: Select all

08:39:57.484 Client activated.
08:39:57.484 Patchbay deactivated.
Not sure what to do about it though.

At least this time they both said the same SuperCollider-01. And then there was this:

Code: Select all

JackEngine::XRun: client = SuperCollider-01 was not finished, state = Running
Again, not sure what to do about it.

I feel like we got closer, but I almost never use JACK anymore.

deepakdeshp
Level 17
Level 17
Posts: 7488
Joined: Sun Aug 09, 2015 10:00 am

Re: Audio qjackctl does not start

Post by deepakdeshp »

MrEen wrote:
Sat Nov 23, 2019 11:32 pm
Damn! I'm at a loss. I'm suspecting this:

Code: Select all

08:39:57.484 Client activated.
08:39:57.484 Patchbay deactivated.
Not sure what to do about it though.

At least this time they both said the same SuperCollider-01. And then there was this:

Code: Select all

JackEngine::XRun: client = SuperCollider-01 was not finished, state = Running
Again, not sure what to do about it.

I feel like we got closer, but I almost never use JACK anymore.
You did all that was possible, yet sonic-doesnt run on Mint. For Sonic I need to go to Windows which I hate.
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help, and keeps the forum clean.
Regards,
Deepak

I am using Mint 19.3 Cinnamon 64 bit with AMD A8/7410 processor . Memory 8GB

User avatar
MrEen
Level 19
Level 19
Posts: 9535
Joined: Mon Jun 12, 2017 8:39 pm

Re: Audio qjackctl does not start

Post by MrEen »

You probably know I hate giving in, so feel free to ignore me at any time, but I'm wondering if your Connect options in QJackCtl look like mine did in this post?

Also, you mentioned starting SuperCollider server. I never had to do that, or even an option that I knew of to do that. Just opening sonic-pi made the connection itself as long as QJackCtl was already running. If you do see SuperCollider in the Connect window, and it isn't "connected" to anything, click on it and drag to system on the opposite side then release the mouse.

User avatar
trytip
Level 13
Level 13
Posts: 4673
Joined: Tue Jul 05, 2016 1:20 pm

Re: Audio qjackctl does not start

Post by trytip »

read some comments to help with it. https://in-thread.sonic-pi.net/t/instal ... lts/1318/4
Image

deepakdeshp
Level 17
Level 17
Posts: 7488
Joined: Sun Aug 09, 2015 10:00 am

Re: Audio qjackctl does not start

Post by deepakdeshp »

MrEen wrote:
Sat Nov 23, 2019 11:50 pm
You probably know I hate giving in, so feel free to ignore me at any time, but I'm wondering if your Connect options in QJackCtl look like mine did in this post?

Also, you mentioned starting SuperCollider server. I never had to do that, or even an option that I knew of to do that. Just opening sonic-pi made the connection itself as long as QJackCtl was already running. If you do see SuperCollider in the Connect window, and it isn't "connected" to anything, click on it and drag to system on the opposite side then release the mouse.
I am not as tenacious as you. I will never ever ignore anybody who is helping me with all his heart and might, in this case you. But unfortunately I did apt purge for the sonic package before I viewed your post.

In my case it was a clean install of Mint 17, then upgrade to 18 and finally to 19.2. Probably thats what has made some difference and I am not able to install SP.
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help, and keeps the forum clean.
Regards,
Deepak

I am using Mint 19.3 Cinnamon 64 bit with AMD A8/7410 processor . Memory 8GB

User avatar
MrEen
Level 19
Level 19
Posts: 9535
Joined: Mon Jun 12, 2017 8:39 pm

Re: Audio qjackctl does not start

Post by MrEen »

deepakdeshp wrote:
Tue Nov 26, 2019 12:15 pm
In my case it was a clean install of Mint 17, then upgrade to 18 and finally to 19.2. Probably thats what has made some difference and I am not able to install SP.
Absolutely. I'm fairly confident that's the cause of the issue here. With smurphos having success in the VM, and me with my old version, I'm sure you've just got something hinky with the system.

The next time you do a clean install, hardware or VM, I'll bet you can get it working.

deepakdeshp
Level 17
Level 17
Posts: 7488
Joined: Sun Aug 09, 2015 10:00 am

Re: Audio qjackctl does not start

Post by deepakdeshp »

I reinstalled sonic-pi. Please feel free to ignore me.

WHen I start qjackctl, it goes in active mode but doesnt show started. I get the messages

Code: Select all

Sonic Pi Boot Error Report
==================


System Information
----------------

* Sonic Pi version: 2.10.0
* OS: Linux Mint 19.2


GUI Log
-------

**/home/uma/.sonic-pi/log/gui.log**
```
[GUI] - using default editor colours
[GUI] - shutting down any old audio servers...
[GUI] - starting UDP OSC Server on port 4558...
[GUI] - UDP OSC Server ready and listening
[GUI] - booting live coding server
[GUI] - waiting for server to boot...
................................[GUI] - server failed to start with this error message: 
      > Server Exception:
 Boot - Unable to connect to SuperCollider
............................
[GUI] - Critical error! Could not boot server.

```


Server Errors
-------------

**/home/uma/.sonic-pi/log/server-errors.log**
```
Failed to start server: Boot - Unable to connect to SuperCollider
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/scsynthexternal.rb:292:in `boot_and_wait'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/scsynthexternal.rb:392:in `boot_server_linux'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/scsynthexternal.rb:181:in `boot'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/scsynthexternal.rb:29:in `initialize'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/server.rb:73:in `new'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/server.rb:73:in `initialize'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/studio.rb:102:in `new'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/studio.rb:102:in `init_studio'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/studio.rb:43:in `initialize'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/lang/sound.rb:123:in `new'
/usr/lib/sonic-pi/server/sonicpi/lib/sonicpi/lang/sound.rb:123:in `block (2 levels) in included'
/usr/lib/sonic-pi/server/bin/sonic-pi-server.rb:99:in `new'
/usr/lib/sonic-pi/server/bin/sonic-pi-server.rb:99:in `<main>'

```


Server Output
-------------

**/home/uma/.sonic-pi/log/server-output.log**
```
Sonic Pi server booting...
Using protocol: udp
Server is exiting.
Shutting down GUI...
Goodbye :-)

```


Scsynth Output
--------------

**/home/uma/.sonic-pi/log/scsynth.log**
```
# Starting SuperCollider 2019-11-28 00:03:18
Found 109 LADSPA plugins
JackDriver: client name is 'SuperCollider'
SC_AudioDriver: sample rate = 44100.000000, driver's block size = 1024
SuperCollider 3 server ready.

```
The qjackctl messages are

Code: Select all

  00:02:57.414 Statistics reset.
00:02:57.432 ALSA connection change.
00:02:57.486 JACK connection change.
00:02:57.498 Client activated.
00:02:57.499 Patchbay deactivated.
00:03:18.528 JACK connection graph change.
00:03:18.855 JACK connection graph change.
00:03:19.001 JACK connection change.
00:03:48.883 JACK connection graph change.
00:03:48.940 JACK connection change. 
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help, and keeps the forum clean.
Regards,
Deepak

I am using Mint 19.3 Cinnamon 64 bit with AMD A8/7410 processor . Memory 8GB

deepakdeshp
Level 17
Level 17
Posts: 7488
Joined: Sun Aug 09, 2015 10:00 am

Re: Audio qjackctl does not start

Post by deepakdeshp »

There looks to be a problem with supercollider.
I started qjackctl.
I kept the jackaudio connection window open and started SP. the supercollider is momentarily visible in the connections window in readable clients window then it goes to writable clients window. It doesnt stay there but disappears.
connections.png
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help, and keeps the forum clean.
Regards,
Deepak

I am using Mint 19.3 Cinnamon 64 bit with AMD A8/7410 processor . Memory 8GB

User avatar
MrEen
Level 19
Level 19
Posts: 9535
Joined: Mon Jun 12, 2017 8:39 pm

Re: Audio qjackctl does not start

Post by MrEen »

Let's see the output of cat ~/.jackdrc

That Patchbay deactivated seems very suspicious as I don't get that line. I do not have Activate Patchbay persistance checked in Setup > Options tab > Connections. If you do, try un-checking that.

User avatar
MrEen
Level 19
Level 19
Posts: 9535
Joined: Mon Jun 12, 2017 8:39 pm

Re: Audio qjackctl does not start

Post by MrEen »

Let's see the output of groups as well. If you're not part of the audio group, adding yourself might help, although I think we'd be seeing different errors in that case relating to real-time privileges.

EDIT: One more output that might help; cat ~/.config/rncbc.org/QjackCtl.conf

Post Reply

Return to “Software & Applications”