![]() ![]() I love the idea of having a generic way of getting the audio output out of Jamulus and feed it into Zoom, Jitsi, WebEx, etc. I did my first "Zoomulus" session last week and it went really well. But aux buses or subgroups could be used. ![]() SoundDesk allows routing a changes audio directly to any audio device, bypassing the main mix. Any other mixer should work but you need separate outputs to feed Zoom and Jamulus with independent mixes. I use SoundDesk as a mixer to tie everything together and BlackHole to loop audio from one app back into another. In my application, I wanted to also feed Zoom audio back to Jamulus so the musicians hear audience feedback during song breaks (e.g., applause). I'm doing the "house mix" on a separate Jamulus client that differs from any musician mix although that may not be necessary. There is increased audio delay doing this so I recommend not using this approach if you are one of the musicians contributing a part to Jamulus. You can even use Apple's sound system Multiple output device so you can route Jamulus audio to Zoom and your headphones. On the Mac, it's pretty easy to hook Jamulus into the Zoom computer input (Zoom Audio Device). I have put a system together that cross-couples Jamulus and Zoom. It would need to access one client mix and route it to the Zoom app. Hooking Zoom into the server is an interesting idea. Just found that a client can autoconnect to a server using the -c command. but definatly no physical cables between them. I think jack + zoom can already run from a scripts/ command line. It can be quite low powered as it is only grabbing the audio and passing it on to jack. ![]() It can all run from a script but may have a gui that we can remotely connect to. We can install this client on a small server somewhere. So that it can startup, have a user profile name, connect to a specified server etc. On reflection, a more realistic solution might be to ask for more variables to starting a jamulus client at a command line. You can discuss that in the jamulus sourceforge open discussion. Please do not add discussion of how a client / singer can create this link manually each time. Also that it somehow has the ability for the same server to be used for multiple large choirs and therefore have some mechanism to use different zoom meeting logons for each. Therefore may I suggest that a strategic solution is built with perhaps the zoom user id and password stored in a config file. There are various methods out there but they appear awkward and really I think it should be part of Jamulus server build. The management of those choirs are stipulating that a link must be made to a zoom call so people can 'sing along'. I cringe as I type this request and this goes against everything I believe in for Jamulus usage, however it is quite apparent that there is a user requirement to have Jamulus audio out to a zoom conference call so non Jamulus users can (.sort of) be part of 'the choir experience'.Īs Jamulus has now successfully been developed for the large choir, it is clear that there are a sizable minority in those choirs that will never, ever use Jamulus. ![]()
0 Comments
Leave a Reply. |