Trying to play a DUO with my friend. He is just literelly 5 blocks from me (geographically).
Do I need to run my own server on the same machine with Jamulus client and have my friend connect to my server OR we both find a closest server in the servers list and connect there?
Any response highly apriciated!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd suggest connecting to the fastest one in the server list first and try that before running your own server. Once you are both connected, set New Client Level to zero. You can also mute anyone else if you need to.
But if that's too much work, you will need to set up a private server. See the docs here:
I would suggest a third, or rather "2b", option. I have sort of the same situation, my band members all living close by and typically the closest servers have ping times of 20-30 ms. To benefit from technically optimized ping (down to 1-2 ms locally) from the get go it would be nice to have the server really close by on occasions like that. I think the alternative to a private server, which sounds like a set up challenge including firewall issues, is to setup your own public server. I did so; took me 1-2 days of research on the very nicely maintained Jamulus forum pages, but the main challenge was the missing entry in the server list (fixed thru updates by now, I believe) and the 127.0.0.1 (localhost) initial connection choice. Other than that it could not be much easier than running one Jamulus instance in (public) server mode and then a second in client mode where you can connect to your own server all on your PC. Then the friend can access in simple client mode - server name should be self explanatory, like your band name or such. I believe the privacy preferences can be met with either the "new client level" and "mute" (as Gilgongo recomends) setting or a server name and message asking for guests to respect privacy. After all it seems musicians are very nice and respectful people
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, in order to minimise latency for you (but not for others outside your network), the advice is always to connect to your own server locally.
I might try doing a diagram illustrating public and private server hosting, partially for this reason. Diagrams sometimes help (or they can confuse even more).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My "Duo" experience (at the start of getting an ensemble setup working) was sort of sobering. Everybody lives in a small town in Germany that has fiber. The fiber has been laid by a sort-of government monopolised actor and is rented out to different providers. If I connect to a buddy about 2 mi away, the connection runs through a central handover point between the providers in a city about 150 mi away. Putting the "central" server at one of our private sites is severely disadvantaging the other person. Instead I have "rented" a virtual server for peanuts that is located in some geographic vicinity to that central handover point. And have set it up with a headless Jamulus server running under a reasonably current Ubuntu.
It's not as good as the best public servers in the public server list (I figured out that our preferred test server was apparently running on some Amazon cloud service but have not seen offers for virtual servers from them, at least not affordable ones), but better than running a server actually in our small town, counterintuitive as it may seem.
This experience may differ if everyone in your town shares the same provider. Sharing the same network infrastructure at the hardware installation level unfortunately is not enough to guarantee short routes.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The cheap offer from Amazon is called LightSail, if you need to run it continuously (5-10€/month).
However, at the beginning you have 1 year of free tier, with which you may have a machine continuously running for free (EC2, tx.micro servers).
I consumed my free tier years ago for other things. I use a faster EC2 machine and switch on/off before and after rehearsals - I spend about 3€/month for that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Trying to play a DUO with my friend. He is just literelly 5 blocks from me (geographically).
Do I need to run my own server on the same machine with Jamulus client and have my friend connect to my server OR we both find a closest server in the servers list and connect there?
Any response highly apriciated!
Hi Dima,
I'd suggest connecting to the fastest one in the server list first and try that before running your own server. Once you are both connected, set New Client Level to zero. You can also mute anyone else if you need to.
But if that's too much work, you will need to set up a private server. See the docs here:
https://github.com/corrados/jamulus/wiki/Running-a-Server
Last edit: Gilgongo 2020-04-13
Thank you so much for your response! and I'm sorry for not answering right away!
I will try both suggestions.
I would suggest a third, or rather "2b", option. I have sort of the same situation, my band members all living close by and typically the closest servers have ping times of 20-30 ms. To benefit from technically optimized ping (down to 1-2 ms locally) from the get go it would be nice to have the server really close by on occasions like that. I think the alternative to a private server, which sounds like a set up challenge including firewall issues, is to setup your own public server. I did so; took me 1-2 days of research on the very nicely maintained Jamulus forum pages, but the main challenge was the missing entry in the server list (fixed thru updates by now, I believe) and the 127.0.0.1 (localhost) initial connection choice. Other than that it could not be much easier than running one Jamulus instance in (public) server mode and then a second in client mode where you can connect to your own server all on your PC. Then the friend can access in simple client mode - server name should be self explanatory, like your band name or such. I believe the privacy preferences can be met with either the "new client level" and "mute" (as Gilgongo recomends) setting or a server name and message asking for guests to respect privacy. After all it seems musicians are very nice and respectful people
Yes, in order to minimise latency for you (but not for others outside your network), the advice is always to connect to your own server locally.
I might try doing a diagram illustrating public and private server hosting, partially for this reason. Diagrams sometimes help (or they can confuse even more).
Please do!!! Thank you!!
Really apreciate your input! Thank you.
Yeah, it looks like I need to dive in into "running your own server" world.
My "Duo" experience (at the start of getting an ensemble setup working) was sort of sobering. Everybody lives in a small town in Germany that has fiber. The fiber has been laid by a sort-of government monopolised actor and is rented out to different providers. If I connect to a buddy about 2 mi away, the connection runs through a central handover point between the providers in a city about 150 mi away. Putting the "central" server at one of our private sites is severely disadvantaging the other person. Instead I have "rented" a virtual server for peanuts that is located in some geographic vicinity to that central handover point. And have set it up with a headless Jamulus server running under a reasonably current Ubuntu.
It's not as good as the best public servers in the public server list (I figured out that our preferred test server was apparently running on some Amazon cloud service but have not seen offers for virtual servers from them, at least not affordable ones), but better than running a server actually in our small town, counterintuitive as it may seem.
This experience may differ if everyone in your town shares the same provider. Sharing the same network infrastructure at the hardware installation level unfortunately is not enough to guarantee short routes.
The cheap offer from Amazon is called LightSail, if you need to run it continuously (5-10€/month).
However, at the beginning you have 1 year of free tier, with which you may have a machine continuously running for free (EC2, tx.micro servers).
I consumed my free tier years ago for other things. I use a faster EC2 machine and switch on/off before and after rehearsals - I spend about 3€/month for that.