• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Internet latency problems
#1
I play with a 4-piece band and we are using JamKazam to rehearse during lockdown. We all live within 10 miles of each other and are all using wired ethernet connections. The other 3 band members experience very little latency between them, but I seem to have a much greater Internet latency and one that varies wildly from about 20ms to over 100ms. I use the same ISP as 2 of the other band members. 

I am using a Behringer UM2 interface and a MacBook running Catalina. My interface latency is 10ms, using a frame size of 2ms. This is not great but within usable limits.

I have tried leaving JamKazam and doing an internet speed test, using one of the publicly-available test sites. Having done this a few times, the results are always around 20Mb/s downstream, 1.8Mb/s upstream and a ping latency of around 15ms (to a server in London, at least 70 miles away). This looks as though my internet connection is OK.

Lowering my outgoing bitrate to 128kbit/s improves things a little, but not sufficiently.

Can anyone please suggest what I might do to diagnose or fix this problem--or is it simply that there is a poor internet service in my neighbourhood?

Any suggestions much appreciated.
  Reply
#2
1.8 upstream or upload should be enough for 4 participants in a session (and that will be without video).

But not more.

The recommended upload for full function is 25 mbps. According to the latest information from a moderator here in forum.

That should be for 8 participants - with 4 of them using video.

The PING test should be done to your internet provider, I think. Mac has a special feature for PING test, by the way.

I have no special solution.

But GB is so to speak "famous" for bad connections, That is my experience.

Having the same internet provider - as 3 of you - is usually giving better connection.

Look here, maybe
LATENCY, mostly TOTAL LATENCY
> https://forum.jamkazam.com/showthread.php?tid=171

And search for latency - and similar

And/or wait for better guidance
  Reply
#3
Thanks, Hans, for the reply and the link to the previous latency thread.

First, just to confirm that none of the band members are using video.

