Click Here to visit Embedded Automation - mControl
More on SDV Tuning Adaptors and OCUR - Chris Lanier's Blog

More on SDV Tuning Adaptors and OCUR

Dave Zatz posted some of the first photos of the upcoming SDV Tuning Adaptor (TA) today and it brings up some interesting questions on whether or not they will work with OCURs on the PC.

First, let’s take a step back to last year when I asked CableLabs if the Tuning Adaptor (formally Tuning Resolver) would work with OCURs.  The reply I received was “we [CableLabs] are working toward a two-way solution now that we have UCDP covered and we have not focused on this intermediate step.”  This was pretty clear to me that OCURs were not being targeted for the TA and that BOCRs would have to be the next step.  (As a side note, I’m also still questioning if UDCP [covers TiVo, etc] and OCUR [PC-only spec] can be used interchangeability.  The reply above told me ‘no,’ as if UDCP is covered and OCUR is not being focused on then OCUR is not UDCP.)

Cut to last week, Ben from EnagadgetHD got a completely different reply with CableLabs saying “The CableLabs specifications for the Tuning Adapter and the UDCP application extension do not technically prevent use with an OCUR.”  This was after I checked out the TA specs to find OCUR not mentioned at all.  So now it sounds like while CableLabs is not focused on TA for OCUR, it could be done.  However, it would be in the hands of ATI/AMD to provide a firmware update which is required for any device to work with the TA.  That's not the end of this story though.

Now that we have pictures of the TA I’m finding other problems that could relate to OCURs.  The TA specs state that the UDCP “USB interface SHALL be the USB type A receptacle.”  Problem?  OCURs have type B USB only.  Could this be fixed with a cheap USB adaptor?  It is technically the exact same if you where to use a USB type A to type B adaptor, but this is something interesting to think about.  As stupid as it sounds, you have to follow the specs set by CableLabs even for something as small as a USB connector type.  This also brings up an issue with internal OCURs, which don't have an external USB aspect at all.

The next issue revolves around USB again, how exactly do you connect an OCUR to the PC after you have gone through the TA?  Checking the block diagram, as well as the back of the Motorola MTA700 TA, USB from OCUR to TA would result in a closed loop.  Since the TA and OCUR operate independently of each other, I believe the USB connection must be from OCUR to PC and not from TA to PC (else if wouldn’t go through the CableCARD).  The only way I could see this being fixed is if ATI/AMD provided a two-way USB switch-like device that provided a USB connector (type A) to the TA, and then a second USB connector (type B) for the PC.  As a part of the needed firmware upgrade, allow the type A connector to only commicate with the TA, and the type B to the PC.

image

Where does this leave us?  Nowhere really.  In my mind things are not matching up for TA with OCUR, but AMD/ATI says they are “in discussions with all the relevant parties to address the issue of Switched Digital Video.”  Whatever that means is your answer to this question.  Does it mean TA, or does it mean BOCR?  Only time will tell.

Published Mon, May 19 2008 19:58 by chrisl

Comments

# re: More on SDV Tuning Adaptors and OCUR

I'm sorry Chris, but I'm totally not with you on this one. Although I agree it is entirely possible that the Tuning Adapter will never work with VMC, your USB reasoning is not plausible.

All they have to do is plug the USB cable from the TA into the PC. Why would the TA need to go through the CableCARD? All that needs to happen is Windows needs to request the frequency from the TA and then instruct the DCT to tune that channel.

I supposed the TA needs some sort of security identifier to be permitted to communicate on the network, but I'm not sure if the FCC mandates it be separate like a normal STB. And if it does, then I'm not sure why it couldn't communicate with the DCT via the PC.

Either way, only time will tell.

Monday, May 19, 2008 9:17 PM by Ben Drawbaugh

# re: More on SDV Tuning Adaptors and OCUR

Ben, your thinking backwards.  Everything you said above is kind-of opposite how TAs work.  Take another look at the block diagram and then remember that the USB connection in the block is from the TA (which has one USB) to the UDCP (which has one USB).  This leaves no USB connector from OCUR to PC.

I'll shoot you an e-mail with a bit more, but going from TA to PC does nothing at all.  Without going through the CableCARD, you can't tune anything.  Windows doesn't communicate with the TA, the OCUR would.  

Monday, May 19, 2008 10:18 PM by chrisl

# re: More on SDV Tuning Adaptors and OCUR

I hear what you're saying Chris, but since the DCT is basically just a USB network device as far as Windows is concerned, there is a good chance the TA will be the same, and if so, then the DCT and TA can communicate over IP via the PC.

The diagram doesn't apply because it is for UPCPs which there are no external version of.

Tuesday, May 20, 2008 10:52 AM by Ben Drawbaugh

# re: More on SDV Tuning Adaptors and OCUR

Chris, you may want to check out the following story...

www.engadgethd.com/.../motorolas-mtr700-tuning-resolver-edges-closer-to-release

According to motorola this SDV tuning adapter will work with any cablecard tuner.

Saturday, May 24, 2008 7:05 AM by Al

# re: More on SDV Tuning Adaptors and OCUR

No, the TA will not work with any CableCARD tuner.  It doesn't say that in that story (which is a month old BTW).

Saturday, May 24, 2008 9:14 AM by chrisl

# re: More on SDV Tuning Adaptors and OCUR

Huh... that's funny... the cable show notes about the motorola tuning resolver linked to the post I listed... at the time I posted that story had an additional line that said it would work with any cablecard device.

I think someone went back and did a little editing.

I know it said it cause I read the thing 3 times just to make sure I wasn't seeing things.

Sunday, May 25, 2008 10:21 PM by Al