I have been monitoring this issue for some time now. I was also disappointed when I brought home my Denon 2807 and got the "no repeaters allowed message", but that has all changed today. The HDMI port took a dump last week on my DCT6412 and I just picked up a new one today and it has firmware 16.20 (Comcast - Little Rock, AR). The HDMI port works again, but then I tried hooking it up directly to the receiver and lo and behold, it was a complete success! I can't believe that Comcast has actually come through on this issue. I hope everyone else has the same results with their respective providers and that mine actually lasts. I'm sure when Comcast updates the box to put ads into the menu that it will kill the HDMI again, but I'll be a somewhat satisfied customer from now until then.

Has anybody got a firmware update in south Texas (Suddenlink customers))

I'm in College Station and trying to find someone here that even knows what firmware is. Going back up the office shortly to see if I can locate some "rank" that knows anything about a roll out date. I'm on 12.31 and switching on my Onkyo 804 is useless with the Moto 6416 like everyone else previously..

Will post if I get any info from Suddenlink.

Spoke to someone at Time Warner where TW recently took over from Comcast in Richardson, TX. Very pleasant, helpful young woman who didn't really understand and checked with a co-worker. Their conclusion was that this was a more technical conversation than they could understand or handle. Fair enough. Their next step is to send a tech who should be able to understand the problem.

Of course the tech won't be able to do anything here, but maybe he will be able to deal with someone up the line. Tech is scheduled for midday Friday. I'll share results.

Let me know if you find anything out

I'm in Omaha, NE and have COX cable. I have a Moto DCT6416 III and an Onkyo 604 with HDMI switching. Like others when I tried using HDMI with the Onkyo it failed, but after reading about the changes made by Cox, I tried it again. It now works! Thanks for the heads up.

In addition, one other problem I had with HDMI also was fixed. I have my cable box set to 480p for SD video. Previously, with HDMI, when I changed between a HD and a SD channel, the video on my Sony KDL40S2000 HDTV would go blank. I would have to power the TV off and on to restore it. My understanding was that the 6416 dropped the HDCP handshake to the Sony HDTV when it switched resolutions between HD and SD. Now it works correctly. Goodbye composite video and digital optical cables; hello HDMI. I don't know if the firmware update fixed this or if having the Onkyo receiver in the curcuit fixed it.

I had given up hope on HDMI working for me. How it works as advertised.

Geore

I've been using my 6412 with my HDTV via HDMI cable with no problems. I just installed some new shelves and had it unplugged for a while. Now when I've hooked everything back up, I can't get the 6412 to output an HDMI signal.

The component cables work with the box, but not the HDMI. Any suggestions?


Thanks.

Any idea when the new STBs will be available?

I've been using my 6412 with my HDTV via HDMI cable with no problems. I just installed some new shelves and had it unplugged for a while. Now when I've hooked everything back up, I can't get the 6412 to output an HDMI signal.

The component cables work with the box, but not the HDMI. Any suggestions?


Thanks.

Maybe the 6412 reset itself when it was unplugged. Check http://en.wikibooks.org/wiki/How_to_use_a_Motorola_DVR/Setup#HDMI.2FYPbPr_Output and also the Bugs tab of that document.

Maybe the 6412 reset itself when it was unplugged. Check http://en.wikibooks.org/wiki/How_to_use_a_Motorola_DVR/Setup#HDMI.2FYPbPr_Output and also the Bugs tab of that document.

A lot of this looks interesting, especially in the "additional HDMI settings" options. But I don't have the 16.20 firmware and don't have those options. I don't think I have the option of switching on and off the HDMI output.

I may try and reset it to factory defaults, if that's even an option on my box. I've got a cox guy coming out on saturday, but he'll probably just swap out the box.

Halleluiah brothers and sisters!! After almost a year of waiting, yesterday Comcast in Salt Lake City finally D/L'd the 16.20 firmware to my STB. I haven't had a chance to test the HDMI/HDCP repeater aspect of it yet. Will do so this weekend and report back.

Keeping my fingers crossed. If it works I'll finally be 100% digital -- HDMI for the Moto 6412 CATV/DVR, HDMI for my Oppo 970 for 1080i upscaled DVD + high res PCM for SACD & DVD-A, Optical Digital for my Pio F605 CD player, and my iPOd 5G/30 through the special port on the AVR - all through my Pio Elite VSX-72TXV. SWEET:D

