-
Notifications
You must be signed in to change notification settings - Fork 221
Running a Server
( en | es )
Home > Running a Server
Not if you don't want to. You can just choose somebody else's server from your list and get going.
Don't want strangers interrupting? Once you and your friends are connected to a public server, press the "solo" buttons on the musicians each of you want to play with. Anyone you don't solo will see a "muted" icon on your channel. And you won't hear them.
It's very important that you read and understand what type of server you want to run. Please read the overview on Server Types then come back here.
The capability of the server itself (and the network it's on) is NOT the main determinant of the quality of a Jamulus session!
Many people attribute problems to the server that are in fact problems with the client. Much depends on the clients' hardware, the networks that they are on, and whether they are sticking to Rule Number One. There is therefore no guarantee that you will achieve lower latency or better overall performance by having your own server.
If you plan to be playing regularly with the same people, you are strongly advised to first make sure that each member of the group is set up to use Jamulus properly. Do this by finding a public server with a reasonable ping time for all of you (20ms or less perhaps), all connect to that and work to fix any individual issues (verifying that they can follow Rule Number One in particular). Use the solo technique above to prevent being interrupted if needed.
Once any issues with musicians have been solved in this way, you can then investigate hosting your own server either at home or on a cloud host such as Amazon, which may result in better latency than servers run at home. For example, see this guide to using AWS Lightsail by Jamulus user Simon Tomlinson (Facebook)
A typical jam might have 4 people, for which you would need 200Kbps * 4 = 800Kbs (0.8Mbps) up and down. So if you have a 10Mbits down and 1Mbps up broadband connection, you may start running out of bandwidth if a fifth player joins, particularly if other musicians choose settings that increase their usage. You may want to check that you have enough speed for that. Read more about bandwidth use at different quality settings.
-
Consider using a cloud host to get better ping times if you having problems
-
Any server should have at least 1.6GHz CPU frequency and 1GB RAM
-
Running a server may require you to adjust any firewalls running on or outside of your machine or cloud host.
-
Running a private server at home (but not a public one) will require you to port forward on your router.
-
Jamulus doesn't currently support IPv6
Server operators may also be interested in downloading this set of useful tools from the Jamulus repository (clone the Git repo and also call git submodule update --init
).
See the Server Troubleshooting FAQ
For Windows, Macintosh and Linux
-
Get detailed help with the Jamulus Help Manual
-
Got a question or problem not covered here? Have a feature request? Try the discussions forums
-
Found a bug? Please post these to Github Issues
If you have a couple of minutes, please fill out our anonymous survey!
This wiki is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.