Multi Channel Fader on one Jamulus

[nicolopozzato]

I play with some friends... All of them have a simple request...

A way to send to the Jamulus Server multiple audio over different fader in the mixer, all of this can be Mono or Stereo.

Example:
I have a microphone, it's mono, so in the first channel I set it in mono, then i can select what device, and the input channel of that device.
After that I have a Keyboard, so in the second channel i can set it in stereo (stereo->stereo, for send two channel, or a stereo->mono to mix down a mono track), then i can select what device, and then i can select the two channel.

After the input I can select if i want a mono or stereo return from the server to hear in the headphone.

We ask this because we all have to open more Jamulus each time, and this leads us to throw away server bandwidth.
We need everyone to do their own mix on headphones, some musicians have two or more keyboards and a microphone, so they start jamulus many times.

If you put together all the open Jamulus as a second or more channel (99% in stereo) we find ourselves having a lot of bandwidth thrown away by the server because the server sends the mix to all the jamulus.

It would be nice to have a setting for unlimited channels. every channel could be mono or true stereo or a strereo mix down mono, every channel could select a different audio device and different channels, also a different name.

In this way you can eliminate the complexity of running multiple Jamulus client and the extra bandwith trown away.

[pljones]

You can hook up a DAW to Jamulus - but it depends on having routing that both ends understand. JACK on Linux is fine. I can't comment on MacOS. On Windows, I run it using Reaper with about 60 or 70 different local channels running through the mixing desk before being routed out to Jamulus and the return audio fed back again.

[nicolopozzato]

Ok but all the channel are local, only for you... The other member see only one channel. I was asking for a way to send multiple channel like I was using multiple Jamulus, so every member can adjust their own audio.

[pljones]

You can run multiple instances of Jamulus, too, if you do it right - that gives that level of control, too.

[nicolopozzato]

But running multiple Jamulus add up also all the output from the server, but they are not needed... So I was thinking at a solution to send multiple separate channel in a Jamulus Server, but to have only one feed to ear from the server.

[pljones]

Two input channels on one client of software adds to the server just as much as two input channels on two clients. It makes no difference - it's just as much network load and CPU load.

[nicolopozzato]

Yes, if I send two signal it's the same as two client, but if I use two client I receive two mix down audio from the server... but I only need to ear one. So in this case the server is creating a mix track that i never listen and so utilizing cpu and internet.

Also in the current state i have Mono/Mono, Mono in/Stereo out but can't send a stereo signal but earing a mono mixdown (Stereo in/Mono out)
This could be useful for a stereo keyboard while I'm wearing headphone only in one ear.
Also this reduce at the same time the extra bandwith for the first problem of having to use multiple jamulus (each of us use many jamulus to have all the voices and all the instruments in the mixer so anyone can have their mix, so keyboard, synth, drum... all of this are stereo but just selecting Stereoin/Monoout clould help with reducing the extra bandwidth)

[pljones]

Actually, yes, you're right about the amount of data from server to two clients being more... (By the one downward stream, plus, if you use them the couple of bytes for the levels.) -edit- Oh dear, must have been a bad day: yes, everything to the second client would be extra...

[Snayler]

If you're under Windows, Voicemeeter might be a good solution for you. You can mix up signals from different audio sources and it lets you control each signal's output, so you can adjust volumes as you'd like. I'm using it so I can have my guitar and my computer's microphone going into Jamulus at the same time, so only one Jamulus client needs to be running.

The same can be accomplished under Linux by using Jack and alsa_in to mix multiple audio interfaces together.

In MacOS, from a fast google search, it appears this is also possible by creating an "Aggregate Device".

[nicolopozzato]

You can mix up signals from different audio sources

Yes. But as saied already, in this way every other member in Jamulus get only ONE fader in their mixer! And because I use this in a live streaming situation some friends have a "sing mic" (mono), and instrument (stereo or mono) and a "non live mic" (mono).
Everyone need a particular mix in their ears and also in the streaming pc in the sanctuary we don't want all the "non live mic" as they are only for speak to each other musicians and singers!

I'm using it so I can have my guitar and my computer's microphone going into Jamulus at the same time, so only one Jamulus client needs to be running.

Only you are able to set the mix about mic and instrument volume... so if another person in jamulus don't want your voice so loud they can't do anything... in our setup with multiple Jamulus client we can have fader for every things! So everyone can have their right mix in their ears!

All of this create pointless use of server cpu and bandwith! I don't know if it's simple or not to implement. But a first step is to divide the "send" from the "receive" so later it's just more socket that has to be open to send multiple channel... and we can receive what we need only one time! Also in this situation we could send a stereo signal (so if someone use stereo as return can listen the instrument in stereo) but recive a mono mixdown!

[WolfganP]

Perhaps an easier way to implement this functionality is for the Jamulus client to start as a secondary/slave mode in second/third/... instances on the same machine, where it only contributes with an upload stream and doesn't request a download mix from the server.
Running multiple instances may be cumbersome for the end user, but the upload/input only mode could be easier to implement for the @devs as a general switch.

[kilcup]

I'm a happy camper who would be even happier with the multiple fader feature.
For now I am running multiple instances of Jamulus (in the Linux/Jack world),
and have one small hopefully easy request --- how about having the client display the
choices made in the profile setting? Call it a first world problem, but I occasionally get
confused as to which instance is which, something I resolve now by opening up the
setting menu. How about saving me a mouseclick and displaying a small version of the
name/instrument icon somewhere, even before we connect?
and again kudos for everything!