salsaman

Actually, now I have dug a bit deeper, having the connection mode no longer makes sense. Instead it is better to have two binary options: - auto start server(s) when...

I think additionally, shutting down the server on exit only makes sense if LiVES also started that server. It would be strange and probably annoying if LiVES connected to an...

LiVES uses jackctl_server_start(), the log file will not be created and it will not use rtp.

If it fails to start the server it will show an error dialog, and exit, and the preferences to start jack at startup will be disabled, as you saw yourself.

Then on restart it will try to connect to a running instance, if it fails this time it will show a different error, "unable to connect to jack server, please...

Some of this is not so user friendly, because in the past it was mainly used by Linux users, and in that environment, most users would be using pulseaudio, whereas...

jack was around before pulse, it was actually developed for Ardour, I am not sure if you are aware of that. But it was only ever really intended for precision...

If you are running jack in realtime mode, as it seems to be the case then it is even more demanding, in fact if you notice that LiVES is being...

Anyway, returning to the original issue, it seems like LiVES may have been able to create the jack server, but the problem occured because it was selecting a non existent...

Ah good to know that pulseaudio does exist there. It seems like I was given misleading information, or I misunderstood. I am aware that there is support for running pulse...