Thinking about it, my 1.8Mbit/s upstream does sound low (I'm sure I used to get around 5Mbit/s). I tried reporting it as a fault to my ISP but they proposed to send an engineer to my house, which is unacceptable at present, as I belong to a category who are not supposed to leave the house or allow anyone else in. I doubt if the problem is in the house, though, unless it is the modem or router--which could be fixed by sending me a new one!
  Reply
#4
(05-23-2020, 12:19 PM)SteveW Wrote: I play with a 4-piece band and we are using JamKazam to rehearse during lockdown. We all live within 10 miles of each other and are all using wired ethernet connections. The other 3 band members experience very little latency between them, but I seem to have a much greater Internet latency and one that varies wildly from about 20ms to over 100ms. I use the same ISP as 2 of the other band members. 

I am using a Behringer UM2 interface and a MacBook running Catalina. My interface latency is 10ms, using a frame size of 2ms. This is not great but within usable limits.

I have tried leaving JamKazam and doing an internet speed test, using one of the publicly-available test sites. Having done this a few times, the results are always around 20Mb/s downstream, 1.8Mb/s upstream and a ping latency of around 15ms (to a server in London, at least 70 miles away). This looks as though my internet connection is OK.

Lowering my outgoing bitrate to 128kbit/s improves things a little, but not sufficiently.

Can anyone please suggest what I might do to diagnose or fix this problem--or is it simply that there is a poor internet service in my neighbourhood?

Any suggestions much appreciated.
-----

First observation is that your local audio interface latency is way too high. By tweaking the frame size to 1 msec (Audio Booster in JK client), buffer size and recording frequency (ASIO driver) you should be able to achieve less than 4 msec. Don't settle for any more, period.

Forget doing PING tests. they use a dedicated IP protocol (ICMP) and aren't representative of your Internet latency. Speed tests are also usually a waste of time unless you have very little of it.

It's all about total latency...

You can check latency to known sites on the Internet using the LATENCY option at TESTMY.NET.  Use that to try and find a time of day where the Internet traffic congestion is the lowest. Then schedule your group at that time if you can.

I've got a group in the same boat as you folks. We all live within the same community and still have varying amounts of latency. It's a killer. Another thing that can help is the use of a drum machine or having your real drummer play to a click track and ignore the latency effects he hears from the rest of the band. Everyone else can just play to that beat. Works ok even with siginficant latency.

Report back with your results...

Stuart.
  Reply
#5
Thanks for the reply, Stuart.

I have tried changing the frame size to 1ms but the audio just breaks up. 2ms is the lowest I can get with the Behringer interface. I am not using ASIO drivers as it is an Apple MacBook, so just using the default Apple drivers, which are not as highly tuned as the ASIO drivers would be (though I'm not sure the UM2 interface has got any specific ASIO drivers, anyway). I am currently using a sample rate of 44.1kHz, which was chosen because that's what other band members are using--I think there should be a speed advantage in all using the same sample rate. Maybe we could improve the latency a little by all using a higher rate. But I imagine that is going to shave off a few milliseconds, rather than cure the big problem of latency fluctuating from 20 to over 100ms.

Very good point about the ping tests. I had forgotten about ICMP.

I have tried Test.Net, as you suggest. This tells me my download speed is 16.5Mbit/s and upload 1.1Mbit/s. These are well below the quoted speeds of my ISP, so I think I am being short-changed by them at the moment. Will give them a call today.

We could give a click track a try. We have tried it in the past for other reasons and didn't get on very well with it, but I guess its a matter of practice and just getting used to it. Also we are using the lockdown to learn some new material, including building band arrangements of songs written by one of the band members, who is a prolific writer. Previously we found that the best results with a click track were when we knew the material very well and could really concentrate on the tightness of our performance. I think it would be least effective where we are trying out new ideas, improvising parts, trying different tempos, etc.

I am not sure my understanding of JamKazam is correct, but I am assuming that, if I set my outgoing bitrate to 256kbit/s, this is the rate for each audio channel, and that I have a separate audio channel for guitar and chat mic to each of the other participants in the session. (Is this correct?) If so, I would need an internet upstream bandwidth of 2 x 3 x 256 = 1536kbit/s. Add to this the overheads of TCP/IP and I am well over the capacity of my upstream connection. So, if this calculation is right, what I have seen as latency may just be the saturation of my internet connection. That would be consistent with what I have experienced: lowering my bitrate made an improvement and, in fact, the band's most successful practice was a day when, for reasons that remain a mystery, I could not get the instrument channel to work on JamKazam and ended up using the chat mic to pick up the guitar sound from from a combo amp, rather than having a dedicated guitar channel. So, on that occasion, I was only setting up a single mono channel to each of the band members.

Will report back after next session with the band.

Steve
  Reply
#6
(05-25-2020, 10:23 AM)SteveW Wrote: Thanks for the reply, Stuart.

I have tried changing the frame size to 1ms but the audio just breaks up. 2ms is the lowest I can get with the Behringer interface. I am not using ASIO drivers as it is an Apple MacBook, so just using the default Apple drivers, which are not as highly tuned as the ASIO drivers would be (though I'm not sure the UM2 interface has got any specific ASIO drivers, anyway). I am currently using a sample rate of 44.1kHz, which was chosen because that's what other band members are using--I think there should be a speed advantage in all using the same sample rate. Maybe we could improve the latency a little by all using a higher rate. But I imagine that is going to shave off a few milliseconds, rather than cure the big problem of latency fluctuating from 20 to over 100ms.

Very good point about the ping tests. I had forgotten about ICMP.

I have tried Test.Net, as you suggest. This tells me my download speed is 16.5Mbit/s and upload 1.1Mbit/s. These are well below the quoted speeds of my ISP, so I think I am being short-changed by them at the moment. Will give them a call today.

We could give a click track a try. We have tried it in the past for other reasons and didn't get on very well with it, but I guess its a matter of practice and just getting used to it. Also we are using the lockdown to learn some new material, including building band arrangements of songs written by one of the band members, who is a prolific writer. Previously we found that the best results with a click track were when we knew the material very well and could really concentrate on the tightness of our performance. I think it would be least effective where we are trying out new ideas, improvising parts, trying different tempos, etc.

I am not sure my understanding of JamKazam is correct, but I am assuming that, if I set my outgoing bitrate to 256kbit/s, this is the rate for each audio channel, and that I have a separate audio channel for guitar and chat mic to each of the other participants in the session. (Is this correct?) If so, I would need an internet upstream bandwidth of 2 x 3 x 256 = 1536kbit/s. Add to this the overheads of TCP/IP and I am well over the capacity of my upstream connection. So, if this calculation is right, what I have seen as latency may just be the saturation of my internet connection. That would be consistent with what I have experienced: lowering my bitrate made an improvement and, in fact, the band's most successful practice was a day when, for reasons that remain a mystery, I could not get the instrument channel to work on JamKazam and ended up using the chat mic to pick up the guitar sound from from a combo amp, rather than having a dedicated guitar channel. So, on that occasion, I was only setting up a single mono channel to each of the band members.

Will report back after next session with the band.

Steve

I think the outgoing but rate encompasses the sum total of all your audio inputs. But your 1.1mb uplink speed is marginal but workable I think. I forgot that you can't use ASIO on the Mac since it uses Core Audio. But if you can adjust the recording frequency you should play with that to get the lowest latency you can. You and your session partners don't have to use the same. Playing with a drum machine or click track is mandatory in our experience in this environment. It's also good musical practice even though most of us would never do it when we were all in a room playing together.

Stuart.
  Reply
#7
Steve, a friend who had a UM2 had to give up on it and bought a UMC202HD. That fixed his problems. If you can get hold of a different a/i, it might be worth a try.
  Reply
#8
Thanks Stuart and Doug for the replies.

I've spoken to my ISP (BT) who readily acknowledged that there was a problem with my internet speeds, have dispatched a new router, will be sending an engineer in the next few days (with instructions not to enter my house) and have given me a discount on my subscription. So I am happy with their response and think the next step is to wait for the results of these things and see what effect that has on my JamKazam sessions before trying anything else. For instance, I may well have to buy a new interface in the long term, (as Doug suggests) but will get the more general networking problems fixed first.
  Reply
#9
Just an update on this problem, in case others are interested. The engineer visit had to be delayed (I appreciate that these are difficult times) but he came earlier this week, checked all connections and replaced a card in the street cabinet. Since then my download speed has been around 37Mbit/s and upload 3.1Mbit/s. The engineer pointed out that the cable from the cabinet to my house uses aluminium conductors rather than copper. Although this was quite common 40 or 50 years ago when the cable was installed, it is not ideal for broadband. I also understand that the main band that is used for upload is at the high end of the frequencies sent along the wire. Hence, if the quality of the cable is poor, the upload speed is the first thing to suffer. So it looks like I am stuck with a 3Mbit/s, or so, upload speed until such time as I can get fibre to the home.

We had our next band practice last night and the latency was much better (consistently around 23ms total latency). So I think a lot of the apparent latency problem was really just a symptom of poor broadband upload speed. Nearly half the latency is now caused by the audio interface, so that is probably the next candidate for optimisation.

Cheers

Steve
  Reply
#10
If about half of latency is audio interface latency, then that means your audio interface latency is about 10 milliseconds.
Which again means that if you get the audio interface latency down to 2-4, then you will get really good connection.

About 15 milliseconds.
It must be considered excellent

I wrote earlier that the recommended upload was for a maximum of 8 participants in sessions.
But now it appears that JamKazam recommends a maximum of 7

Just for the sake of order
  Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)