> The thing is that because Jack is essentially a wrapper for ALSA if someone codes PA support for Jack then we kill two birds with one stone.
What if a user has installed ALSA but not Jack: Will it still work?
So if Audacity statically links libjack.a, will that contain
everything a user needs just to play through ALSA?
This is not true of arts or esd; they're useless APIs if their
respective daemons are not running.
> If I'm understanding correctly then you may want to take a look at the code for alsaplayer. It does something very similar on startup.
> Basically it takes a flag for the audio driver. If It can't find that one then it recurses through all the other supported drivers until it finds one it can use. If it doesn't find one then it uses a dummy "no sound driver" so at least you can still see the scopes.
> Is this similar to what you are referring to?
The portaudio team has already discussed adding this feature.
We could do the same thing in Audacity, outside of portaudio,
if they don't get around to it. That would be less work.
But I'd prefer to help make the change to portaudio, since
that would be potentially useful to more people.