US Cable Support > OptimumOnline > [iO] HBO Ondemand Breakup

reply to Oceanside426

Re: [iO] HBO Ondemand Breakup

Ok thanks for that info. I also would like to hear from people who are closer to where I live so I can get a better Idea.

Did the problem begin two weeks ago tonight (on Wednesday, December 5)? I'll bet it did.

They changed the data for both SD and HD that evening, and it has caused a lot of pixleation problems on different stations and on combinations of stations if one is being recorded and another, carried on the same frequency, is being watched.

They are supposedly working on patches for the problems, but I haven't seen any improvement on the issues I have noted and complained about.

They clearly need to do a better job of testing software before they send it out.

i'm not quite sure but it could be I just recently noticed this problem and never have I had any problems in the past with HBO ondemand but I do know as you pointed out that they are working a lot on backend stuff recently to be ready for the deployment of the new guide especially in areas like ours that only have the samsung boxes with the new guide deployed and not the SA boxes. I also agree with you that they need better handling of new software so there customers do not become test subjects. I posted pictures of my diagnostic screens for two different boxes running off two separate drops that are both experiencing the problem. I am not experienced with reading the diagnostics of these boxes so I was hoping that someone here could give me some insight on to if there seems to be a problem with these results. Thanks.

I'm far from an expert on video but on the diag. screens for the 741 MHz Frequency show 0 errors both Corrected and Uncorrected. That combined with the fact that it is only HBO on demand that is having a problem would lead me to believe it is a headend problem, not a transmission or noise problem.
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore.

I am in agreement with you. I really think its something at the head end. I just don't know if cablevision will put any effort into fixing this. So based on these diagnostic results things look good on my end ??

If the problem is easily reproducable (as in, takes just a few minutes to see), a field tech would actually be a good idea. They would be able to see the error happen, and if they clear everything at the house, they can escalate accordingly.

I thought about that the problem is it takes 30-40 minutes sometimes longer before the problem shows and it happens for just a few seconds also if it is a short program like a half hour program you may not even see the problem. It is almost like an internet video breaking up for a few seconds to buffer.

You can press B on remote while on diagnostic so you can make it see through. Idk if you know. I believe its page 5 on 4250 box or page 4 on 8300 where you can see corrected and uncorrected errors on whatever channel frequency yur on. True if you dont have any errors that its probly headend problem . Sometimes can be box issue but usually you will have very high error count with bad box. Also sometimes if the card is burnt where it goes into box that can cause pixilation.

You are correct that on page 5 of my 4250's it shows the corrected and on uncorrected. My question is it normal to have some corrected bytes or should you have 0 corrected bytes and 0 uncorrected bytes? Because I notice even cable modems get corrected bytes. Thanks.

Downstream Correctables and Uncorrectables are caused by noise on the downstream channel. Docsis contains an error correction mechanism (FEC) to correct octets when corruption is not too great. Having some Uncorrectables/Correctables are OK but you want a very low percentage.

See my post in the link below for some links to articles that give a more in depth discussion of Correctables and Uncorrectables.

»Re: How do my Signals Look?
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore.

I just played an HD hour long Boardwalk Empire episode on one of my boxes and my corrected Bytes were 115 with 0 uncorrected Bytes and now on my second box playing another HD Hour Long Boardwalk Empire episode they were 19 corrected bytes and 0 uncorrected bytes.. this box did have lower corrected bytes however the problem still happened. I still don't think these number of corrected bytes should cause problems.

Do these number of corrected bytes cause problems? What do you guys think?

I'm sure you had tens of thousands of correctly sent bytes, where that small amount would not really indicate a problem. Averaging one every 2-3 minutes isn't bad.

Thanks.. I wonder if it has something to do with a frequency I am noticing that at my cousins house when he plays HBO on-demands with out breakup on the scientific atlanta's the frequency is 597 while at my house the frequency is 741.. could hardware such as a splitter cause a certain frequency to malfunction.. its just that I don't think this is the case because I have two drop wires and all my boxes are split between two different splitters with all direct runs and these splitter are only a few months old. It just seems unlikely to me that they went bad at the same time having the same problem. I hope it isn't the splitters because I have all my wires organized in a outside wire box and I don't want to reorganize them again =(

I had a tech come today. The tech told me something interesting he said that the tap was energized meaning there is an electrical interference from some live wire or something like that. I hope that once they find out whats going on with this that could clear up this random breakup. Because the breakup is now even starting to occur on other services such as DVR Plus and other on-demands. I did see that when the tech was on the poll outside my house he took a red meter and the meter started making noise when he placed it near the tap and thats when he said there is some type of electrical interference. Has anyone ever heard of this problem before??