Thanks for the quick reply on the previous post, Hans.
ok... so the last post wasn't directly related to the OP... but indirectly, because I was asking about running the CLI version as a service... my mind connected some dots
Still wondering about the following:
Q2: I've got custom ST presets saved. My theory is that the CLI version will start even if the GUI is flaky on Debian. Is it possible to run my existing configuration from the CLI version of ST8.30 -- bybassing the GUI altogether? Is this even possible with my workflow, or is the CL version limited only to wav or raw pcm, i.e., not jack aware?
Q3: Would it be more reliable to create a systemd unit to start ST, then an entry in Startup Applications?
I just put the new machine back into service and I've got a remote broadcast tomorrow, so it will probably be Wednesday before I can test 8.31. I'll let you know what happens!
My existing Jack/ST workflow is:
Rivendell out -> ST in (( rivendell_0:playout0L -> PortAudio:in_0 // rivendell_0:playout0R -> PortAudio:in_1 ))
ST out -> Liquidsoap in (( PortAudio:out_0 -> liquidsoap:in_0 // PortAudio:out_1 -> liquidsoap:in_1 ))
ST out -> System Playback in (( PortAudio:out_0 -> system:playback_1 // PortAudio:out_1 -> system:playback_2 ))
*I also have system capture -> Rivendell in defined in QJackCTL (but it's not dependent on ST)
Thank you again!!!