Choose your cart
Choose your cart
Solved! Go to Solution.
UPDATE:
I am glad to say that this issue seems to have been resolved for me. When this issue first arose I checked the forums and saw that Verizon apparently did not have any solutions for this other than switch to component cables. I did that and the problem did not go away, it was a little better, but I still experienced video dropouts.
I finally called Verizon tech support about 2 weeks ago (I didn't update this sooner, because I wanted to make sure the issue was in fact resolved before I did), and spoke with someone who I honestly did not trust and he new it. I begrudgingly did as he asked, and questioned his methods every step of the way, but I will admit that he was correct and knew what he was doing.
He explained to me that there is a problem with the receiver communicating with the modem/router (this is where I started to question his abilities and knowledge). He wanted me to reset the modem/router, which I did, only after I reminded him that he should tell all people that do this in the future that this will remove all security from your router and reset it back to OTB "Out of the box" settings. After I reset it, he ran some tests, made a couple of changes (not sure what), then he reset my DVR from his desk. After it was reset, I had to run a test on the DVR unit to get reply times for him. He then said that it should be resolved. I got off the phone with him, quite skeptical that anything was resolved.
Over the last 2 weeks though, I have had my DVR hooked up to my LCD via HDMI cable, the same one that wasn't working before, and I have not had ANY dropped video signals at al since then. I am glad that I finally called and spoke to someone who knew what they were talking about. I'm not sure if this is the solution for everyone with the same issue, but it is worth giving them a call and asking.
‎06-20-2009 06:32 PM - edited ‎06-20-2009 06:39 PM
The first posts to this thread describe known HDMI interoperability issues between the QIP7216 and many displays.
The solution is (a) use component, or (b) swap the QIP7216 for a QIP6416 which doesn't exhibit the problem.
Edit: Verizon plans to improve the QIP7216's HDMI compatibility with an update by the end of August.
"The solution is (a) use component, or (b) swap the QIP7216 for a QIP6416 which doesn't exhibit the problem"
Great solution, Go back to component when we all spend alot of $$ to use HDMI and the latest technology. I guess being a techie has its drawbacks. Does the QIP6416 even have HDMI hookup or is that only component? Now that Direct is advertising 1080p direct to the TV how long will it take Comcast and Verizon to finally upgrade the boxes to actually work correctly. {please keep it relevant}
@Massman wrote:"The solution is (a) use component, or (b) swap the QIP7216 for a QIP6416 which doesn't exhibit the problem"
Great solution, Go back to component when we all spend alot of $$ to use HDMI and the latest technology. I guess being a techie has its drawbacks. Does the QIP6416 even have HDMI hookup or is that only component? Now that Direct is advertising 1080p direct to the TV how long will it take Comcast and Verizon to finally upgrade the boxes to actually work correctly. {please keep it relevant}
http://en.wikipedia.org/wiki/1080p [edit] Broadcasting standardsIn the United States, ATSC support 1080p video, but only at the frame rates of 24, 25, and 30 frames per second (1080p24, 1080p25, 1080p30). The ATSC is considering amending its standard to allow the incorporation of the newer codecs for optional usage as the DVB Project consortium already has done with DVB-S2.[6] However, doing so is not expected to result in widespread availability of 1080p60 programming, since most of the existing digital receivers in use would only be capable of decoding the older, less-efficient MPEG-2 codec, and bandwidth limitations do not allow for broadcasting two simultaneous streams on the same broadcast channel (e.g. both a 1080i MPEG-2 stream alongside a 1080p MPEG-4 stream).
In Europe, 1080p25 signals have been supported by the DVB suite of broadcasting standards; higher frame rates, such as 1080p50 and 1080p60, have been foreseen as the future broadcasting standard, [4] though they require more bandwidth and/or advanced codec such as H.264/MPEG-4 AVC. Starting Fall 2009, ETSI and EBU, the maintainers of DVB, will require that DVB-compatible digital receivers feature support for 1080p signals at 50/60 Hz and MPEG-4 AVC High Profile Level 4.2 with Scalable Video Coding extensions. [7] [8] SVC enables forward compatibility with 1080p50 broadcasting for older MPEG-4 AVC receivers, so they will only recognize baseline SVC stream coded at a lower resolution/frame rate and gracefully ignore additional frames, while newer hardware will be able to decode full-resolution 1080p50 signal. EBU recommends that legacy hardware should at least not crash in presence of SVC or 1080p50 (and higher resolution) signals.[7]
your 1080p that your referring to is vod. its important to me that your exact in your statements.
the 6416 has problems with hdmi just like the 7216.....
@Tektronic wrote:your 1080p that your referring to is vod. its important to me that your exact in your statements.
the 6416 has problems with hdmi just like the 7216.....
The interoperability issues are not comparable between the two. The 7216 might exhibit HDMI compatibility issues with 50-70% of TVs, whereas the 6416 might exhibit HDMI compatibility issues with 10% of TVs. In the latter case, the fault is just as likely to be with the TV as it is with the 6416; some older (and newer low-cost) TVs were rushed to market and skimped on their HDMI compatibility testing. Samsung in particular was known for this.
As noted above, Verizon does plan an update before the end of the summer that will improve HDMI compatibility on the QIP7216. For now, you either need to use component, or switch to the QIP6416 for HDMI. Or buy a TivoHD / Moxi.