Thank you tim and Alastair for your replies. The problem seems to lie with getting jack (jackit 0.94) to work on my system. Starting Jack with Qjackctl gives an error message: ... JACK: unable to mlock() port buffers: Operation not permitted cannot set thread to real-time priority (FIFO/20) (1: Operation not permitted) cannot use real-time scheduling (FIFO/10) (1: Operation not permitted) 12:24:50.512 Could not connect to JACK server as client. Starting Jack from the command line < jackd -d alsa -d hw:0 > results in: loading driver .. creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|rt|32bit control device hw:0 configuring for 48000Hz, period = 1024 frames, buffer = 2 periods Couldn't open hw:0 for 32bit samples trying 24bit instead Couldn't open hw:0 for 24bit samples trying 16bit instead Couldn't open hw:0 for 32bit samples trying 24bit instead Couldn't open hw:0 for 24bit samples trying 16bit instead after which the system monitor (KDE System Guard) lists jackd as active and other audio functions which are not compatible with jack do not work properly. However jack-reliant applications still fail to respond. For example starting QSynth, whether or not jackd is running, gives an error message: ... failed to create the audio driver (jack) .... I will hunt about on the jack homepage for a bit and try to make sense of the situation, however any guidance is always appreciated. David