Menu
Reply
chrisjohnoleary
  • 4
  • 0
  • 0
Tuning in
688 Views
Message 1 of 13
Flag for a moderator

Latency too high for real-time audio

Hi, Jon/Mod team. 

I am currently on Virgin 200Mb Broadband and trying to achieve a much lower ping for realtime audio jamming using https://jamulus.io/ many people are succesfully doing this over BT and other providers, however most on virgin are having problems and i'm contemplating leaving, I'd rather stick with VM as I've been with you for the past 18 years, so please let me know if there is something you can do to help reduce it?

I am currently hardwired in to the superhub 3 with a 2m long cat 7 ethernet cable, running windows 10 on the latest release, fully updated. Tried with antivirus on and off, tried with all other apps shut down. I had been monitoring my results on https://www.thinkbroadband.com/ 

Can you help?

0 Kudos
Reply
conman33158
  • 1.56K
  • 131
  • 295
Super solver
642 Views
Message 2 of 13
Flag for a moderator

Re: Latency too high for real-time audio

Can you please upload your router stats and set up a BQM

Type 192.168.0.1 or (192.168.100.1 if you have your Hub in Modem mode) into your address bar at the top of your browser

DO NOT LOG IN, just click “Check Router Status” at the bottom of the page. Sometimes the “Check Router Status” is missing, in this case just go ahead and log in and go to Advanced Settings-> Tools-> Network Status.

Please copy and paste the contents of the Downstream, Upstream, Configuration and Network Log tabs, if you get a yellow warning just click the Post button again.

You can use more than one post for each item if needed!

If you get a warning when you hit “Post” just hit “Post” again and it should work ok!

Please do not use screenshots

Also can you please setup a Broadband Quality Monitor (BQM) at thinkbroadband.com. Just click on Create a new monitor.

Under your graph you just created Click (Share Live Graph)

Copy the text in the “Direct Link” box and paste it on here

***********************************************************************************************************************************
Super Hub 4.0 (modem mode) - Gig1 Fibre FTTP - Asus RT-AX82U & Asus RT-AX56U with AiMesh setup
***********************************************************************************************************************************
My Broadband Ping - conman33158
0 Kudos
Reply
mjpartyboy
  • 375
  • 21
  • 53
Fibre optic
628 Views
Message 3 of 13
Flag for a moderator

Re: Latency too high for real-time audio

Latency is out of your control. The current DOCSIS infrastructure VM use inherently has higher latency than other types of broadband technology.
SH2 modem mode | AC86U router | AC68U node
0 Kudos
Reply
Serena_C
  • 1.33K
  • 54
  • 143
Forum Team
Forum Team
554 Views
Message 4 of 13
Flag for a moderator

Re: Latency too high for real-time audio

Hi Chris,

 

Welcome to the Community Hub Forums 🙂 Thank you for your post regarding the high latency issues which are preventing you from jamming. I understand how frustrating this must be.

 

I've taken a look at your account and there are no issues showing in regard to your connection. How are things working for you now when you try to jam - are you still experiencing high latency issues?

 

Serena

0 Kudos
Reply
chrisjohnoleary
  • 4
  • 0
  • 0
Tuning in
534 Views
Message 5 of 13
Flag for a moderator

Re: Latency too high for real-time audio

https://www.thinkbroadband.com/broadband/monitoring/quality/share/d4445f39c2bd9f4a92fc595bf6448449d52bc62d

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)
475000000
Locked
Ranged Upstream Channel (Hz)
39400000
Locked
Provisioning State
Online

 

 
Downstream bonded channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
14750000006.540256 qam9
2483000000740256 qam10
3491000000740256 qam11
44990000007.540256 qam12
55070000007.340256 qam13
65150000007.940256 qam14
75230000007.140256 qam15
85310000007.940256 qam16
95390000007.440256 qam17
10547000000840256 qam18
115550000007.840256 qam19
125630000007.840256 qam20
135710000007.540256 qam21
14579000000740256 qam22
155870000007.840256 qam23
16595000000840256 qam24
176030000008.540256 qam25
186110000007.640256 qam26
19619000000840256 qam27
206270000007.540256 qam28
216350000008.538256 qam29
226430000008.340256 qam30
236510000008.540256 qam31
24659000000840256 qam32
0 Kudos
Reply
chrisjohnoleary
  • 4
  • 0
  • 0
