on 09-03-2023 19:26
Hello,
I used to be able to Stream on Twitch with next to no frame drops on 6000kbps bitrate, however, since the 2nd March 2023 I now have over 65% dropped frames making my Stream Lag (kb/s is constantly bouncing up and down instead of being steady) with spikes & disconnects which is no good for viewers watching.
I had Virgin Media Gig1 Fibre Broadband installed back on the 14th Jan 2023 & enjoyed a stable Upload Speed between 50 - 52 Mbps. Now since 2nd March 2023, my speedtests show varying results each day between 24 - 39 Mbps.
My Connection / Upload speed feels inconsistent as my ping rises & lowers during gameplay.
It seems like there is noise or some interference occuring as the results are sporadic & often dip the longer a speed test goes on for, whereas before it would sit around 52Mbps solidly. The Download Speed seems unaffected but the Upload Speed is painfully different.
This is what I do for a living so it's affecting me greatly & I would like help solving this issue.
I have tried
-Restarting Router
-Changing Ethernet Cables
-Streaming using different Servers (London/France/Amsterdam)
-Streaming on another PC in House (To try to confirm that it's not a Hardware/Software/Network Card Issue)
-Streaming Downscale to 720p
-Streaming at 30fps
-If I stream at 3k Bitrate I have around 2-5% dropped frames but I still suffer infrequent spikes & disconnects.
This never used to happen so something has changed.
on 10-03-2023 09:53
Just a few thoughts before someone with more experience with streaming comes along.
You can check whether your suspicion of noise is correct by posting the upstream and downstream data from the Hub.
You can check how busy your local network is by setting up a free BQM and posting a live link here. It will look terrible while you are streaming, but between those times you can see what you are sharing with.
https://www.thinkbroadband.com/broadband/monitoring/quality
Ultimately if this is for your living you may need a more appropriate broadband connection than Virginmedia which is not intended or supported for that sort of use.
on 11-03-2023 13:49
Hi jpeg1,
Thanks for your helpful response.
I have set up a BQM over the past 24 hours (See below for results)
Here are the statistics for the upstream & downstream data from the Hub.
Hopefully someone can understand this & help resolve this issue.
Downstream bonded channels
1 | 179000000 | 2.2 | 36 | QAM 256 | 6 |
2 | 139000000 | 2.9 | 36 | QAM 256 | 1 |
3 | 147000000 | 2.6 | 36 | QAM 256 | 2 |
4 | 155000000 | 2.3 | 36 | QAM 256 | 3 |
5 | 163000000 | 2.1 | 36 | QAM 256 | 4 |
6 | 171000000 | 2 | 36 | QAM 256 | 5 |
7 | 187000000 | 2.5 | 36 | QAM 256 | 7 |
8 | 195000000 | 3 | 36 | QAM 256 | 8 |
9 | 203000000 | 3.3 | 36 | QAM 256 | 9 |
10 | 211000000 | 3.8 | 37 | QAM 256 | 10 |
11 | 219000000 | 3.8 | 37 | QAM 256 | 11 |
12 | 227000000 | 3.9 | 36 | QAM 256 | 12 |
13 | 235000000 | 3.9 | 37 | QAM 256 | 13 |
14 | 243000000 | 3.9 | 36 | QAM 256 | 14 |
15 | 251000000 | 3.7 | 37 | QAM 256 | 15 |
16 | 259000000 | 3.6 | 37 | QAM 256 | 16 |
17 | 267000000 | 3.4 | 37 | QAM 256 | 17 |
18 | 275000000 | 3.3 | 36 | QAM 256 | 18 |
19 | 283000000 | 3.2 | 37 | QAM 256 | 19 |
20 | 291000000 | 3.2 | 36 | QAM 256 | 20 |
21 | 299000000 | 3 | 37 | QAM 256 | 21 |
22 | 307000000 | 2.9 | 37 | QAM 256 | 22 |
23 | 315000000 | 2.9 | 37 | QAM 256 | 23 |
24 | 323000000 | 2.8 | 37 | QAM 256 | 24 |
25 | 331000000 | 2.5 | 36 | QAM 256 | 25 |
26 | 339000000 | 2.3 | 36 | QAM 256 | 26 |
27 | 347000000 | 2.3 | 36 | QAM 256 | 27 |
28 | 355000000 | 2.3 | 36 | QAM 256 | 28 |
29 | 363000000 | 2.4 | 36 | QAM 256 | 29 |
30 | 371000000 | 2.5 | 37 | QAM 256 | 30 |
31 | 379000000 | 2.7 | 37 | QAM 256 | 31 |
Downstream bonded channels
1 | Locked | 36 | 14 | 0 |
2 | Locked | 36 | 1 | 0 |
3 | Locked | 36 | 14 | 0 |
4 | Locked | 36 | 5 | 0 |
5 | Locked | 36 | 14 | 0 |
6 | Locked | 36 | 1 | 0 |
7 | Locked | 36 | 2 | 0 |
8 | Locked | 36 | 0 | 0 |
9 | Locked | 36 | 3 | 0 |
10 | Locked | 37 | 1 | 0 |
11 | Locked | 37 | 1 | 0 |
12 | Locked | 36 | 16 | 0 |
13 | Locked | 37 | 1 | 0 |
14 | Locked | 36 | 16 | 10 |
15 | Locked | 37 | 0 | 0 |
16 | Locked | 37 | 25 | 2 |
17 | Locked | 37 | 1 | 0 |
18 | Locked | 36 | 2 | 0 |
19 | Locked | 37 | 1 | 0 |
20 | Locked | 36 | 1 | 0 |
21 | Locked | 37 | 0 | 0 |
22 | Locked | 37 | 1 | 0 |
23 | Locked | 37 | 1 | 0 |
24 | Locked | 37 | 3 | 0 |
25 | Locked | 36 | 4 | 0 |
26 | Locked | 36 | 9 | 0 |
27 | Locked | 36 | 4 | 0 |
28 | Locked | 36 | 10 | 0 |
29 | Locked | 36 | 15 | 0 |
30 | Locked | 37 | 20 | 0 |
31 | Locked | 37 | 12 | 0 |
Upstream bonded channels
0 | 60300000 | 34.8 | 5120 | QAM 64 | 1 |
1 | 53700000 | 34.8 | 5120 | QAM 64 | 2 |
2 | 46200000 | 34.8 | 5120 | QAM 64 | 3 |
3 | 39400000 | 34.8 | 5120 | QAM 64 | 4 |
4 | 32600000 | 35 | 5120 | QAM 64 | 5 |
5 | 23600000 | 35.5 | 5120 | QAM 64 | 6 |
Upstream bonded channels
0 | ATDMA | 0 | 0 | 1 | 0 |
1 | ATDMA | 0 | 0 | 0 | 2 |
2 | ATDMA | 0 | 0 | 14 | 0 |
3 | ATDMA | 0 | 0 | 25 | 1 |
4 | ATDMA | 0 | 0 | 54 | 1 |
5 | ATDMA | 0 | 0 | 81 | 1 |
Network Log
10-03-2023 12:07:38 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
10-03-2023 11:08:03 | warning | Dynamic Range Window violation |
10-03-2023 11:08:03 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
10-03-2023 11:03:44 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
10-03-2023 11:03:44 | warning | Dynamic Range Window violation |
10-03-2023 08:16:40 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
10-03-2023 07:38:38 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
10-03-2023 01:13:00 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
10-03-2023 00:59:07 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
10-03-2023 00:50:09 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-03-2023 23:16:17 | warning | Dynamic Range Window violation |
09-03-2023 23:16:17 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-03-2023 22:50:20 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 5;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-03-2023 22:50:20 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-03-2023 22:44:08 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-03-2023 22:44:05 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-03-2023 22:10:11 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-03-2023 22:10:11 | warning | Dynamic Range Window violation |
09-03-2023 22:00:52 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-03-2023 22:00:52 | warning | Dynamic Range Window violation |
09-03-2023 21:02:58 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-03-2023 20:17:02 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-03-2023 20:17:02 | warning | Dynamic Range Window violation |
09-03-2023 19:20:48 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-03-2023 16:37:23 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-03-2023 16:37:23 | warning | Dynamic Range Window violation |
09-03-2023 07:57:53 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-03-2023 07:50:01 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-03-2023 03:55:03 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-03-2023 20:23:47 | warning | Dynamic Range Window violation |
08-03-2023 20:23:46 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-03-2023 04:17:20 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 13-03-2023 15:40
Hi @Racer,
Thank you for your posts and welcome to our community forums. We're here to help.
I'm very sorry to hear that you appear to be facing some connection quality issues recently. Are these ongoing today? If they are, are you able to provide a link to your live BQM? That way we can see the connection quality in real-time.
Thanks,
on 13-03-2023 16:29
on 13-03-2023 17:45
All those T3 errors show something seriously wrong.
on 13-03-2023 19:04
Check for a local fault on : 0800 561 0061
The reason for saying this is this connection has six "QAM 64" "DOCSIS 3.0" channels connected that equates to ( 6 x 27Mb/s ) = 162Mb/s of upstream for the Hub to use for upstream transmission.
Yet there are speed test shared in the thread showing repeated runs having failed to exceed 12Mb/s on the upstream.
13-03-2023 21:11 - edited 13-03-2023 21:12
What I find different about this case vs others is you can get equal T# across all channels but in this case they are failing unequal.
on 13-03-2023 21:57
Yes. In a slope inversely proportional to frequency.
on 13-03-2023 23:16
@jpeg1 wrote:Yes. In a slope inversely proportional to frequency.
Yep, because I'm sure you are aware of the relationship between attenuation against frequency on a cable of fixed properties!