Skip to content

Commit

Permalink
Corrections to EN files (#899)
Browse files Browse the repository at this point in the history
Co-authored-by: John Dempsey <1750243+mcfnord@users.noreply.github.com>
  • Loading branch information
ignotus666 and mcfnord authored Jan 15, 2023
1 parent 7bb9750 commit 25995a5
Show file tree
Hide file tree
Showing 5 changed files with 62 additions and 65 deletions.
5 changes: 2 additions & 3 deletions wiki/en/Command-Line-Options.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ permalink: "/wiki/Command-Line-Options"

# Command Line Options

## Shared commands
## Shared commands

{% include_relative Include-Shared-Commands.md %}

Expand All @@ -17,5 +17,4 @@ permalink: "/wiki/Command-Line-Options"

## Server only commands

See [Running a Server](Running-a-Server#server-mode-options)

See [Running a Server](Running-a-Server#server-mode-related-options)
9 changes: 4 additions & 5 deletions wiki/en/FAQ.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,15 +22,15 @@ permalink: "/wiki/FAQ"

### Is there a metronome, synchronization, or some other way of keeping in time?

No. Musicians on a Jamulus Server play in real time together as they would in person. If you want to have a time signal, then there are shared metronome solutions on the Internet you can try. But it’s probably best to just minimise latency so nobody has an overall delay more than about 30-50 ms.
No. Musicians on a Jamulus Server play in real time together as they would in person. If you want a time signal, there are shared metronome solutions on the Internet you can try. But it’s probably best to just minimise latency so nobody has an overall delay more than about 30-50 ms.

Bear in mind also that all participants should follow [The Golden Rule](/wiki/Client-Troubleshooting#you-all-sound-ok-but-its-difficult-to-keep-together) which will also determine whether you can play in time properly.

### How do I know if I can join a Server? Are there rules?

If somebody lists a Server on one of the Directories built into Jamulus, they accept that anyone can play on it. Jamulus has no password protection or other authentication mechanisms. Whilst some Servers may state their policies in the welcome message you will see in the chat window, Jamulus itself does nothing to enforce these.

Note also that Servers do not have to be registered on a Directory in order for Jamulus Clients to connect to them. Server operators can just give out the address of their Servers to those they want to play with, and they can then connect directly. Have a look at [this overview for more information](/wiki/Running-a-Server#server-types).
Note also that Servers do not have to be registered on a Directory in order for Jamulus Clients to connect to them. Server operators can just give out the address of their Servers to those they want to play with, and they can then connect directly. Have a look at [this overview for more information](/wiki/Running-a-Server#server-modes).

### Why shouldn’t I use wireless equipment?

Expand All @@ -46,7 +46,7 @@ Of course, if you are playing an acoustic instrument, or are a singer, it will b

### Do I need a fast Internet connection?

No, especially if you don't run a Server to host other musicians. Having a low ping is more important. For most people on standard broadband (e.g. 10 Mbit/s down and 1 Mbit/s up) you will have no problems. For those running Servers at home, depending on how many people join, you may encounter issues if your _upstream_ bandwidth is lower than about 5 Mbit/s.
No, especially if you don't run a Server to host other musicians. Having a low ping is more important. Most people on standard broadband (e.g. 10 Mbit/s down and 1 Mbit/s up) will have no problems. For those running Servers at home, depending on how many people join, you may encounter issues if your _upstream_ bandwidth is lower than about 5 Mbit/s.

### Do I need to run a Server?

Expand All @@ -70,5 +70,4 @@ Adding video support adds a lot of complexity. You can use other software like J

Normally, network address translation (NAT) firewalls prevent incoming requests initiated from outside the local network. Inbound traffic is only possible for packets relating to an outbound request (strictly speaking, “related” and “established” packets to an initial outbound connection). In Registered Server mode, when your Jamulus Server connects to a Directory it of course initiates an outbound connection. From then on, the Directory sends (established/related) connection “pings” (not ICMP pings) to your Server at regular intervals to keep the relevant NAT port(s) open on your router/firewall.

However, in Unregistered mode, Clients have to **initiate** connections into the Server’s network. NAT firewalls prevent this, so you need to tell them to allow incoming connection requests on the Jamulus port using port forwarding.

However, to reach an Unregistered Server, each Client has to **initiate** a connection into the Server’s network. A NAT firewall prevents this, so you need to configure the firewall to allow incoming connection requests on the Jamulus port using port forwarding.
Loading

0 comments on commit 25995a5

Please sign in to comment.