Suddenly - Jack problems (on upgrade)

Unofficial support for the KXStudio Linux distribution and applications.
More info at http://kxstudio.linuxaudio.org/

Moderators: MattKingUSA, khz

Post Reply
mdickson
Established Member
Posts: 20
Joined: Wed Dec 05, 2012 6:00 pm

Suddenly - Jack problems (on upgrade)

Post by mdickson »

I have been running KXStudio for a while and liking it a lot.

I have a Scarlett 2i4, which worked just fine out of the box. I normally used it at 48K, buffer size 128, 2 periods/buffer. I know that I was able to use it at least down to a buffer size of 32.

After recently doing all of

Code: Select all

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
and rebooting, suddently two things have happened:

1. Starting Jack (from Cadence) fails if the buffer size is below 256.
2. I can start Jack once upon boot-up (assuming buffer >=256), but after it shuts down once, it refuses to restart.

The logs look like this after a complete reboot, then start Jack at buffer=256. (I start Jack from within Cadence, and I do not have it set to start automatically at bootup, though I used to until this problem started.)
Mon May 12 12:54:42 2014: ------------------
Mon May 12 12:54:42 2014: Controller activated. Version 1.9.10 (0+) built on Thu May 8 13:41:09 2014
Mon May 12 12:54:42 2014: Loading settings from "/home/michael/.config/jack/conf.xml" using expat_2.0.1 ...
Mon May 12 12:54:42 2014: setting parameter 'engine':'driver':'(null)' to value "alsa"
Mon May 12 12:54:42 2014: setting parameter 'engine':'realtime':'(null)' to value "true"
Mon May 12 12:54:42 2014: setting parameter 'engine':'realtime-priority':'(null)' to value "95"
Mon May 12 12:54:42 2014: setting parameter 'drivers':'dummy':'rate' to value "44100"
Mon May 12 12:54:42 2014: setting parameter 'drivers':'dummy':'period' to value "256"
Mon May 12 12:54:42 2014: setting parameter 'drivers':'alsa':'device' to value "hw:USB,0"
Mon May 12 12:54:42 2014: setting parameter 'drivers':'alsa':'rate' to value "48000"
Mon May 12 12:54:42 2014: setting parameter 'drivers':'alsa':'period' to value "256"
Mon May 12 12:54:42 2014: setting parameter 'drivers':'alsa':'nperiods' to value "2"
Mon May 12 12:54:42 2014: setting parameter 'drivers':'alsa':'midi-driver' to value "raw"
Mon May 12 12:54:42 2014: setting parameter 'drivers':'alsa':'hw-alias' to value "true"
Mon May 12 12:54:42 2014: Listening for D-Bus messages
Mon May 12 12:55:28 2014: Starting jack server...
Mon May 12 12:55:28 2014: JACK server starting in realtime mode with priority 95
Mon May 12 12:55:28 2014: self-connect-mode is "Don't restrict self connect requests"
Mon May 12 12:55:28 2014: Acquired audio card Audio2
Mon May 12 12:55:28 2014: creating alsa driver ... hw:USB,0|hw:USB,0|256|2|48000|0|0|nomon|swmeter|-|32bit
Mon May 12 12:55:28 2014: Using ALSA driver USB-Audio running on card 2 - Focusrite Scarlett 2i4 USB at usb-0000:00:13.2-5, high speed
Mon May 12 12:55:28 2014: configuring for 48000Hz, period = 256 frames (5.3 ms), buffer = 2 periods
Mon May 12 12:55:28 2014: ALSA: final selected sample format for capture: 32bit integer little-endian
Mon May 12 12:55:28 2014: ALSA: use 2 periods for capture
Mon May 12 12:55:28 2014: ALSA: final selected sample format for playback: 32bit integer little-endian
Mon May 12 12:55:28 2014: ALSA: use 2 periods for playback
Mon May 12 12:55:30 2014: scan: added port hw:2,0,0 in-hw-2-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 12:55:30 2014: scan: added port hw:2,0,0 out-hw-2-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 12:55:30 2014: graph reorder: new port 'system:capture_1'
Mon May 12 12:55:30 2014: port 'system:midi_capture_1' created
Mon May 12 12:55:30 2014: New client 'system' with PID 0
Mon May 12 12:55:30 2014: New client 'system' with PID 0
Mon May 12 12:55:30 2014: graph reorder: new port 'system:capture_2'
Mon May 12 12:55:30 2014: scan: opened port hw:2,0,0 in-hw-2-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 12:55:30 2014: graph reorder: new port 'system:playback_1'
Mon May 12 12:55:30 2014: port 'system:midi_playback_1' created
Mon May 12 12:55:30 2014: graph reorder: new port 'system:playback_2'
Mon May 12 12:55:30 2014: scan: opened port hw:2,0,0 out-hw-2-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 12:55:30 2014: graph reorder: new port 'system:playback_3'
Mon May 12 12:55:30 2014: graph reorder: new port 'system:playback_4'
So everything appears to be fine, and Cadence tells me that Jack is running. Then I stop it and attempt to restart, and it fails. The logs below show the stop and failed restart.
Mon May 12 12:57:45 2014: Stopping jack server...
Mon May 12 12:57:45 2014: Client 'system' with PID 0 is out
Mon May 12 12:57:45 2014: Client 'system' with PID 0 is out
Mon May 12 12:57:45 2014: scan: deleted port hw:2,0,0 in-hw-2-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 12:57:46 2014: scan: deleted port hw:2,0,0 out-hw-2-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 12:57:46 2014: Released audio card Audio2
Mon May 12 12:58:08 2014: Starting jack server...
Mon May 12 12:58:08 2014: JACK server starting in realtime mode with priority 95
Mon May 12 12:58:08 2014: self-connect-mode is "Don't restrict self connect requests"
Mon May 12 12:58:08 2014: Acquired audio card Audio2
Mon May 12 12:58:08 2014: creating alsa driver ... hw:USB,0|hw:USB,0|256|2|48000|0|0|nomon|swmeter|-|32bit
Mon May 12 12:58:08 2014: Using ALSA driver USB-Audio running on card 2 - Focusrite Scarlett 2i4 USB at usb-0000:00:13.2-5, high speed
Mon May 12 12:58:08 2014: configuring for 48000Hz, period = 256 frames (5.3 ms), buffer = 2 periods
Mon May 12 12:58:08 2014: ALSA: final selected sample format for capture: 32bit integer little-endian
Mon May 12 12:58:08 2014: ALSA: use 2 periods for capture
Mon May 12 12:58:08 2014: ALSA: final selected sample format for playback: 32bit integer little-endian
Mon May 12 12:58:08 2014: ALSA: use 2 periods for playback
Mon May 12 12:58:09 2014: scan: added port hw:2,0,0 in-hw-2-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 12:58:09 2014: scan: added port hw:2,0,0 out-hw-2-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 12:58:09 2014: scan: opened port hw:2,0,0 in-hw-2-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 12:58:10 2014: ERROR: JackPosixProcessSync::LockedTimedWait error usec = 106660 err = Connection timed out
Mon May 12 12:58:10 2014: ERROR: JackEngine::ClientActivate wait error ref = 2 name = dbusapi
Mon May 12 12:58:10 2014: ERROR: failed to activate dbusapi jack client. error is -1
Mon May 12 12:58:10 2014: ERROR: JackPosixProcessSync::LockedTimedWait error usec = 106660 err = Connection timed out
Mon May 12 12:58:10 2014: ERROR: JackEngine::ClientDeactivate wait error ref = 2 name = dbusapi
Mon May 12 12:58:10 2014: ERROR: JackPosixProcessSync::LockedTimedWait error usec = 21332 err = Connection timed out
Mon May 12 12:58:10 2014: ERROR: JackEngine::ClientCloseAux wait error ref = 2
Mon May 12 12:58:10 2014: scan: opened port hw:2,0,0 out-hw-2-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 12:58:10 2014: scan: deleted port hw:2,0,0 in-hw-2-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 12:58:10 2014: scan: deleted port hw:2,0,0 out-hw-2-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 12:58:10 2014: Released audio card Audio2
Then reboot the machine, set the buffer to 128, and attempt to start. Jack fails. However, something continues to ping the audio interface -- I can tell because the lights on the front continue to blink (they always blink a few times on startup but in this situation they blink repeatedly). The only way (that I know of) to stop the blinking lights is to pull the (USB) plug on the interface (which I did and you can see that in the logs).
Mon May 12 13:03:22 2014: ------------------
Mon May 12 13:03:22 2014: Controller activated. Version 1.9.10 (0+) built on Thu May 8 13:41:09 2014
Mon May 12 13:03:22 2014: Loading settings from "/home/michael/.config/jack/conf.xml" using expat_2.0.1 ...
Mon May 12 13:03:22 2014: setting parameter 'engine':'driver':'(null)' to value "alsa"
Mon May 12 13:03:22 2014: setting parameter 'engine':'realtime':'(null)' to value "true"
Mon May 12 13:03:22 2014: setting parameter 'engine':'realtime-priority':'(null)' to value "95"
Mon May 12 13:03:22 2014: setting parameter 'drivers':'dummy':'rate' to value "44100"
Mon May 12 13:03:22 2014: setting parameter 'drivers':'dummy':'period' to value "256"
Mon May 12 13:03:22 2014: setting parameter 'drivers':'alsa':'device' to value "hw:USB,0"
Mon May 12 13:03:22 2014: setting parameter 'drivers':'alsa':'rate' to value "48000"
Mon May 12 13:03:22 2014: setting parameter 'drivers':'alsa':'period' to value "256"
Mon May 12 13:03:22 2014: setting parameter 'drivers':'alsa':'nperiods' to value "2"
Mon May 12 13:03:22 2014: setting parameter 'drivers':'alsa':'midi-driver' to value "raw"
Mon May 12 13:03:22 2014: setting parameter 'drivers':'alsa':'hw-alias' to value "true"
Mon May 12 13:03:22 2014: Listening for D-Bus messages
Mon May 12 13:03:28 2014: Saving settings to "/home/michael/.config/jack/conf.xml" ...
Mon May 12 13:03:33 2014: Saving settings to "/home/michael/.config/jack/conf.xml" ...
Mon May 12 13:03:34 2014: Starting jack server...
Mon May 12 13:03:34 2014: JACK server starting in realtime mode with priority 95
Mon May 12 13:03:34 2014: self-connect-mode is "Don't restrict self connect requests"
Mon May 12 13:03:34 2014: Acquired audio card Audio3
Mon May 12 13:03:34 2014: creating alsa driver ... hw:USB,0|hw:USB,0|128|2|48000|0|0|nomon|swmeter|-|32bit
Mon May 12 13:03:34 2014: Using ALSA driver USB-Audio running on card 3 - Focusrite Scarlett 2i4 USB at usb-0000:00:13.2-5, high speed
Mon May 12 13:03:34 2014: configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 2 periods
Mon May 12 13:03:34 2014: ALSA: final selected sample format for capture: 32bit integer little-endian
Mon May 12 13:03:34 2014: ALSA: use 2 periods for capture
Mon May 12 13:03:34 2014: ALSA: final selected sample format for playback: 32bit integer little-endian
Mon May 12 13:03:34 2014: ALSA: use 2 periods for playback
Mon May 12 13:03:36 2014: scan: added port hw:3,0,0 in-hw-3-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 13:03:36 2014: scan: added port hw:3,0,0 out-hw-3-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 13:03:41 2014: ERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
Mon May 12 13:03:41 2014: ERROR: Driver is not running
Mon May 12 13:03:41 2014: ERROR: Cannot open client name = dbusapi
Mon May 12 13:03:41 2014: ERROR: failed to create dbusapi jack client
Mon May 12 13:03:41 2014: scan: opened port hw:3,0,0 in-hw-3-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 13:03:41 2014: scan: opened port hw:3,0,0 out-hw-3-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 13:04:47 2014: ERROR: ALSA: prepare error for playback on "hw:USB,0" (Protocol error)
Mon May 12 13:04:47 2014: ERROR: JackAudioDriver::ProcessAsync: read error, stopping...
Mon May 12 13:04:47 2014: scan: deleted port hw:3,0,0 in-hw-3-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 13:04:47 2014: scan: deleted port hw:3,0,0 out-hw-3-0-0-Scarlett-2i4-USB-MIDI-1
Mon May 12 13:04:47 2014: ERROR: control open "hw:USB" (No such device)
Mon May 12 13:04:47 2014: ERROR: control open "hw:USB" (No such device)
Any insight that anybody can provide would be greatly appreciated.
--
Michael
Top
bazsound
Established Member
Posts: 480
Joined: Sat Aug 03, 2013 11:46 am

Re: Suddenly - Jack problems (on upgrade)

Post by bazsound »

I seen a recent update come through for jackd and jackdfirewire. Maybe they have introduced a bug into jack. maybe you could try rolling back jack firewire to a previous version
Top
Post Reply

Return to “KXStudio Discussion”