Skip to content

Update 2021-09-09-Inputs.md #1151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pcar75 wants to merge 2 commits into
base: release
Choose a base branch
from
+6 −5
Open

Update 2021-09-09-Inputs.md #1151

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6850624
Update 2021-09-09-Inputs.md
pcar75 Jun 29, 2026
f4e2240
Update _posts/2021-09-09-Inputs.md
pcar75 Jun 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions _posts/2021-09-09-Inputs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,11 @@ heading: "Points to note about inputs"

## Points to note about inputs

- If you want to connect 2 or more sources (e.g. voice + synth + guitar), it is important to note that Jamulus currently handles only 2 input channels (L/R). So the hardware being used must provide a mixed-down stereo output to Jamulus. Alternatively, run two instances of Jamulus, if your hardware supports it, or use virtual audio inputs to Jamulus for each hardware input.
- 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** output AND separate signals only (no mixed-down signal) on their **digital** output.
- A few Mixers with USB/FireWire/Thunderbolt will either send **only** a mixed-down signal to the **digital** output (small/budget mixers), or else also ADD a stereo mixed-down signal to the separate signals on the digital output.
- If you want to connect many sources (e.g. voice + synth + guitar), 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. Alternatively, run more instances of Jamulus (if your hardware/software supports it), or use virtual audio inputs (1) to Jamulus for each hardware input.

@mcfnord mcfnord Jun 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- If you want to connect many sources (e.g. voice + synth + guitar), 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. Alternatively, run more instances of Jamulus (if your hardware/software supports it), or use virtual audio inputs (1) to Jamulus for each hardware input.
- If you want to connect many sources (e.g. voice + synth + guitar), 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. Alternatively, run more instances of Jamulus (if your hardware/software supports it), or use virtual audio inputs to Jamulus for each hardware input. (Tip: You could use a DAW with virtual routing between your hardware and Jamulus (example : Reaper with ReaRoute).)

Not sure if this change captures the precise nuances, but I prefer keeping related details together. There are ways to logically separate them inline.

@pljones pljones Jul 1, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe "head" the bullet "Connecting multiple sources to Jamulus" and give each method its own second level bullet? I see three separate points being made, really.

@pcar75 pcar75 Jul 1, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pljones (...) I am not familiar with the specifics of HTML or any markdown language, so beyond putting or not a coma someplace (?!), I would not know what you are referring to.
Et mon français est bien meilleur ...
"head" the bullet ?

The right format should be ...

Title - "Connecting....
Text - Paragraph 1
Bullet 1 - "Audio interfaces... "
Bullet 2 - "Mixers ..."
Bullet 3 - "Mixers with USB/FireWire/Thunderbolt ..."
Bullet 4 - "A few Mixers ...."
Text italic - "Tip : You could use ..."
delete the unnecessary mention "(Thanks to pcar75 for this information)"
... but thanks for the thought anyway.

But what markdowns should be used ??

- 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.
(1) You could use a DAW with virtual routing between your hardware and Jamulus (example : Reaper with ReaRoute).

@pljones pljones Jun 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a "proper" way to do footnotes in markdown. Don't look at the Github markdown docs, as this is Jekyll and it uses a different sub/super-set of "standard" markdown.

@pcar75 pcar75 Jul 1, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pljones As I recall, I believe I had posted the the original topic in the Discussion section (or was it in SourceForge ?) ; some maintainer judged the topic sufficiently interesting to put and format it in the Knowledge Base. I am not familiar with the specifics of HTML or any markdown language, so beyond putting or not a coma someplace (?!), I would not know what you are referring to.
Et mon français est bien meilleur ...
"proper" footnotes ?


_(Thanks to [pcar75](https://github.com/pcar75) for this information)_