For Beast, we should simply work as well and as user-friendly as the browsers by picking PuleAudio by default, trying JACK only if Jackd is running and falling back to the first ALSA hw device if it is not busy.
In the situation where PulseAudio and JACK are available, I think we should choose JACK. It is highly unlikely that jackd is running by accident. The user made it run. So the user wants to have low latency communication between all his pro-audio applications. Note that Bitwig doesn't support inputs if you use PulseAudio. I guess they also didn't want to implement drift compensation.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.