Pinging www.google.ca [2607:f8b0:400b:802::2003] with 32 bytes of data:
Reply from 2607:f8b0:400b:802::2003: time=22ms
Request timed out.
Request timed out.
Reply from 2607:f8b0:400b:802::2003: time=40ms
Ping statistics for 2607:f8b0:400b:802::2003:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 40ms, Average = 31ms
Jamulus Live Performance Portal
Hello out there,
I am a musician now working from home as there are no venues open. I am working with a live performance portal call “Jamulus” to practice with my band mates and also jam with other musicians in almost real time. The musicians I am currently working with are in Toronto and I live in Ottawa. Three of five are able to connect (they are on Bell Fibe) without too much latency and can rehearse and collaborate in almost real time, one can’t connect due to hardware and tech issues and then there is me. I am on Rogers ignite 500. I am able to connect however my connection to the dedicated music server has a high latency / delay of 80ms making real time playing unworkable. A trace from the host server to my IP address shows 13 hops (servers) where the others are only going through three. How can I reduce the latency issue? Can I manually select a more direct route to the dedicated server (on Bell Fibe). Can I use a different router or hub to bypass the Rogers modem Ignite modem? Will a VPN work?
Hope someone out there can direct me to a solution. Hungry to get back to the jam…
I don't want to jinx anything but it looks like Rogers has been busy behind the scenes.
First of all, they have readdressed the section of the network that I am connected to. (They were previously using an address range from the 126.96.36.199/11 CIDR block, now from 188.8.131.52/14)
More importantly, latency on ping tests is waay down, with a deviation of only 2.8 ms from the mean of 11.8 ms:
--- 184.108.40.206 ping statistics ---
3600 packets transmitted, 3600 received, 0% packet loss, time 3603974ms
rtt min/avg/max/mdev = 6.903/11.840/81.653/2.841 ms
Only 25 (of 3600) pings had a RTT of 50 ms or higher.
I'll test again later today but this is the best that I have seen things in quite a while.