Of course I have read about the various bugs that have been introduced in the 16.20 FW update :( , so I hope they won't seriously detract from my happiness at finally being all digital.

Spoke to someone at Time Warner where TW recently took over from Comcast in Richardson, TX. Very pleasant, helpful young woman who didn't really understand and checked with a co-worker. Their conclusion was that this was a more technical conversation than they could understand or handle. Fair enough. Their next step is to send a tech who should be able to understand the problem.

Of course the tech won't be able to do anything here, but maybe he will be able to deal with someone up the line. Tech is scheduled for midday Friday. I'll share results.

I saved the tech a visit by explaining the situation. He thought it shouldn't be a problem to upgrade the firmware but that he had to talk to an engineer at the head end the following week and would get back to me in several days.

It is now the end of the "following week" and I haven't hear back. I'd actually forgotten that he owes me a call back. I've been waiting to see an update on my box, but that hasn't happened either. I'll call TW back Monday to get an update.

Bernie

I saved the tech a visit by explaining the situation. He thought it shouldn't be a problem to upgrade the firmware but that he had to talk to an engineer at the head end the following week and would get back to me in several days.

It is now the end of the "following week" and I haven't hear back. I'd actually forgotten that he owes me a call back. I've been waiting to see an update on my box, but that hasn't happened either. I'll call TW back Monday to get an update.

Firmware updates are only pushed out from the headend "en mass" to all STBs on their network at the same time. The decision of when to push the FW is made by the tech & admin folks at the highest levels running the headend -- and, apparently, is a closely guarded secret.

Although your tech thought "it shouldn't be a problem" -- he was wrong if he meant that you could get a FW update on your box independent of all others. If you want any kind of knowledgable answer (I gave up trying long ago and just "sat & waited") you need to call you cableco and keep pushing/escalating to someone who actually "KNOWS" when they will push out the next FW update (either 12.35 or more likely 16.20) across their network. Probably will be the top level tech manager for the headend -- if anyone.

As reported in my previous post -- yesterday they finally did it here in SLC -- so I assume your market can't be that far behind our little bitty one in the Intermountain West.

']Any idea when the new STBs will be available?


They are NOT going to be new STB's.. The Tivo software will be loaded on existing DCT-64xx boxes.

I'm in Allen, TX, with same situation/provider. My results are not looking good. The number they gave me (972-445-5555) was just a front to the same 972-PICKTWC menu tree, ending in a customer service rep who isn't trained in this specific issue. I got the same basic message. I won't go into the poor customer service/run-around in trying to get someone to talk to.
However, after stomping my feet, I got this reply via email:
"Thank you for responding to the email. We support the connection from the cable coming in to your home to the DCT 6412, then to the TV. The AVR box that you have is a connection that we don't support."

FYI- I don't have an AVR, am only contemplating this purchase. And I mentioned that to them. So the answer is "NO". I'm not happy about this. It basically says that TWC does not want any equipment between their box and the TV. Not good for supporting the growth and enthusiasm of the AV crowd, nor the growing customer base like me who is getting interested in this stuff.

I am hunting down a senior technical leader at TWC and will forward my question to them. I have to think that if I can get to a technically savvy person, I might get a better answer. It would be sad if the Customer Service "Specialist" says no and yet their corporate direction is "yes". Stay tuned....

Glad to report that the senior person I contacted did respond and has promised to get someone technical to engage with me. I haven't heard anything this week but am hopeful for next week.....

Halleluiah brothers and sisters!! After almost a year of waiting, yesterday Comcast in Salt Lake City finally D/L'd the 16.20 firmware to my STB. I haven't had a chance to test the HDMI/HDCP repeater aspect of it yet. Will do so this weekend and report back.

Keeping my fingers crossed. If it works I'll finally be 100% digital -- HDMI for the Moto 6412 CATV/DVR, HDMI for my Oppo 970 for 1080i upscaled DVD + high res PCM for SACD & DVD-A, Optical Digital for my Pio F605 CD player, and my iPOd 5G/30 through the special port on the AVR - all through my Pio Elite VSX-72TXV. SWEET:D

Of course I have read about the various bugs that have been introduced in the 16.20 FW update :( , so I hope they won't seriously detract from my happiness at finally being all digital.
Hooked up my 6412's HDMI output to the Pio Elite 72 over the weekend and I'm glad to confirm what OP's have reported -- FW V16.20 fixed the HDMI/HDCP repeater/handshaking problem. I'm now in "all digital" mode and lovin' it. :D

Of course it's ridiculous and still pisses me :mad: off that we all have had to wait so long for something that should NEVER have been a problem in the first place. But at least the promised fix works, so I'll "count my blessings" for now. ;)

Other than the well-known bug of not responding well to FF, REW and Play commands when moving through live recorded material (which I don't think was introduced by 16.20 -- just perpetuated) I haven't run into any of the new 16.20 bugs yet. :)

Happy to report that Insight Communications is getting ready to push-out firmware version 16.20! I just spoke to a very knowledgeable rep in their Florence office who gave me the information. No exact date yet, but he said 'within the next two weeks, barring any major issues'.

I'm not sure if this is for all Insight customers or only their Northern Kentucky system?

Firmware updates are only pushed out from the headend "en mass" to all STBs on their network at the same time. The decision of when to push the FW is made by the tech & admin folks at the highest levels running the headend -- and, apparently, is a closely guarded secret.

Although your tech thought "it shouldn't be a problem" -- he was wrong if he meant that you could get a FW update on your box independent of all others. If you want any kind of knowledgable answer (I gave up trying long ago and just "sat & waited") you need to call you cableco and keep pushing/escalating to someone who actually "KNOWS" when they will push out the next FW update (either 12.35 or more likely 16.20) across their network. Probably will be the top level tech manager for the headend -- if anyone.

As reported in my previous post -- yesterday they finally did it here in SLC -- so I assume your market can't be that far behind our little bitty one in the Intermountain West.
Just to set the record straight. My post above was based on info from my Comcast headend and other posts I have read in various AVS threads. BUT I just went over the audioholics.com thread devoted to this topic and saw a couple of posts saying that they have been able to get their individual STB's upgraded to the new firmware even though it had not been pushed out across the entire network. So even though I'm contradicting myself, I thought this info was important enough to share -- and I stand corrected. :o :( Here's a link --http://forums.audioholics.com/forums/showthread.php?t=21194&page=7

It looks like that with enough pushing, shoving and persistence some folks have been able to get the FW update ahead of others in their region. So it might be possible in other regions as well. Good luck.

Just to set the record straight. My post above was based on info from my Comcast headend and other posts I have read in various AVS threads. BUT I just went over the audioholics.com thread devoted to this topic and saw a couple of posts saying that they have been able to get their individual STB's upgraded to the new firmware even though it had not been pushed out across the entire network. So even though I'm contradicting myself, I thought this info was important enough to share -- and I stand corrected. :o :( Here's a link --http://forums.audioholics.com/forums/showthread.php?t=21194&page=7

It looks like that with enough pushing, shoving and persistence some folks have been able to get the FW update ahead of others in their region. So it might be possible in other regions as well. Good luck.

Thank you for sharing that encouraging bit of news, and the ink to the other site (especially post #54 at that site). I'd previously mentioned on here that I spoke to a Tech on January 5 about the problem and he said "shouldn't be a problem to get a firmware upgrade, but I'll have to talk to an engineer and I'll get back to you in a few days."

Well, I never did hear back from him so I called T-W again on January 16 and the Rep can't tell who the tech was and the incident had been closed, so she opened another incident. I spoke to a tech today and he was nearby so he came to the house. I showed him how to locate the firmware level in the diagnostics screen, and he also asked for a printout of the section of the wikibook that discusses the problem. He took that with him so that he would have more ammunition when as he tires to get a solution, or at least an answer. He was also going to examine boxes at the office to see if he could find one with a firmware level higher than 12.31. I have this tech's name and phone number, so if I don't hear back in a few days I cna track him down myself, and he said he would welcome that if I don't hear from him first.

I'll share what I learn here in Richardson, Texas

I have been reading all the posts regarding the HDMI / HDCP issues with the various DCT's. I have found that CC Maryland has set up a toggle in their databases to activate/deactivate the HDMI function. It is up to the Customer Account Executive to "flip the switch". You must challenge them to find and apply what you need. And yes, some STB's choke when an HDMI cord is connected to an A/V receiver/amplifier. We're still trying to sort out all the various chunks of info that trickle in.

To some of the contributors that are comparing the DCT 6412 III, DCT 3412 or DCT 3416 (newest dct on the market) to the DCT 700........there is no comparison, as the DCT 700 is not a DVR. It is a modem sized ADS Digital converter that many esthetically motivated consumers are demanding for in home use. They have no front LED screen for time or channel display and have only RF in/out ports and 1 set of composite outputs. Nothing fancy here.....just a solid non-HD ADS digital STB without the frills.

Does anyone have firmware version 12.41 on their 6412? I don't see that mentioned on Wikipedia. Nor have I seen it in this thread.

Anyway, with 12.41, I still can't get HDMI to work and receive the green screen. I have a a new Sony STR-DG1000 receiver and a Samsung DLP (720p).

Also, I'd be interested to hear if any Suddenlink customers have had any luck. When I talked to them, I got the typical "we don't support A/V receivers . .. " response and the CSR that I talked to had no idea what firmware was.

Thanks.

Hey, Comcast just upgraded us in Denver area to 16.20 as well this w/e. Connected to my receiver and changed the settings to use HDMI and it works! HDMI from the Comcast box to Receiver and from there to my LCD and a great picture. Am able to up-convert my cable, although a few channels that have poor quality still are poor when upconverted. However I did notice that if I want to watch TV and listen to other music I won't be able to do that unless I move the connection. Not to big a deal though, actually easy for me to do that if necessary since my LCD swivels around and its right next to my receiver.

Glad to report that the senior person I contacted did respond and has promised to get someone technical to engage with me. I haven't heard anything this week but am hopeful for next week.....
Took some more firm prodding but finally got some response.

Senior Tech leaders at TWC confirm that they know of the issue of HDCP/HDMI with the DCT 6412 box. They will be testing the fix and if that works well, will roll it out in the next few months. This is good - they know it and have plans to fix it.

I'm pushing back to get some more firmness on dates - like when testing will start and how to stay engaged on the process so I know when I can take advantage of a better setup. At this point it's not firm enough for me.

So, some encouraging news in the near term - but we still have to get thru testing/deployment. If you are a TWC subscriber and have the aforementioned HDCP issue OR are considering adding an AVR to your mix (DCT 6412/HD TV), make noise. The more noise we make, the faster we'll all benefit.

How do we 'make noise'? I have called them several times only to talk to people who have no idea what I am talking about... I asked to speak to people higher up, and they said I couldnt speak to the higher tier techs as they dont take phone calls... So who should I talk to? Thanks

Took some more firm prodding but finally got some response.

Senior Tech leaders at TWC confirm that they know of the issue of HDCP/HDMI with the DCT 6412 box. They will be testing the fix and if that works well, will roll it out in the next few months. This is good - they know it and have plans to fix it.

I'm pushing back to get some more firmness on dates - like when testing will start and how to stay engaged on the process so I know when I can take advantage of a better setup. At this point it's not firm enough for me.

So, some encouraging news in the near term - but we still have to get thru testing/deployment. If you are a TWC subscriber and have the aforementioned HDCP issue OR are considering adding an AVR to your mix (DCT 6412/HD TV), make noise. The more noise we make, the faster we'll all benefit.

I am much more confident and understanding that the problem will be fixed by TWC. The folks I've chatted with have been good about explaining to me the state of things. The good news is they are working on final testing to support new boxes that support FCC Cable Card mandates. And that testing includes the fix for HDCP. It could still go sideways; the main software goes but the bug for HDCP doesn't prove out - but it could more than likely be fixed as part of the new firmware. My sense is they have a logistic challenge - making sure a lot of software all interrelated passes QA.

I've got a contact who will let me check back occasionally and see how things are going. So with testing starting in a few weeks, we may have some more insight in about two months about the "when" it will be available. Some time after that obviously, a fix could be available.

If you have HDMI and DCT6412 and an AVR, you will have problems using that setup for a few more months. If you can get around it by using component/optical then you can stay functional. If you're like me and want to buy a setup, know that it's still going to be a few more months. But it is known and will get fixed, I believe. I was about to drop TWC and try some other avenue but will now stay a customer - they were THAT open and helpful to me.

I now don't think we can do much to beat on them to force a fix. I work in software and understand the complexities in large complex systems. If the testing breaks down then maybe we should raise the noise. But right now, it just doesn't seem that that would solve the immediate problem.

Cheers!

I am much more confident and understanding that the problem will be fixed by TWC. The folks I've chatted with have been good about explaining to me the state of things. The good news is they are working on final testing to support new boxes that support FCC Cable Card mandates. And that testing includes the fix for HDCP. It could still go sideways; the main software goes but the bug for HDCP doesn't prove out - but it could more than likely be fixed as part of the new firmware. My sense is they have a logistic challenge - making sure a lot of software all interrelated passes QA.

I've got a contact who will let me check back occasionally and see how things are going. So with testing starting in a few weeks, we may have some more insight in about two months about the "when" it will be available. Some time after that obviously, a fix could be available.

If you have HDMI and DCT6412 and an AVR, you will have problems using that setup for a few more months. If you can get around it by using component/optical then you can stay functional. If you're like me and want to buy a setup, know that it's still going to be a few more months. But it is known and will get fixed, I believe. I was about to drop TWC and try some other avenue but will now stay a customer - they were THAT open and helpful to me.

I now don't think we can do much to beat on them to force a fix. I work in software and understand the complexities in large complex systems. If the testing breaks down then maybe we should raise the noise. But right now, it just doesn't seem that that would solve the immediate problem.

Cheers!
Hmmmm..... That's a very nice and easy-going approach to this problem - :confused: - BUT the fact is that starting many months ago various cable companies and/or regions of the same cableco were deploying firmware V12.31 or 16.20 that does indeed FIX the problem that is the primary concern of those posting in this thread. Firmware V16.20 was just downloaded to my STB a few weeks ago and since then I have been able to switch the DCT6412 HDMI output via my AVR to my HDTV with no problem.

[START OF RANT] :mad: Other than basic incompetence -- since the fix is known and widely available-- I find it VERY hard to understand why ANY cableco can not simply deploy the firmware that fixes the HDMI/HDCP repeater problem. IT IS AVAILABLE AND READY TO GO -- SOOOOO JUST DO IT -- DAMN IT!!!! Stop with the excuses and thumbs up the rectum. ("Rectum? Damn near killed him! -- obligatory ending to any use of the word "rectum")

I also work in software and understand the complexities of version upgrades, large-scale rollouts, etc. BUT IMO the cablecos have had PLENTY of time and opportunity to fix this problem and -- in many cases -- have simply refused to do so. The complexity of the problem was known long ago and a fix was available long ago. The reason it has not been deployed in many cases is that (for the most part) the cablecos have a monopoly and don't really give a sh*t.)[END OF RANT] :mad: :mad:

I am much more confident and understanding that the problem will be fixed by TWC. The folks I've chatted with have been good about explaining to me the state of things. The good news is they are working on final testing to support new boxes that support FCC Cable Card mandates. And that testing includes the fix for HDCP. It could still go sideways; the main software goes but the bug for HDCP doesn't prove out - but it could more than likely be fixed as part of the new firmware. My sense is they have a logistic challenge - making sure a lot of software all interrelated passes QA.

I've got a contact who will let me check back occasionally and see how things are going. So with testing starting in a few weeks, we may have some more insight in about two months about the "when" it will be available. Some time after that obviously, a fix could be available.

If you have HDMI and DCT6412 and an AVR, you will have problems using that setup for a few more months. If you can get around it by using component/optical then you can stay functional. If you're like me and want to buy a setup, know that it's still going to be a few more months. But it is known and will get fixed, I believe. I was about to drop TWC and try some other avenue but will now stay a customer - they were THAT open and helpful to me.

I now don't think we can do much to beat on them to force a fix. I work in software and understand the complexities in large complex systems. If the testing breaks down then maybe we should raise the noise. But right now, it just doesn't seem that that would solve the immediate problem.

Cheers!

I wasn't going to say it quite the way that Skipsterut said it, but I was going to say more or less the same thing. Motorola has developed a fix, quite some time ago, and Comcast, TWC and others have been rolling it out sporadically. I'll be glad when they have completely new software for the box, or a new box, but in the meantime there is a fix readily available. Even if they are trying to avoid two upgrades within a period of several months, they could/should make the existing fix available to people that report the problem now.

I am using the optical feed from the cablebox to the AVR, and the hfmi video feed direct to the TV as a bypass. BUT, it appears that the delay factor is different when displaying DVR video than when displaying DVD video. I'm hoping/expecting that difference to go away when everything goes through the HDMI feed. That will also provide the convenience of showing adjustments on the AVR to be displayed on the TV.

TWC certainly has no problem making repeated, frequent changes to the channel line-up. In my locality two significant changes in January alone.

So, glad you're getting responses, but they sound like someone just sharing their plans for the future, not someone responding in the best and easiest way to real customer needs. And I, too, have been involved in software product development and implementation of large systems.

Bernie

----------------------------------------------------------------------------------------------------------
Happy to report that Insight Communications is getting ready to push-out firmware version 16.20! I just spoke to a very knowledgeable rep in their Florence office who gave me the information. No exact date yet, but he said 'within the next two weeks, barring any major issues'.

I'm not sure if this is for all Insight customers or only their Northern Kentucky system?
---------------------------------------------------------------------------------------------------------
Hi,
I stay in Lexington, KY and Insight Customer. Can you give me the tel # to contact to get firmware upgrade information. Tried customer support, and standard reply.
Did you receive the firmware upgrade. ?

Thanks.

Hmmmm..... That's a very nice and easy-going approach to this problem - :confused: - BUT the fact is that starting many months ago various cable companies and/or regions of the same cableco were deploying firmware V12.31 or 16.20 that does indeed FIX the problem that is the primary concern of those posting in this thread. Firmware V16.20 was just downloaded to my STB a few weeks ago and since then I have been able to switch the DCT6412 HDMI output via my AVR to my HDTV with no problem.

[START OF RANT] :mad: Other than basic incompetence -- since the fix is known and widely available-- I find it VERY hard to understand why ANY cableco can not simply deploy the firmware that fixes the HDMI/HDCP repeater problem. IT IS AVAILABLE AND READY TO GO -- SOOOOO JUST DO IT -- DAMN IT!!!! Stop with the excuses and thumbs up the rectum. ("Rectum? Damn near killed him! -- obligatory ending to any use of the word "rectum")

I also work in software and understand the complexities of version upgrades, large-scale rollouts, etc. BUT IMO the cablecos have had PLENTY of time and opportunity to fix this problem and -- in many cases -- have simply refused to do so. The complexity of the problem was known long ago and a fix was available long ago. The reason it has not been deployed in many cases is that (for the most part) the cablecos have a monopoly and don't really give a sh*t.)[END OF RANT] :mad: :mad:

Good points.

I guess I"m not ranting because I investigated before I got into the situation of being challenged by the technology. I suppose I'm behind the curve/you/others in that regard.

I didn't try to find out why it's not fixed yet - TWC just took over our system a few months ago - and the box has not changed in one bit since then. Same firmware. So if I have a beef, it would be with Comcast (old system) which seems to be fixing it now for others. But since I'm in TWC-land, just in dumb bad luck/timing seems to rule.

It is VERY sad that the industry can't keep these kinds of problems from happening. I let lots of my friends know to be careful before the jump in.

I suggest you go blast those at TWC for the issue. Doing it here probably won't get much of their attention.

I have been having problems with this as well with Comcast in the Philadelphia area, and being a stubborn fool who demands answers I slowly pushed my way up the CSR chain at Comcast. I figured I'd share the responses.

Hello Mr. McManimie,

We do not routinely disseminate code information to anyone as a general rule. The code you mentioned has other bugs in it that needed to be addressed and is being examined in detail in a lab scenario.

I can understand your unhappiness with the HDMI issue, but with monolith type code acceptance (TV Guide, SeaChange and Motorola in this case)there are other impacting events we must watch for.


Dan McMonigle
Director, New Product Implementation
Comcast East Division




-----Original Message-----
From: Bridge, David
Sent: Tuesday, February 06, 2007 1:37 PM
To: McMonigle, Dan
Subject: DVR Firmware HDMI question

Hello Dan,

Are you able to give me some advice on a Firmware issue affecting our DVR's? I have been responding to a customer who is trying to get any information on this issue, and I'm pretty well out of resources on this one.

Any help would be appreciated.

Please see correspondence, starting at very bottom. Thanks, David.


Original Message Follows:
-------------------------

We'll, with all due respect, if this was done on a routine basis then the firmware release that Motorola distributed last June (http://en.wikibooks.org/wiki/How_to_use_a_Motorola_DVR/Firmware_and_Sof
twar
e#Version_12.35) would have been installed by now. Moreover I am running 12.22, and thereby I haven't been upgraded in well over a year now.

David, I am fully aware that this is done by your engineering staff, and I also realize, based on extensive correspondence with your low level support staff that we are not permitted contact with the engineers. My question is whether you can provide me with some insight in regard to a roll out schedule for our area. This firmware upgrade has been distributed to scattered service areas throughout the country and so I was hoping at the very least I could speak to someone who is at the very least cognizant of this HDMI issue, and possibly provide me with a small nugget of info regarding when, if ever, I may be able to take advantage of the high end functionality that you allegedly support.

Respectfully,

-Ryan

-----Original Message-----
From: Comcast ECARE-NewCastle [mailto:ecare-NewCastle@comcast.com]
Sent: Saturday, February 03, 2007 11:46 AM
To: Ryan McManimie
Subject: RE: Service - Comcast Cable Television (KMM24634460V21127L0KM)

Dear Mr. McManimie,

Thank you for contacting Comcast Cable.

Firmware upgrades on Comcast equipment are carried out routinely by our engineering staff.

We have no input on when this is done - it the domain of the Engineering staff, who do not interact with customers on this issue.

Please be assured, the upgrade will be forthcoming, as/when our Engineering staff are ready with the upgrade.

Sincerely,
David
Comcast Customer Care Specialist

I have V 16.20 in my Moto 3412 hooked directly to a Mits 52631 and last night I got the "swamp water" green screen and the - compromised HDMI connection - message. A couple of cold starts with the TV and STB got me going again. I feel they still have a ways to go past 16.20.

So I'm not the only person with this problem. I contact Comcast everyday thru an online chat. I talk to either Nicole or Leslie sometimes another person and they keep telling me they won't push out a firmware for just one person. So I tell them I will keep coming back until they upgrade us all. I think I might just go to DirecTV even though I don't like the unsightly dishes and that they have to hang off of my house, but this is getting ridiculous.

I think the only thing that keeps me sane is that I get to pester Nicole and Leslie on a daily basis. Or does that make me crazy who knows.

By the way I have an Onkyo TX-SR674 with a Philips LCD, the POS 6412 PIII and on my way to pickup a PS3 this weekend. All of these could be ran thru the HDMI on my ONKYO only if I had the right firmware version. So for now I run my component cable and wait.

So I'm not the only person with this problem. I contact Comcast everyday thru an online chat. I talk to either Nicole or Leslie sometimes another person and they keep telling me they won't push out a firmware for just one person. So I tell them I will keep coming back until they upgrade us all. I think I might just go to DirecTV even though I don't like the unsightly dishes and that they have to hang off of my house, but this is getting ridiculous.

I think the only thing that keeps me sane is that I get to pester Nicole and Leslie on a daily basis. Or does that make me crazy who knows.

By the way I have an Onkyo TX-SR674 with a Philips LCD, the POS 6412 PIII and on my way to pickup a PS3 this weekend. All of these could be ran thru the HDMI on my ONKYO only if I had the right firmware version. So for now I run my component cable and wait.

You might want to check the 1080P Panel Wars III Westinghouse LVM-37w3 37" LCD thread here at avsforum [sorry, I cannot yet post a link]. The PS3 is reported to have HDMI handshaking problems. You might want to serach the thread to find out if HDMI-switch is viable at this time.

Does this issue apply equally to those with the 3416?

My 6412 box has the following software:

SW Ver 71.44 1203
Firmware: 09.19

These numbers do not seem to align with the firmware versions I've heard others reporting. Am I misreading this firmware? What version do I need have and does it have the patch applied for HDMI? Thanks.

My 6412 box has the following software:

SW Ver 71.44 1203
Firmware: 09.19

These numbers do not seem to align with the firmware versions I've heard others reporting. Am I misreading this firmware? What version do I need have and does it have the patch applied for HDMI? Thanks.

No, that version does not fix the HDMI problem. It is a pretty old version. Check http://en.wikibooks.org/wiki/How_to_use_a_Motorola_DVR/Firmware_and_Software

No, that version does not fix the HDMI problem. It is a pretty old version. Check http://en.wikibooks.org/wiki/How_to_use_a_Motorola_DVR/Firmware_and_Software

Actually I was making an assumption that sounds like was incorrect based on your info...

Currently I have the 6412p1 (I believe it is the p1, definitely not the p3). My box only has DVI.

I'll be getting a new HDMI A/V receiver soon along with an HDMI display and am planning to pick up a new STB from Comcast that is the 6416 or 3416 with the HDMI.

I assumed that if I looked at the firmware on my old 6412 that it would be representative of the firmware I'd have on the new HDMI box. But it sounds like the firmware is specific to the box?

So is it possible then that if I picked up the new HDMI box it would have a newer firmware? Or was my original assumption actually correct and I'd have the same old firmware on that box too?

Thanks!

Actually I was making an assumption that sounds like was incorrect based on your info...

Currently I have the 6412p1 (I believe it is the p1, definitely not the p3). My box only has DVI.

I'll be getting a new HDMI A/V receiver soon along with an HDMI display and am planning to pick up a new STB from Comcast that is the 6416 or 3416 with the HDMI.

I assumed that if I looked at the firmware on my old 6412 that it would be representative of the firmware I'd have on the new HDMI box. But it sounds like the firmware is specific to the box?

So is it possible then that if I picked up the new HDMI box it would have a newer firmware? Or was my original assumption actually correct and I'd have the same old firmware on that box too?Did you read the info in the Wiki link in bernie33's post? The firmware isn't specific to the box itself, but to the model or series (phase). It's kind of obvious that you have a P1 box which has a completely different firmware series than P2 and P3 boxes.

Whether or not a new 64XX (P2 or P3) or 34XX box in your region has the required firmware to fix the HDCP repeater problem -- maybe someone can tell you if you'll post where you are geographically. Or call your local cableco and ask them.

Better yet, since it doesn't cost anything and you need to do it anyway, just go to your local cableco office with your P1 in hand, and exchange it for the latest model they have available. You'll more than likely get a P3 box (maybe P2, but I doubt it) which will certainly have different firmware than your P1 box. Take it home, plug it in and then follow the Wiki instructions to see which firmware version you have. If you're lucky you'll have 12.35 or 16.20.

Working with Comcast in Richmond is very painful. I had them send out a technician with a new box. He called me up and asked me what firmware was. After I told him he told me to call another office in the area. I actually got to speak to a manager and they basically said "We'll get to it when we get to it". I'm so freakin irritated with this. I am still not getting this resolved.

I've talked to DirectTV and the sales person didn't know what HDMI was or what firmware was. So I hung up and called Verizon FIOS, fortunately they have the same boxes 6412 and she said they are using firmware 15.18 which from the wiki doesn't even exist so I'm pretty sure she doesn't know what firmware means either. She tried though, at least.

Why do companies hire people who do not know what they are selling or what features come with the product. How hard can it be to read a little about your product. Basically we're all screwed until they hire some compotent people who give a d**n about the customers. :mad:

At Comcast, the customer is always wrong.

--SNIP--
So for now I run my component cable and wait.That's what I did because my HDTV only has one HDMI input and I also wanted to be able to control everything thorugh the AVR. But if your TV has 2 HDMI inputs another option is to run HDMI from the 6412 directly to the TV and switch the TV's source between the AVR feed of your other gear and the 6412 depending on what you are watching. The only advantage of this is being able to have digital video instead of component while you are waiting for your local Comcast to fix the HDCP repeater problem. I personally can not see the difference in HD between component and HDMI signals as displayed on my TV, so I was fine with my setup. But others have a more discerning eye and prefer the digital video.

--SNIP--
Why do companies hire people who do not know what they are selling or what features come with the product. How hard can it be to read a little about your product. Basically we're all screwed until they hire some compotent people who give a d**n about the customers. As Slick Willie said "I feel your pain." Sounds like you are doing everything possible to get someone at your local Comcast to respond to the issue, but they appear to be even more incompetent and less customer friendly than many others. I've alrady done my rant about this kind of behavior by Comcast and other cablecos so won't do it again ...... but ARRGGHHHHH!!!! :mad: :mad:

I have the 6416, and Comcast upgraded our firmware about 4 days before my HDMI cables arrived.

Plugged it in through my Onkyo TX-SR604 HDMI Port 1, and no picture. Spent about an hour on the phone with the comcast technician. She never solved the issue, but she was very pleasant and did know about the HDCP issues, and she tried to troubleshoot that. When we gave up she took my information and told me that she would have another technician, who "was very versed in this stuff" contact me when he got off of his next call. Must have been a long call, because a week and a half later I still haven't heard from him.

Called Onkyo, and they suggested performing a clear on my receiver, and configuring the HDMI ports again. I did this, and it didn't seem to work. Then I decided to try moving the cable over to HDMI port 2, and viola!! It worked. HDMI Port 1 wants to automatically configure to the DVD input when you turn on HDMI switching, so I'm wondering if Onkyo won't allow the connection for non-DVD sources through HDMI 1. Sounds far fetched to me, and when I get a few minutes (my cable box is in the basement, and my tv is in the family room, so changing sources and testing requires a lot of trips up and down the stairs) I'm going to switch back to HDMI 1 with the Comcast box to see if I still get a picture.

Does this bug we are discussing affect all HDMI switchers, or just those in A/V receivers?

For example, I may hold off on an HDMI switching receiver and just get a 3 in 1 HDMI switcher. If my local Comcast does not have the corrected firmware, will I have the same problem of not being able to get HDMI on my display throught the switcher (or is this issue specific somehow to A/V receiver switching)?

Thanks!

Does this bug we are discussing affect all HDMI switchers, or just those in A/V receivers?

For example, I may hold off on an HDMI switching receiver and just get a 3 in 1 HDMI switcher. If my local Comcast does not have the corrected firmware, will I have the same problem of not being able to get HDMI on my display throught the switcher (or is this issue specific somehow to A/V receiver switching)?

Thanks!I think I have seen posts saying that some video scalers and/or switchers are OK, but can't guarantee it. The basic problem is that the STB's can't handshake correctly with any device that identifies itself as an HDCP repeater. It would seem to me that a simple switch is not a "repeater" in the sense defined in the HDCP spec, but that's just an assumption. Perhaps you could find out either in the specs or from the manuafcturer of the switcher if it is considered as an HDCP repeater or not. Another option is to buy it from a company with a good 30 day return policy (e.g. jr.com, Vanns, etc.), try it out and return if it doesn't work.

As I mentioned in a couple of my previous posts I didn't find the option of connecting the STB via component as an interim solution to an HDMI switching AVR to be that bad -- aggravating and frustrating that it had to be done -- but IMO preferable to spending money for an extra device such as an HDMI switcher. If you're ready to upgrade your system with a new AVR and the only thing stopping you is the STB HDCP problem, I would go ahead and enjoy the benefits of the new setup now, and just live with component out of the STB until they update your firmware, which I imagine will probably be in the next few months anyway, since many regions have already deployed the new firmware. Then when they do update your firmware all you need to do is replace the component cable from the STB to the AVR with an HDMI cable and your in "full digital" mode.

Another thing to consider is that most of the new AVR's are also video scalers, so even a component input to the AVR will be not only converted to HDMI digital it would also be upscaled to 720p, 1080i, or 1080p depending on the AVR and your HDTV's display capability. So from a PQ perspective the HDMI out of the STB is almost unnecessary if your AVR does a good job of scaling the video. Again, thinking of this as a temp ifx until the STB firmware is updated -- hopefully soon. Just my $0.02 FWIW.

I'm with Comcast in Annapolis, MD and am building a new media room. I was an early HDMI convert and ran into the HDCP issue right off the bat - that was many moons ago and I'm deflated checking back on this forum to find the problem evidently hasn't been resolved. In my new media room I have to pull in-wall cables (electrical inspectors, don't you know) so I have to get it right. I'm using the new Mits HC5000BL projector and was going to run HDMI from my amp - sounds like I better opt for a high quality component cable instead!

I'm with Comcast in Annapolis, MD and am building a new media room. I was an early HDMI convert and ran into the HDCP issue right off the bat - that was many moons ago and I'm deflated checking back on this forum to find the problem evidently hasn't been resolved. In my new media room I have to pull in-wall cables (electrical inspectors, don't you know) so I have to get it right. I'm using the new Mits HC5000BL projector and was going to run HDMI from my amp - sounds like I better opt for a high quality component cable instead!Which amp/AVR do you have? Assuming its a fairly recent model AVR with HDMI capability, you can probably still run HDMI from the AVR to the the Mits pj since the AVR should either transcode (i.e., convert from analog to digital with no change in resolution) and/or transcode and upscale any lower level signal. Thats' how I am using my Pio Elite 72. I have the following inputs -- 2 HDMI (Moto STB and Oppo 970 DVD), 1 component (also the Moto STB), 1 composite (an old VCR) but there is just one HDMI output to my Panny HDTV -- since the Pio transcodes all the lower level signals to the HDMI out. :)

BTW -- One thing to be careful about in long runs of HDMI is to get the right gauge wire --or for really long runs you might need an amp/repeater in the circuit. See thie Wikibook article for more (http://en.wikipedia.org/wiki/Hdmi#Cable_length).

I think I have seen posts saying that some video scalers and/or switchers are OK, but can't guarantee it. The basic problem is that the STB's can't handshake correctly with any device that identifies itself as an HDCP repeater. It would seem to me that a simple switch is not a "repeater" in the sense defined in the HDCP spec, but that's just an assumption.

So are there SOME A/V receivers that will work with HDMI and firmware prior to 12.35?

I just picked up a 3416. I don't have my A/V receiver with HDMI switching yet so I can't try that part of it out. The firmware shows at 12.31. Not good...

I was wondering though - as soon as I plugged in my box it did not download any firmware. Is it possible that it will take hours/days/weeks and then download new software? The box was factory sealed with plastic so perhaps its possible that Comcast in my area is running firmware, and it just will take the box some time to download it? Is it worth me forcing a refresh of the firmware to see what happens?

Thanks!!

So are there SOME A/V receivers that will work with HDMI and firmware prior to 12.35?Maybe, but not that I have heard of. Certainly not if they are HDCP compliant.

I just picked up a 3416. I don't have my A/V receiver with HDMI switching yet so I can't try that part of it out. The firmware shows at 12.31. Not good...3416 is good -- all digital and 160 GB -- the current max available from Comcast. But yep - 12.31 is not good for HDMI via an AVR.

Is it worth me forcing a refresh of the firmware to see what happens?Probably can't hurt - especially since it was "factory wrapped" when you got it. But since you don't have an HDMI AVR yet what's the rush? :confused:

Probably can't hurt - especially since it was "factory wrapped" when you got it. But since you don't have an HDMI AVR yet what's the rush? :confused:

I'll be picking up the new HDMI AVR within the next week or two so I'm just trying to get prepared in advance.

Let's say worse case scenario I can't get the HDMI working through the AVR. In this case I will run the HDMI to the display straight from STB. Then use an optical cable into my AVR.

However can someone please confirm that when the HDMI is used on the 3416 - does it still output 5.1 audio simultaneously on the optical jack (even though an HDMI cable is plugged in)?

Thanks!

I'll be picking up the new HDMI AVR within the next week or two so I'm just trying to get prepared in advance.

Let's say worse case scenario I can't get the HDMI working through the AVR. In this case I will run the HDMI to the display straight from STB. Then use an optical cable into my AVR.

However can someone please confirm that when the HDMI is used on the 3416 - does it still output 5.1 audio simultaneously on the optical jack (even though an HDMI cable is plugged in)?

Thanks!

I have a 6412-3, connected the way you describe to the TV and the AVR, and yes the audio works fine.

I'll be picking up the new HDMI AVR within the next week or two so I'm just trying to get prepared in advance.

Let's say worse case scenario I can't get the HDMI working through the AVR. In this case I will run the HDMI to the display straight from STB. Then use an optical cable into my AVR.

However can someone please confirm that when the HDMI is used on the 3416 - does it still output 5.1 audio simultaneously on the optical jack (even though an HDMI cable is plugged in)?It does on my 6412 -- all outputs are active at all times, and using one does not have any effect on the others. I'd be 99% certain it's the same on the 3416. But maybe someone with a 3416 can "chime in" here to confirm.

I think I saw this issue addressed in the official 3412 & 3416 thread (http://www.avsforum.com/avs-vb/showthread.php?t=604142) so either a thread search or a new post there might get you a quick answer.

Well, you guys called it and I confirmed it... Just tried with firmware 12.31 sending HDMI from the 3416 into my A/V receiver and to my display via HDMI. It shows the picture just fine for a few seconds, then puts up this message, then goes to an all green screen:

"The set-top does not support HD content protected repeaters. Please use the YPbPr outputs for your HD connections." Arghh! :mad:

Does anyone have a good suggestion for a good way to find the right contact within my local Comcast office who knows about firmware updates and works on the tech side of things? I'm sure if I just call in with this to the regular customer service folks they either won't have a clue what I'm talking about or have no useful info. Thanks!

Well, you guys called it and I confirmed it... Just tried with firmware 12.31 sending HDMI from the 3416 into my A/V receiver and to my display via HDMI. It shows the picture just fine for a few seconds, then puts up this message, then goes to an all green screen:

"The set-top does not support HD content protected repeaters. Please use the YPbPr outputs for your HD connections." Arghh! :mad:

Does anyone have a good suggestion for a good way to find the right contact within my local Comcast office who knows about firmware updates and works on the tech side of things? I'm sure if I just call in with this to the regular customer service folks they either won't have a clue what I'm talking about or have no useful info. Thanks!

You're in the same boat as the rest of us, waiting for our respective cable companies to roll-out the update. And local franchises are on different schedules, there is no consistency across the country within either Comcast or Time Warner.

You're in the same boat as the rest of us, waiting for our respective cable companies to roll-out the update. And local franchises are on different schedules, there is no consistency across the country within either Comcast or Time Warner.What he said.

Fortunately I am one of the lucky few -- V16.20 was deployed by our headend in early January. But since I had post #2 (and many more) in this thread, you can see that I've been pushing, shoving -- and mostly waiting -- for almost a year.

As to trying to get help/info from your local Comcast -- it's just a matter of luck -- but stubborn persistence, refusing (politely) to take the standard CSR line of crap and insisting to speak to a manager -- maybe, but not likely -- will help. Perhaps you'll at least get through to someone who is willing to say when they will roll out the FW update, so you won't have to stew and fume with no end in sight. :mad: :(

Good luck. Let us know how it goes.

I have a supervisor at Cox cable looking into my firmware problem. It took me many calls to finally get someone to listen to me. Most CSRs didn't even know what I was talking about. She actually called me back and told me they are looking into it. She then said she would call back in the next couple of days with more info. I was impressed I even got that far. This is total bullcrap that they can't just update the boxes. I told her that these receivers are becoming mainstream and they are going to be getting many complaints. I am keeping my fingers crossed.

I have a supervisor at Cox cable looking into my firmware problem. It took me many calls to finally get someone to listen to me. Most CSRs din't even know what I was talking about. She actually called me back and told me they are looking into it. She then said she would call back in the next couple of days with more info. I was impressed I even got that far. This is total bullcrap that they can't just update the boxes. I told her that these receivers are becoming mainstream and they are going to be getting many complaints. I am keeping my fingers crossed.

I filed a complaint with the Better Business Bureau and a Comcast representative said that she didn't know what firmware was until she saw my complaint. I told her most of your people don't know what it is, that's the problem. She still said that "it is in testing" and "will be released" so basically I'm screwed until then. So filing a complaint with the BBB gets you no where. Next stop FCC.

It would be nice if someone could develop a firmware upgrade utility and get access to the upgraded firmware files. I even offered to be a beta tester and they told me that they don't offer that. I laugh when I get that damn generic comment about how "we don't offer support over hdmi". If I learn I can get a direct tv box that can satisfy my needs then I will switch over and drop cable.

What he said.

Fortunately I am one of the lucky few -- V16.20 was deployed by our headend in early January. But since I had post #2 (and many more) in this thread, you can see that I've been pushing, shoving -- and mostly waiting -- for almost a year.

As to trying to get help/info from your local Comcast -- it's just a matter of luck -- but stubborn persistence, refusing (politely) to take the standard CSR line of crap and insisting to speak to a manager -- maybe, but not likely -- will help. Perhaps you'll at least get through to someone who is willing to say when they will roll out the FW update, so you won't have to stew and fume with no end in sight. :mad: :(

Good luck. Let us know how it goes.
Of course, as you've seen from other posters, it's not necessarily a good thing to get a date, because technical problems can and do push that date back multiple times, causing increased frustration. In my area, we had multiple dates to get 12.35, but as other areas rolled it out, the new bugs it brought caused my area to scrap it altogether and wait for 16.20.

What firmware update contains the new (fancy) menu's with video windows and so forth (VRN I think it may be called)? When our area rolls this out will that for sure include the HDMI repeater fix or are these things separate?

What firmware update contains the new (fancy) menu's with video windows and so forth (VRN I think it may be called)? When our area rolls this out will that for sure include the HDMI repeater fix or are these things separate?

I think these are different. I've been on 12.31 for a while and my menu's changed but my firmware stayed the same. Someone can correct me if I'm wrong.

Low rumbling chant "Fios, Fios, Fios, Fios"

Maybe when Fios is in my neighborhood, it will make comcast crumble and then another providor can go on ignoring my pleadings.

Well I am completely surprised that I got a follow up call from the supervisor at Cox cable telling me that they plan on doing a firmware upgrade in March (this month). She is not sure what date but it should be in March. I just hope that they follow thru with this.

I just wrote a complaint letter to Comcast headquarters and finally someone called me back from my local Comcast headend and said that we will be getting firmware 16.35 on Wednesday night Thursday morning. This should fix all my problems even some that other users are having with the DVR.

I just wrote a complaint letter to Comcast headquarters and finally someone called me back from my local Comcast headend and said that we will be getting firmware 16.35 on Wednesday night Thursday morning. This should fix all my problems even some that other users are having with the DVR.

Great news! Did they say what areas it would be rolled out in?

I just wrote a complaint letter to Comcast headquarters and finally someone called me back from my local Comcast headend and said that we will be getting firmware 16.35 on Wednesday night Thursday morning. This should fix all my problems even some that other users are having with the DVR.Yes, that's great news! Enjoy! :D

Maybe more complaint letters would get more action -- or at least a higher level of communication with their customers.

Our Time Warner DVR hasn't made the shift to Dalight Savings Time. Neither has the Guide. I don't find anything on TWC's webpages about it either.

I'm surprised I haven't seen it mentioned here.

Bernie

Yes, that's great news! Enjoy! :D

Maybe more complaint letters would get more action -- or at least a higher level of communication with their customers.

To who's attention at corporate should we send a letter?

To who's attention at corporate should we send a letter?cadsystems -- who did you write to? Was it your local Comcast HQ or corporate HQ? How did you address it -- i.e., to who's attention?

cadsystems -- who did you write to? Was it your local Comcast HQ or corporate HQ? How did you address it -- i.e., to who's attention?

I went online and found this link under executive section of the website audit_committee_chairman@comcast.com and wrote about a 2 page synopsis of the problem and how to fix it plus the run around that I was getting from my local Richmond Headend. The next day I got an email back, the day after that I got a phone call, and then the day after that I got an Engineer that left a message that said they were pushing out 16.35 to the Richmond VA area on Wednesday night. It's done. It works pretty good, haven't had a time to test it thuroughly since I was in DC all day working on a DS3 connection with Verizon. I did notice that when using the HDMI when I change channels it takes a few seconds for the signal to show up then it's fine. My Onkyo shows no signal for about 5 seconds then it comes through. Anyone else having this problem? It's not horrible but it would be nice if it worked faster. I hate this whole HDCP issue making us jump through hoops just to get our equipment hooked up and running right.

I have the Onkyo TX-SR604, and I get the same delay. I typically only see it when I go from an HD broadcast to a non-HD broadcast or vice-versa. But I sometimes "lose signal" for as much as 5 seconds or so when I'm skipping forward on a recorded or time-shifted program.

I have a friend who just hooked up his Comcast box and Pioneer HTR via HDMI, and he's reported similar delays.

I have the Onkyo TX-SR604, and I get the same delay. I typically only see it when I go from an HD broadcast to a non-HD broadcast or vice-versa. But I sometimes "lose signal" for as much as 5 seconds or so when I'm skipping forward on a recorded or time-shifted program.

I have a friend who just hooked up his Comcast box and Pioneer HTR via HDMI, and he's reported similar delays.

I read some where that a person fixed it by hooking up his audio thru another cable and assigning that audio to the port and that fixed this problem. i might try that this weekend to see if that fixes this problem.

I read some where that a person fixed it by hooking up his audio thru another cable and assigning that audio to the port and that fixed this problem. i might try that this weekend to see if that fixes this problem.


Not sure if that would work or not. I may try it also, just to see. I have a feeling it may have more to do with HDMI/HDCP video than audio.

Even if it does work I don't like that as a workaround. One of the selling points of HDMI is the ability to cut down on cables, and get rid of the need for the TOS cable. If they're going to make me live with the HDCP aspect of HDMI, I would expect to get the ostensible benefits, too.

Not sure if that would work or not. I may try it also, just to see. I have a feeling it may have more to do with HDMI/HDCP video than audio.

Even if it does work I don't like that as a workaround. One of the selling points of HDMI is the ability to cut down on cables, and get rid of the need for the TOS cable. If they're going to make me live with the HDCP aspect of HDMI, I would expect to get the ostensible benefits, too.Not that I care much about this subject being a bit OT for this thread, but thought I'd mention that you might get more input on your problem by posting in the broader "Official 6412 thread (http://www.avsforum.com/avs-vb/showthread.php?p=10103864#post10103864)."

Also thought I'd mention that I am using HDMI exclusively for both video and audio through a Pio Elite 72 AVR to a Panny 42" HD plasma. There is always a brief interruption of both video and audio on any channel change (1 or 2 seconds) and even longer when going from HD to SD, or vice-versa, while the signal resyncs (1-3 seconds). BUT I have not experienced the problem you describe on playback of recorded or time shifted shows.

Perhaps it's firmware related (I am on V16.20) but could also just be a bad box. Why not exchange it and see if that helps?

Not sure I quite agree with the OT call, given the fact that I believe this is all related to buggy firmware in relation to HDMI/HDCP on the STB. but whatever.

I actually just got the box not too long ago. It has the 16.20 firmware on it. Given the fact that 4 different people, including yourself, using 4 different HTRs are all experiencing roughly the same problems, I think it points to the fact that Motorola still has a ways to go to make this box all it should be for the HDMI connection.

I shudder to think what's going to happen when/if Comcast and Tivo get the Tivo front end on this thing.

I too recently updated my 64XX to a 3416 and changed from a DVI only connection to an HDMI connection. My old setup worked flawlessly with the exception that I had a phase one box and it overheated and hung up all the time with remote control issues. The 3416 has performed excellently with this:

ONE EXCEPTION My TV does not like the HDMI input from the DVR I have to either power off and on the DVR AFTER the tv has been turned on (try powering your dvr off and on while its recording something) OR kill myself reaching behind and unplugging the HDMI cable and replugging it back in. Either way will establish the HDCP handshake but you have to do one or the other. You cant just turn on the TV and watch. Lots of other people are experiencing the same problem and it seems the only solution is to wait for the 16.35 firmware update in your area and hope it fixes this one!

Anybody know when Atlatna, GA is getting the 16.35 firmware?

Firmware 16.35 upgrade
My local TWC franchise is testing 16.35 and allowed me to do a user test. So far the results are very positive. The HDCP problem when connecting to a surround sound via an HDMI cable is resolved. So far we have not had any occurrences of the loss of sound that frequently occurred after rewinding or fast forwarding. You can now setup multiple Favorites lists, i.e. for different family members, and switch between them.

I've updated the wikibook to describe how to setup the multiple lists and how to switch between them. http://en.wikibooks.org/wiki/How_to...orola_DVR/Setup

Bernie

Is anyone else in Los Angeles with Time Warner Cable? I spent an hour going around in circles with the idiot tech on the phone who had no idea what I was talking about. He said they'd have to send a technician out with a new box. I explained that it's not a box issue, it's the software/firmware and that it is something they download/push from the headend to update all the boxes. HELP.

My source says the fix is in - HDCP fixed and approved for deployment. The best way to get the fix is to get a Cable Card set-top - these all have the fix and have to be deployed by end of June. It's fixed in other units but up to local area when it gets delivered.

Anyone know how feasible it is to just take my DCT6412 box into the local office and request a Cable Card box?

Anyone recently get a Cable Card box and verify the fix?

Is anyone else in Los Angeles with Time Warner Cable? I spent an hour going around in circles with the idiot tech on the phone who had no idea what I was talking about. He said they'd have to send a technician out with a new box. I explained that it's not a box issue, it's the software/firmware and that it is something they download/push from the headend to update all the boxes. HELP.

You may have better luck through the online method of communicating with them and asking them to forward your request to the Regional VP of Engineering or the Regional Operations Manager. Those people will understand the issue. The Customer Service people are not expected to deal with firmware and are not trained in what it even is.

The technical management will understand. They can also contact their national support teams and also their Motorola rep. You might even suggest that they contact their peers in the Dallas area who are very familiar with the issue - and were very helpful in my case.

To upgrade your box they must also bring their headend equipment up to the right level of support, and they must get their version of all the iGuide software at the right level. They need to upgrade both the firmware to 16.35 and then the iGuide software in your box to work with the new firmware.

I got the update 5/28/07 16.35 and it works Great!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


By the way i am in southtexas

My source says the fix is in - HDCP fixed and approved for deployment. The best way to get the fix is to get a Cable Card set-top - these all have the fix and have to be deployed by end of June. It's fixed in other units but up to local area when it gets delivered.

Anyone know how feasible it is to just take my DCT6412 box into the local office and request a Cable Card box?

Anyone recently get a Cable Card box and verify the fix?

Oh great great news!
Came home tonight, flipped on TV to see Cle/Det game. Hit the guide and something looks different (icon sizes). Go looking at firmware and VOILA 16.35.
Drool starts to form rapidly on my quivering lips.... Could this be.... I haven't changed the box but...

Quickly drain my beer, start yanking cables, redirecting from DCT6412 into AVR, reprogram AVR and VOILA!!!!

HDMI works through my AVR now! No more optical cable.

I am very pleased. Did I say it works now - hdmi and hdcp - cablebox -to - avr -to - TV - all HD!!!! it WORKS it WORKS it WORKS!

And our friends at TWC delivered as promised. Engineering folks kept me in the loop, said it would be ready for June. Got it 5/31 delivered as normal via local (Dallas) update - same box, no cable card, and it works!

Now I have to figure out my Logitech/Harmony id/pwd to reset my Harmony remote to remove a useless step....

Can I interest anyone in an optical cable? B^)

Wow, thats great news. I tried it today and it worked for me too!!! Now finally my all HDMI setup is complete.

Wow, Cox cable in RI just updated their dvr to firmware version 16.38. Finally I can hook up my dvr to my yamaha 6090 with hdmi. Back a few months ago I complained and got to talk to a supervisor and she promised it would be in late March to April, I guess better late than never. Finally an all hdmi setup.

Wow, Cox cable in RI just updated their dvr to firmware version 16.38. Finally I can hook up my dvr to my yamaha 6090 with hdmi. Back a few months ago I complained and got to talk to a supervisor and she promised it would be in late March to April, I guess better late than never. Finally an all hdmi setup.It's been more than 15 months since we started this thread, but based on this post and a few others recently it sounds like most cable systems are finally getting up to date with later firmware/software that allows connection to HDCP repeaters. That's great to hear! :) Hang in there those of you who haven't been upgraded yet. Sounds like progress is coming more and more quickly. Maybe someday soon we can close down this thread and ALL just simply enjoy the advantages of an 100% digital HT setup. :D

Suddenlink in Pflugerville Texas has updated customer boxes with 16.35. I like some of the new features (bold letters on unwatched recordings, grouping recordings and iGuide sort options). I don't like the extra confirmation dialog box to delete a recorded show.

Now that we all have the proper firmware version I have ran into another issue. While I am waiting on a response from Time Warner I was wondering if anyone had a solution. It looks like my hdmi port has been disabled through software. Whenever i go into the setup menu under dvi/hdmi it shows the port as turned off. Does anyone know if there is a code to reactivate the port.

Thanks,

Now that we all have the proper firmware version I have ran into another issue. While I am waiting on a response from Time Warner I was wondering if anyone had a solution. It looks like my hdmi port has been disabled through software. Whenever i go into the setup menu under dvi/hdmi it shows the port as turned off. Does anyone know if there is a code to reactivate the port.
I haven't had to do anything to mine, so can't answer directly. But maybe a post in the official 6412 thread (http://www.avsforum.com/avs-vb/showthread.php?p=10772001#post10772001) would get more eyeballs on the problem and possibly a better response.

Today COX dropped off a DCT6412 III and HDMI does not work with my Westinghouse 42" 1080p LCD - it says something about HDCP Authentication Failed. Do I have any hope? The firmware is 16.38. I also wanted to mention that I just moved so I had to switch from Time Warner, I believe I previously had a 6412 (looked the same) and HDMI worked just fine!

Today COX dropped off a DCT6412 III and HDMI does not work with my Westinghouse 42" 1080p LCD - it says something about HDCP Authentication Failed. Do I have any hope? The firmware is 16.38. I also wanted to mention that I just moved so I had to switch from Time Warner, I believe I previously had a 6412 (looked the same) and HDMI worked just fine!

Well I tried everything and finally gave up. I went to a COX store and traded in my old 6412 for a brand spanking new 3416 - this thing looks awesome and HDMI works like a champ! They said it came out last week.

http://www.cybertheater.com/wp-content/uploads/2007/02/motorola_dch3416_440.jpg

I have the Onkyo TX-SR604, and I get the same delay. I typically only see it when I go from an HD broadcast to a non-HD broadcast or vice-versa. But I sometimes "lose signal" for as much as 5 seconds or so when I'm skipping forward on a recorded or time-shifted program.

I have a friend who just hooked up his Comcast box and Pioneer HTR via HDMI, and he's reported similar delays.

Did you ever get this working?

I just tried setting this up with my brother this afternoon, and we got lost signals pretty randomly when flipping channels. This was with the Onkyo TX-SR604 and a Samsung HL-S5087W TV.

I have the 6400 Motorola set top box running 16.35. When I try to connect it to Onkyo 605 receiver via DVI/HDMI cable, I still get the HDCP Repeater error: http://i1.tinypic.com/2yv4g9x.jpg

Any suggestions?

I have the 6400 Motorola set top box running 16.35. When I try to connect it to Onkyo 605 receiver via DVI/HDMI cable, I still get the HDCP Repeater error: http://i1.tinypic.com/2yv4g9x.jpg

Any suggestions?That's strange for FW 16.35. I don't have the Onkyo so can't be of much help other than to suggest all the normal troubleshooting actions which you have probably already tried. Cold boot the Moto box, check the HDMI cable, call Onkyo to see if they have it as a known issue (perhaps a firmware upgrade is needed for the Onkyo?), etc.

This thread is pretty much dead so you might get more/better answers in either the official Moto 6412 thread (http://www.avsforum.com/avs-vb/showthread.php?t=464986)or the Onkyo 605 owners thread (http://www.avsforum.com/avs-vb/showthread.php?t=854964). Good luck.