Kevin Windrem

Thanks, I'll do that.

I'm trying to manage a faceless Jamulus CLIENT (on Debian) in such a way that it remains connected to the external audio interface and the server. I use process status to determine if Jamulus and jackd are running and use a directory listing to determine if the audio interface is connected. I can't find a way to determine of the client is connected to a server. I've looked at the Jamulus stdout and stderr streams and also looked at netstat and other network traffic utilities and just can't seem to...

Unfortunately the link above no longer exists. Guess he took it down. I would also like to see an iPad version. There are many musicians in my girl friend's circle that don't have a modern computer but many have or are about to invest in a recent iPad. USB-C ethernet dongles appear to "just work" on the newest models with a USB-C connector on them. No joy with an older iPad with Lightening connector and USB adapter.

My other post postulates the addition of a "None" selection as well. This could be used when no match is found as well rather than showing noting in the drop-down before it's opened. None would be used to disable either the input or the output, e.g., for a "listen only" client.

Really, all that needs to be saved is the name of the input and output devices, then select those on restart if they currently exist. In another issue, I'm also suggesting separating selections of input and output devices because the combined list gets long very quickly. Two short lists are better than one verly long one.

I am playing with Jamulus running on a Raspberry PI and on it's 800x480 7" touch screen. On that small a screen, the important part of the user interface gets cut off so you have to scroll up and down. There is real estate above and below the scrolling area that is essentially wasted. Refer to the attached screen shot that illustartes the problem Is there a way to increase the scrollable area, moving "Personal Mix ..." up or eliminatint it? If the entire gray area were available for the mixer, I...

I don't mind leaving off "Same as Input". It does add complications and additional coding and in these settings will probalby be visited by most infrequently.

I belive I've come up with a mechanism that's both easy to unserstand and simpler to use. The Soundcard area of the Settings dialog is changed as shown in the attached image. This splits the Device selection into an Input Device and and Output Device drop-downs which reduces the number of choices significantly. (The list includes the available input or output devices, not every combination of all input and output devices.) The Input Channel Mapping and Output Channel Mapping drop-downs are shown...