I have been testing Jamulus on my Raspberry Pi 3 B with a Behringer U-Phoria UMC202HD and it works quite well.
Since schools, choirs,... still can't play together jamulus is a very valuable piece of software. Unfortunately not everybody can set it up on their own. That's why me and some others came up with the idea of installing Jamulus on Raspberry Pis, connect them to an audio interface set them up,... The only thing a musician should have to do is to plug in an ethernet cable + microphone or instrument + headphone and the Pi should automatically connect to a specific server.
Since of course all the Pis are behind a NAT/firewall accessing them remotely is not easy. Reverse SSH + Ansible might solve the problem.
Another yet unsolved problem is how to let the musician control all the jamulus features like the faders since it is planned to let the device be as headless as possible.
I have already created a repo with some (unfinished and untested) scripts to setup some basic stuff, install a basic gui (openbox, which I actually don't want to use),... https://github.com/ann0see/rasjam
I assume there have already been people testing something similar?
I'd love to have some input mainly on the headless part on the clients.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your input! I just implemented the headless version of jamulus in the installation script. Unfortunately it seems as if jamulus can't be controlled without a midicontroller in headless mode (especially faders, paning, chat,...). At least the faders should be somehow possible to change. I think the way to do it at the moment is to change the config file with a e.g. php script and restart jamulus. But that's not really a clean solution.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
we have had good test results with using the full remote control fuctionality on zoom to troubleshoot users. you have remote mouse and keyboard control.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
VNC wouldn't be an option since then the users would have to install something on their devices (probably the people who use the raspi wouldn't know how to do that on their own)
Does jamulus support some kind of other outside interaction/API or can a midi controller be emulated?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does jamulus support some kind of other outside interaction/API or can a midi controller be emulated?
I'm afraid the answer to the first question is not currently, but I don't know the answer to the second. Perhaps worth asking as a follow up comment on that Github issue thread I mentioned?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Rachel,
I don't quite see how one could control a Jamulus client without the GUI. Without knowing who is connected and in which order this seems to me to be a very hit or miss deal.
From what we see here on the forum almost all the problems setting up Jamulus come from people trying to use their computers internal audio interface, be it PC or MAC. As you are already using an interface with its own ASIO driver it should be no problem even for uninitiated to install Jamulus and the interface and be up and running.
As most people already have a PC or MAC that is good enough for Jamulus together with an external audio interface I don't see the advantage of running another computer "in the blind". And if all your people could be convinced to use the same audio interface the collective knowledge should reduce the work for you even if you might have to do a remote session once to get some of your people up and running.
Just my thoughts,
Don
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
there is a clear use case for running a headless server with dxtdnsive renote control: run theclient on a raspberry pi and use your phone or tablet/ipad to control it. a webserver running on the raspberry would suffice but that requires some sort of remote process API to the jamulus client.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Mats,
For servers I can see what you mean, although except for turning recording on and off I don't see the necessity and that is already possible.
If you really need the server GUI run the Win10 server on Azure and you can control using the graphic remote screen.
In any case, I was talking about the client, as had the original poster here.
Don
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have been testing Jamulus on my Raspberry Pi 3 B with a Behringer U-Phoria UMC202HD and it works quite well.
Since schools, choirs,... still can't play together jamulus is a very valuable piece of software. Unfortunately not everybody can set it up on their own. That's why me and some others came up with the idea of installing Jamulus on Raspberry Pis, connect them to an audio interface set them up,... The only thing a musician should have to do is to plug in an ethernet cable + microphone or instrument + headphone and the Pi should automatically connect to a specific server.
Since of course all the Pis are behind a NAT/firewall accessing them remotely is not easy. Reverse SSH + Ansible might solve the problem.
Another yet unsolved problem is how to let the musician control all the jamulus features like the faders since it is planned to let the device be as headless as possible.
I have already created a repo with some (unfinished and untested) scripts to setup some basic stuff, install a basic gui (openbox, which I actually don't want to use),...
https://github.com/ann0see/rasjam
I assume there have already been people testing something similar?
I'd love to have some input mainly on the headless part on the clients.
Hi Rachel,
I think there has been some discussion around some of the issues you raise. For example:
https://github.com/corrados/jamulus/issues/472
It might be worth seeing if you can contact https://github.com/Brian-McBride perhaps?
Thanks for your input! I just implemented the headless version of jamulus in the installation script. Unfortunately it seems as if jamulus can't be controlled without a midicontroller in headless mode (especially faders, paning, chat,...). At least the faders should be somehow possible to change. I think the way to do it at the moment is to change the config file with a e.g. php script and restart jamulus. But that's not really a clean solution.
I've not been involved with midi, but if you're referring to this:
https://github.com/corrados/jamulus/wiki/Tips,-Tricks-&-More#using-the---ctrlmidich-midi-controller-channel-option
Then yes, it would need a midicontroller it seems.
we have had good test results with using the full remote control fuctionality on zoom to troubleshoot users. you have remote mouse and keyboard control.
Running Zoom headless on a Raspberry Pi would be a bit of a challenge though, no? Mind you, maybe VNC? But then you'd need the Jamulus UI too...
Last edit: Gilgongo 2020-08-25
VNC wouldn't be an option since then the users would have to install something on their devices (probably the people who use the raspi wouldn't know how to do that on their own)
Does jamulus support some kind of other outside interaction/API or can a midi controller be emulated?
I'm afraid the answer to the first question is not currently, but I don't know the answer to the second. Perhaps worth asking as a follow up comment on that Github issue thread I mentioned?
Hi Rachel,
I don't quite see how one could control a Jamulus client without the GUI. Without knowing who is connected and in which order this seems to me to be a very hit or miss deal.
From what we see here on the forum almost all the problems setting up Jamulus come from people trying to use their computers internal audio interface, be it PC or MAC. As you are already using an interface with its own ASIO driver it should be no problem even for uninitiated to install Jamulus and the interface and be up and running.
As most people already have a PC or MAC that is good enough for Jamulus together with an external audio interface I don't see the advantage of running another computer "in the blind". And if all your people could be convinced to use the same audio interface the collective knowledge should reduce the work for you even if you might have to do a remote session once to get some of your people up and running.
Just my thoughts,
Don
there is a clear use case for running a headless server with dxtdnsive renote control: run theclient on a raspberry pi and use your phone or tablet/ipad to control it. a webserver running on the raspberry would suffice but that requires some sort of remote process API to the jamulus client.
Hi Mats,
For servers I can see what you mean, although except for turning recording on and off I don't see the necessity and that is already possible.
If you really need the server GUI run the Win10 server on Azure and you can control using the graphic remote screen.
In any case, I was talking about the client, as had the original poster here.
Don