www.michael-jansen.biz

As an update to the last article here my latest changes to the setup that finally make it work without the hassle of crashing at login once.

Additionally i forgot to mention a script i found that checks certain settings to see how your system scores in terms of low latency.

Changes to the Autostart Script

I now moved the file from the .kde/Autostart/ folder to .kde/env. This one is called at the very beginning of startkde and is able to induce environment variables into the kde session. The content was changed too.

#!/bin/sh
 
killall timidity
killall jackd
 
( cd /tmp;
  nohup qjackctl >/tmp/${LOGNAME}-qjackctl.log 2>&1 &;
  sleep 10;
  nohup timidity -iA -Oj >/tmp/${LOGNAME}-timidity.log 2>&1 &; )
 
export JACK_START_SERVER=1

The shebang line is not really needed because the script is sourced by startkde. The parentheses around the commands make it execute in a subshell. The sleep 10 command does not halt your login progress because of them. It only makes sure qjackctl had enough time to start the jackd server. You have to enable Start JACK audio server on application startup in the Misc tab of the Jack Audio Connection Kits Setup dialog. Because of this setup you can use qjackctl to configure the settings an be sure that on the next login you will have them active.

Realtime configuration quick scan

Additionally there is a script that checks certain settings on your system and tells you what to do to get nearer to a realtime configuration. You can find it on google code: realtimeconfigquickscan. To use it clone it with mercurial from https://realtimeconfigquickscan.googlecode.com/hg/ . Run it and it will tell you what to do. Resize the result dialog or you will miss important information on the very right side.

Mike