i downloaded Ardour 6.5 ARM32 and ARM64 for to use with raspberry4 4GB rpiOS32,
where jack2 1.9.2 and zita-j2a/a2j 0.7.0 j2n/n2j 0.4.1 are started in advance
when creating a new session Ardour stops with following message:
Could not create session in “/home/pi/Untitled-2020-11-25-00-41-06” — Log Messages: INFO: Loading menus from /opt/Ardour-6.5.0/etc/ardour.menu —
please see that jack was started in realtime mode:
jack_control ep
— get engine parameters (type:isset:default:value)
driver: Driver to use (str:set:dummy:dummy)
name: Server name to use. (str:notset:default:default)
realtime: Whether to use realtime mode. (bool:notset:True:True)
realtime-priority: Scheduler priority when running in realtime mode. (sint:notset:10:10)
temporary: Exit once all clients have closed their connections. (bool:notset:False:False)
verbose: Verbose mode. (bool:notset:False:False)
client-timeout: Client timeout limit in milliseconds. (sint:notset:0:0)
clock-source: Clocksource type : c(ycle) | h(pet) | s(ystem). (uint:notset:0:0)
port-max: Maximum number of ports. (uint:set:2048:16)
replace-registry: Replace shared memory registry. (bool:notset:False:False)
sync: Use server synchronous mode. (bool:notset:False:False)
self-connect-mode: Self connect mode. (char:notset: : )
slave-drivers: Slave drivers to use (str:notset:
when restarting with jack_control eps realtime-priority 1 the error is still there.
You have to configure a rt priority > 5. JACK uses the given priority and the 5 below for process threads.
try:
jack_control eps realtime-priority 10
which is the default.
Also configuring jack to use realtime-priority does no mean that it has permissions to do so.
Check ~/.log/jack/jackdbus.log for jackdbus, or easier: jack -d alsa and see if that shows any errors. If so, on debian based distros you can use sudo dpkg-reconfigure -p high jackd2 to enable rt permissions for audio-group users, then re-login (or reboot).
after dpkg-reconfig the ALSA setup shows the same error like JACK.
Wed Nov 25 03:07:02 2020: Controller activated. Version 1.9.12 (unknown) built on Sun Feb 25 20:41:33 2018
Wed Nov 25 03:07:02 2020: Loading settings from “/home/pi/.config/jack/conf.xml” using expat_2.2.6 …
Wed Nov 25 03:07:02 2020: setting parameter ‘engine’:‘driver’:’(null)’ to value “dummy”
Wed Nov 25 03:07:02 2020: setting parameter ‘engine’:‘realtime’:’(null)’ to value “true”
Wed Nov 25 03:07:02 2020: setting parameter ‘engine’:‘realtime-priority’:’(null)’ to value “10”
Wed Nov 25 03:07:02 2020: setting parameter ‘engine’:‘port-max’:’(null)’ to value “16”
Wed Nov 25 03:07:02 2020: setting parameter ‘drivers’:‘dummy’:‘capture’ to value “0”
Wed Nov 25 03:07:02 2020: setting parameter ‘drivers’:‘dummy’:‘playback’ to value “0”
Wed Nov 25 03:07:02 2020: setting parameter ‘drivers’:‘dummy’:‘rate’ to value “96000”
Wed Nov 25 03:07:02 2020: setting parameter ‘drivers’:‘dummy’:‘period’ to value “256”
Wed Nov 25 03:07:02 2020: Listening for D-Bus messages
Wed Nov 25 03:07:02 2020: Starting jack server…
Wed Nov 25 03:07:02 2020: JACK server starting in realtime mode with priority 10
Wed Nov 25 03:07:02 2020: self-connect-mode is “Don’t restrict self connect requests”
Wed Nov 25 03:07:04 2020: Saving settings to “/home/pi/.config/jack/conf.xml” …
Wed Nov 25 03:07:17 2020: New client ‘ANALout’ with PID 1747
Wed Nov 25 03:07:19 2020: New client ‘ANALin’ with PID 1753
Wed Nov 25 03:07:21 2020: New client ‘AIRdigi’ with PID 1759
Wed Nov 25 03:07:23 2020: New client ‘jkmeter’ with PID 1764
Wed Nov 25 03:07:39 2020: New client ‘ardourprobe’ with PID 1800
Wed Nov 25 03:07:39 2020: Client ‘ardourprobe’ with PID 1800 is out
Wed Nov 25 03:07:39 2020: New client ‘ardourprobe’ with PID 1800
Wed Nov 25 03:07:39 2020: Client ‘ardourprobe’ with PID 1800 is out
Wed Nov 25 03:07:43 2020: New client ‘ardour’ with PID 1800
Wed Nov 25 03:07:43 2020: ERROR: JackEngine::XRun: client = ardour was not finished, state = Triggered
Wed Nov 25 03:07:43 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed Nov 25 03:07:43 2020: ERROR: JackEngine::XRun: client = ardour was not finished, state = Triggered
Wed Nov 25 03:07:43 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed Nov 25 03:07:46 2020: Connecting ‘ardour:Click/audio_out 1’ to ‘ANALout:playback_1’
Wed Nov 25 03:07:46 2020: Disconnecting ‘ardour:Click/audio_out 1’ from ‘ANALout:playback_1’
Wed Nov 25 03:07:52 2020: Client ‘ardour’ with PID 1800 is out
sorry, i learned that jack was still using the unchanged DUMMY setup from the conf.xml settings.
i changed the file for ALSA driver and then it worked out well
is there a problem with the DUMMY driver?
best regards
markus
Wed Nov 25 03:21:11 2020: Controller activated. Version 1.9.12 (unknown) built on Sun Feb 25 20:41:33 2018
Wed Nov 25 03:21:12 2020: Loading settings from “/home/pi/.config/jack/conf.xml” using expat_2.2.6 …
Wed Nov 25 03:21:12 2020: setting parameter ‘engine’:‘driver’:’(null)’ to value “alsa”
Wed Nov 25 03:21:12 2020: setting parameter ‘engine’:‘realtime’:’(null)’ to value “true”
Wed Nov 25 03:21:12 2020: setting parameter ‘engine’:‘realtime-priority’:’(null)’ to value “10”
Wed Nov 25 03:21:12 2020: setting parameter ‘engine’:‘port-max’:’(null)’ to value “16”
Wed Nov 25 03:21:12 2020: setting parameter ‘drivers’:‘alsa’:‘capture’ to value “0”
Wed Nov 25 03:21:12 2020: setting parameter ‘drivers’:‘alsa’:‘playback’ to value “0”
Wed Nov 25 03:21:12 2020: setting parameter ‘drivers’:‘alsa’:‘rate’ to value “96000”
Wed Nov 25 03:21:12 2020: setting parameter ‘drivers’:‘alsa’:‘period’ to value “256”
Wed Nov 25 03:21:12 2020: Listening for D-Bus messages
Wed Nov 25 03:21:12 2020: Controller deactivated.