oracle57
Dialled in
Joined 15 years ago
User Profile
User Widgets
Contributions
Re: Pixelation on Portrait Artist of the Year on Sky Arts
So far all this weeks recordings I have done of Portrait Artist of the Year, on various Sky channels and at various time, have all recorded without a glitch. I was waiting until the last one records tonight before making any posts. Just for clarification we have had Virgin Media (NTL) for a very long time. There is nothing electrical on or charging in the vicinity of the V6 box and all other equipment (TV, DVD etc.) are switched off overnight. It was only this one program that exhibited the pixelation, and only the 02:00 broadcast of it, hence not raising a stand alone discussion. We have other recordings done at a similar time that view with no trouble. One, therefore, must assume that we are actually recording the source that is pixelated, and the source is being corrupted up the line somewhere Yes we could record the show at a different time, but the V6 box chose that time as part of a Series Record, we did watch the episodes on demand. But that does not get away from the fact that there was an issue somewhere that corrupted the signal. Hence reporting, not the ‘natural "me too" instinct’ to complain as implied..82Views0likes0CommentsPixelation on Portrait Artist of the Year on Sky Arts
We have exactly the same, and it seems a few others are also experiencing this issue... Pixelation on Portrait Artist of the Year on Sky Arts from recording @ 01:59. Only on recording and only Portrait Artist of the Year. All other recordings are OK. Have had to watch it on catch-up instead.Solved241Views0likes7CommentsRe: Pixelation on Portrait Artist of the Year on Sky Arts
Firstly I did not raise this as a stand alone discussion, it was part of another discussion regarding the same issue. It was a comment on another post and was intended to aid any investigation. 1 occurrence could be the V6 box, 2 independent occurrences becomes a bit less likely, above this (as in this case) might show a route cause of the issue. As stated our experience is that is is only occurring on this recording. Live works (at the moment) as does all other recordings and pausing. We have not tried it @01:59 for obvious reasons. That's why we are recording it! The pixilation starts about 30 minutes in, so would make it about 02:30 at recording time. This has only started within the last 2-3 weeks.148Views0likes0CommentsRe: Intermittent Signal in Area with errors indicated in logs
UPDATE AND HOPEFUL FIX: An engineer came out a week ago and after laughing at the 10-15 year old connectors, splitters and cables he proceeded to change everything. Outside connector from the road to the house was renewed as it was “just a little corroded”. I hoped that this would solve the issue, and it did to an extent. The next morning had a few T3 errors showing but a lot better than the previous month. Then at midday the whole street went off. Service Status showed VM were aware and in attendance. No-one in the street saw or heard from VM, but I did see a VM van with flashing lights parked 3 roads away. After some time the red lights on the router stopped and the system became usable again. No update was forthcoming from VM. Since this outage, and I assume a VM fix of some sort, I have had a clear Network Errors page with just the Pre-RS errors slowly creeping up. No network interruptions or slow connection speed. Not sure as to which part fixed the issue, but at least I have a working connection... for now.39Views0likes0CommentsRe: Intermittent Signal in Area with errors indicated in logs
3.0 Upstream channels Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 0 49600000 43 5120 QAM 64 5 1 43100000 43 5120 QAM 64 6 2 36600000 43.8 5120 QAM 64 7 3 30100000 44.5 5120 QAM 64 8 4 23600000 44.3 5120 QAM 64 11 3.0 Upstream channels Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 0 ATDMA 0 4 28 0 1 ATDMA 0 4 10 0 2 ATDMA 0 4 10 0 3 ATDMA 0 4 25 0 4 ATDMA 0 4 8 0 3.1 Upstream channels Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation 12 10.4 38.5 2K QAM 256 3.1 Upstream channels1View0likes0CommentsRe: Intermittent Signal in Area with errors indicated in logs
3.0 Downstream channels Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 1 467000000 10.1 41 QAM 256 8 2 427000000 10.2 41 QAM 256 3 3 435000000 10.1 41 QAM 256 4 4 443000000 10 41 QAM 256 5 5 451000000 10 41 QAM 256 6 6 459000000 10 41 QAM 256 7 7 475000000 10.1 41 QAM 256 9 8 483000000 9.7 41 QAM 256 10 9 491000000 9.2 41 QAM 256 11 10 499000000 8.8 41 QAM 256 12 11 507000000 8.5 41 QAM 256 13 12 515000000 8.6 41 QAM 256 14 13 523000000 8.6 41 QAM 256 15 14 531000000 8.7 41 QAM 256 16 15 539000000 8.6 41 QAM 256 17 16 547000000 8.3 41 QAM 256 18 17 555000000 7.9 41 QAM 256 19 18 563000000 7.4 40 QAM 256 20 19 571000000 7.1 40 QAM 256 21 20 579000000 7.1 40 QAM 256 22 21 587000000 7.1 40 QAM 256 23 22 595000000 6.9 40 QAM 256 24 23 603000000 6.6 40 QAM 256 25 24 611000000 6.3 40 QAM 256 26 25 619000000 6.1 40 QAM 256 27 26 627000000 6.1 40 QAM 256 28 27 635000000 6.1 40 QAM 256 29 28 643000000 6.2 40 QAM 256 30 29 651000000 6.4 40 QAM 256 31 30 659000000 6.7 40 QAM 256 32 31 667000000 7.3 40 QAM 256 33 3.0 Downstream channels Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors 1 Locked 41 12002 3476 2 Locked 41 33 19 3 Locked 41 33 18 4 Locked 41 10 14 5 Locked 41 15 1976 6 Locked 41 3 0 7 Locked 41 13 964 8 Locked 41 2 0 9 Locked 41 6 20 10 Locked 41 7 977 11 Locked 41 7 985 12 Locked 41 17 966 13 Locked 41 8 21 14 Locked 41 5 21 15 Locked 41 76 912 16 Locked 41 10 13 17 Locked 41 9 25 18 Locked 40 54 945 19 Locked 40 44 942 20 Locked 40 16 15 21 Locked 40 12 13 22 Locked 40 16 26 23 Locked 40 17 14 24 Locked 40 26 34 25 Locked 40 30 59 26 Locked 40 36 80 27 Locked 40 34 23 28 Locked 40 28 36 29 Locked 40 24 33 30 Locked 40 25 71 31 Locked 40 18 70 3.1 Downstream channels Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz) 41 94 4K 1840 QAM 4096 1108 3.1 Downstream channels Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile) 41 Locked 39 4.9 1568670166 193740Views0likes0CommentsRe: Intermittent Signal in Area with errors indicated in logs
This still seems to be a problem - Network Log Time Priority Description 09-10-2025 08:49:19 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:49:13 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:49:13 critical 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:48:55 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:48:52 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:48:52 critical 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:47:16 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:46:59 warning TCS Partial Service;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:46:42 critical No Ranging Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:46:42 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:46:40 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:46:39 critical No Ranging Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:46:38 critical No Ranging Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:46:38 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:46:31 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:46:23 critical No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:46:21 critical No Ranging Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:46:20 critical No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:46:18 critical No Ranging Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:46:16 critical No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:46:03 critical No Ranging Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:45:59 warning MDD message timeout;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:45:50 critical No Ranging Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:45:49 warning MDD message timeout;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:45:45 critical No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:45:28 critical No Ranging Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:45:27 warning MDD message timeout;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:45:27 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:45:26 warning RCS Partial Service;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:45:21 critical No Ranging Response received - T3 time-out;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:45:17 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 09-10-2025 08:45:16 warning MDD message timeout;CM-MAC=00:;CMTS-MAC=00:CM-QOS=1.1;CM-VER=3.1; 08-10-2025 15:40:36 notice GUI Login Status - Login Success from LAN interface0Views0likes0CommentsRe: Intermittent Signal in Area with errors indicated in logs
I have now done the requested Factory Reset to the V5 router. It has sort of worked, I think! Reset went ok and I configured everything. I finished and did a final Service Status check to be told that Last updated today, 04:24 pm. Intermittent signal in your area We’re looking into it. Check back here after 24 hours, and if there’s still an issue we’ll help you book an engineer. At least it wasn't Unable to Connect message, but once again I am slightly unclear if there is a fault with the cabling to our house - not the equipment inside. There has been a lot of work being carried out over the past few months with adjacent BT cabling. Virgin Media were at the road cabinet on the 19th and 22nd of this month to fix issues.14Views0likes0CommentsRe: Intermittent Signal in Area with errors indicated in logs
Hi, There was an area issue and this was apparently being fixed on the 22 September. Since then I have received a number of SMS texts stating there is an intermittent issue with my line and 2 asking me to book an engineer - the links of which does not work. I have also contacted, on-line, the support desk, of which they could not answer where these text came from. As stated the last 48 hours have been stable so I am now surprised with what you are seeing. I will Factory Reset as requested just in case this helps...9Views0likes0CommentsRe: Intermittent Signal in Area with errors indicated in logs
Well it's been 48 hours since reporting this on here and as luck would have it I have had no errors. So 3 weeks of box rebooting by itself at random times daily, thousands of Pre/Post RS errors and network logs filling up with Sync errors to relative stability with a constant speed. Service Status still getting the message We can’t connect to the broadband kit in your home (even after reboot so must be an issue somewhere as never had this before). Afraid now to do anything as at least I have some sort of service!149Views0likes0Comments