KB : Multiple Inputs correction

[pcar75]

( Abandoning PR #1151 , to try and follow regular process )

In the KnowledgeBase section of the Jamulus website, in the article Multiple Inputs / Points to note about inputs , I recently realized that one of my description was in error.

(...) Mixers with USB/FireWire/Thunderbolt generally output a mixed-down signal on their analogue output AND separate signals only (no mixed-down signal) on their digital output. (...)

Generally these mixers only send mixed-down audio on both their analog and digital output.

As it is more oriented towards newcomers, I have reformulated the post below to improve it while retaining it's generality. My apologies to anyone the error may have inconvenienced.

Connecting multiple sources to Jamulus

If you want to connect many sources (e.g. voice + keyboard + bass), it is important to note that Jamulus currently handles only 2 input channels (either Mono 1 and 2 or Stereo L/R). So the hardware (audio interfaces or mixers) being used must provide a mixed-down 2 channels output to Jamulus.

• Audio Interfaces generally output a mixed signal on their analogue output, but separate signals (1 per source) on their digital output (USB/FireWire/Thunderbolt).

• Mixers generally only output mixed-down signals on their analogue output.

• Mixers with USB/FireWire/Thunderbolt generally output a mixed-down signal on their analogue and digital output.

• A few Mixers with USB/FireWire/Thunderbolt (sometimes called "mixerface") can send a stereo mixed-down signal AND/OR separate signals on the digital output.

Alternatively, you could run more instances of Jamulus, if your hardware/software supports it, or use a software mixer with virtual routing between your hardware and Jamulus (examples: Reaper with ReaRoute [Windows], UAD 8's Console).

[ann0see]

Have a look at the _posts folder. You should be able to add the article there. You could ping gilgongo I believe

[ann0see]

Hmmm. I think you could just fork the jamuluswebsite repo and write a file in this style https://github.com/jamulussoftware/jamuluswebsite/blob/release/_posts/2020-03-28-Server-Rpi.md then open a PR.

[pcar75]

Done. Thanks.

[pcar75]

@ann0see or any website maintainer.
I have followed the update process but I'm not sure my update is in the pipeline to the website update; I expected it would be in the repository's "next release" branch , but it's not. Could a maintainer help me ?

Maybe a misunderstanding from my part ??

• The suggested file name was "Update 2021-09-09-Inputs.md" . As all other files had dashes (-) between words, I changed the name to "Update-2021-09-09-Inputs.md".
• At the end a message was displayed that said the update was OK and on to the update process and that I could delete the current form, which I did.

[ann0see]

It should go to release and then GitHub should automatically merge it to next release

[ann0see]

Also you must raise a PR to jamulussoftware/jamuluswebsite not your fork