-
Notifications
You must be signed in to change notification settings - Fork 223
Running a Server
Home > Running a Server
Not if you don't want to. If you just want to play with other people, just choose somebody else's server from your list and get going.
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!
Much also 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.
For most people, connecting to a public server showing a low ping time is enough.
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.
-
The 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.
-
Running a private server (but not a public one) will require you to port forward on your router.
-
Jamulus doesn't currently support IPv6
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.