-
Notifications
You must be signed in to change notification settings - Fork 93
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.
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
jamulussoftware:release
Choose a base branch
from
pcar75:patch-1
base: release
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+6
−5
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -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. | ||
| - 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). | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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. |
||
|
|
||
| _(Thanks to [pcar75](https://github.com/pcar75) for this information)_ | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if this change captures the precise nuances, but I prefer keeping related details together. There are ways to logically separate them inline.
There was a problem hiding this comment.
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.