KPSK and aRtsd soundserver -- conflict resolution

As a realtime application, KPSK uses the soundcard directly. Conflicts can arise between KPSK and KDE due to the default aRtsd soundserver configuration to: start at KDE startup, run with realtime priority, and autosuspend when unused for more than 60 seconds. The documentation simply advises to turn off aRtsd completely--but what if you want to keep aRtsd running?

The solution to these conflicts is to:
1. Disable system notification sounds...system sounds continually tie up the soundserver, preventing it from autosuspending. If you want to keep system notification sounds, one option is to turn off the soundserver while running KPSK and turn it on again when you are done.
2. Configure aRtsd to autosuspend after a shorter period of time (15 or 30 seconds) to shorten the wait until aRtsd suspends to allow other applications to access the card.
3. Uncheck "run with realtime priority" -- this will help to resolve any performance lagging that is observed when aRtsd and KPSK are running simultaneously, with aRtsd suspended. This may also be helped by changing the system scheduling priority given to KPSK, e.g.
user@system:$ nice -10 kpsk