Tuning in
532 Views
Message 6 of 13
Flag for a moderator

Re: Latency too high for real-time audio

 

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked40.3100
2Locked40.9220
3Locked40.370
4Locked40.3110
5Locked40.310
6Locked40.9100
7Locked40.300
8Locked40.390
9Locked40.350
10Locked40.340
11Locked40.3180
12Locked40.950
13Locked40.9420
14Locked40.330
15Locked40.9160
16Locked40.360
17Locked40.900
18Locked40.300
19Locked40.960
20Locked40.320
21Locked38.900
22Locked40.3180
23Locked40.3130
24Locked40.3360

 

 
Upstream bonded channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
13940000043512064 qam4
25369996643.8512064 qam2
34620000043.3512064 qam3
43260000043.3512064 qam5


Upstream bonded channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

General Configuration
Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
cmreg-vmdg505-bbt060-b.cm


Primary Downstream Service Flow
SFID153668
Max Traffic Rate230000061
Max Traffic Burst42600
Min Traffic Rate0


Primary Upstream Service Flow
SFID153667
Max Traffic Rate22000061
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort

 

 

 
Network LogTime Priority Description
15/04/2021 20:13:46noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/04/2021 08:10:15ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/04/2021 07:42:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/04/2021 10:58:1criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/04/2021 19:42:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/04/2021 02:12:38criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/04/2021 07:42:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/03/2021 06:38:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/03/2021 19:42:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/03/2021 03:12:45criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/03/2021 07:42:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/03/2021 20:12:2noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/03/2021 19:42:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/03/2021 04:54:46criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/03/2021 07:42:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2021 05:21:46criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2021 03:55:49ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/03/2021 04:22:51criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/03/2021 22:29:36ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

PING 8.8.8.8 (8.8.8.8): 64 data bytes
72 bytes from 8.8.8.8: seq=0 ttl=117 time=20.000 ms
72 bytes from 8.8.8.8: seq=1 ttl=117 time=10.000 ms
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 2 packets received, 33% packet loss
round-trip min/avg/max = 10.000/15.000/20.000 ms

0 Kudos
Reply
Molly_G
  • 1.15K
  • 53
  • 135
Forum Team (Retired)
Forum Team (Retired)
397 Views
Message 7 of 13
Flag for a moderator

Re: Latency too high for real-time audio

Hi @chrisjohnoleary,

 

Thanks for posting your stats. How is your BQM looking since you have set this up?

 

Thanks,

Molly_G
Forum Team



New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply
chrisjohnoleary
  • 4
  • 0
  • 0
Tuning in
381 Views
Message 8 of 13
Flag for a moderator

Re: Latency too high for real-time audio

Chris BQM <- link here. 

not good enough with too much jitter, spikes and unpredictability 😒

0 Kudos
Reply
Roger_Gooner
  • 7.14K
  • 500
  • 1.31K
Legend
371 Views
Message 9 of 13
Flag for a moderator

Re: Latency too high for real-time audio

When I ping 8.8.8.8 I get average round trip times of 13ms, best is 12ms and worst is 19ms.

--
Hub 3.0, TP-Link Archer C8, TP-Link TL-SG108S 8-port gigabit switch, V6
My Broadband Ping - Roger's VM Broadband Connection
0 Kudos
Reply
conman33158
  • 1.56K
  • 131
  • 295
Super solver
363 Views
Message 10 of 13
Flag for a moderator

Re: Latency too high for real-time audio


@chrisjohnoleary wrote:

Chris BQM <- link here. 

not good enough with too much jitter, spikes and unpredictability 😒


Your BQM is really good as is you router stats. You're never going to get better than that with DOCSIS 🙂

***********************************************************************************************************************************
Super Hub 4.0 (modem mode) - Gig1 Fibre FTTP - Asus RT-AX82U & Asus RT-AX56U with AiMesh setup
***********************************************************************************************************************************
My Broadband Ping - conman33158
0 Kudos
Reply