Comcast, Xfinity and so long Firewire

[MacDaddy]

This may not be the right forum to post in, so feel free to move if appropriate.

I normally don't pay a lot of attention to the Comcast announcements, other than to prepare myself for chasing the channel lineups as they play whack-a-mole with the freqs. I didn't expect a lot from their XFINITY rollout - perhaps the possibility for them to introduce a new logo.

Last night I received the latest upgrade from Comcast. All of sudden I can't get my firewire channel changes to work. I monkey with the drivers to see if I can isolate what went wrong. Finally I get the bright idea to bring up the SA3250HD configuration pages and find that the 1394 port is disabled. A pain in the a$$ to get here, but I'm sure a quick call to tech support can get it turned back on.

I get the never-ending run around in the call center. Eventually I get it escalated to someone who actually knows what Firewire is and acknowledges that the 1394 port does in fact exist on the STB. When I ask to get it re-enabled, I'm told that the feature was never offered, never supported and that they no longer respond to it.

I was not a happy camper

Does anyone know where I can find info to locally enable the Firewaire port? And if you're in Houston and using Firewire channel changing, be ready.

[evilpenguin]

You may just try and swing by Comcast and swap our your cable box before you panic too much.

[MacDaddy]

I hear you. When I had a prior 3250HD go bad, the replacement did not have 1394 enabled. I took it back and got the current one I have lived with for a couple of years now. I've heard on other boards that Scientific Atlanta had a number of boxes where the ports were not terminated (as opposed to firmware activation).

My concern this time is the statement from the rep that the Xfinity rollout will continue to all boxes, that firewire support is expressly disabled, that it was never intended as an offering, no support, no backout, no way out.

I'm roaching through the boards now to see if there is some local configuration option that can get me back.

Or maybe this is the universe telling me to get the CETON:-)

[videolog]

Has anything been said about Sage officially supporting cable card? I think the cable companies are writing on the wall, if you know what I mean.

[MacDaddy]

There's SageMCTuner and SageDCT that show promise. I would love to see what the SiliconDust Prime could do.

Difficult for me to see what advantage the Cable companies get by deactivatiing Firewire. While I understand the DRM paranoia, there was not much use for more than channel changing. Just another reason to let Direct, Dish or Uverse in the house. Sure wish FIOS was around here.

Even cable card would lose them the rental of the STB. Dumb.

[sleonard]

At one time the cable co's were required by law to provide FW if asked for it. There were even posts here that cited the exact FCC regulation. I remember because I used it to get Cox to provide FW ports on my boxes.

Did that change?

S

[basset]

This just happened to me today, comcast in Forsyth, Georgia. Update to cable box completely disabled firewire channel changing. I can still record via firewire, but no channel changing. No matter what I try .. channel.exe with all permutations and even tried SageChanger :(

This is not nice ... not sure where I'll find a USB-UIRT in one day :(

[UgaData]

I have had the firewire (1394) ports turned off by the Cable Co. before.

If an IEEE 1394 exists on a cable box it is suppose to be enabled and available for the the consumer to use. (this doesn't mean they can't 5C anyone though.)

When I explained the problem with the 1394 port being turned off I was met with a blank stare (Huh, what is a firewire/1394 port? never heard of it.)

Eventually, after escalating the issue, and still without admitting that they knew what firewire/1394 was, it was recommended that I exchange the STB for another one.


By the way, have you checked the output from "channel -v" to verify nothing has changed?
If your using channel or channelw for channel changing you can alternately use the "-n" option with the MAC address of the STB.
Using the MAC address should work even if the enumeration of the STB changes.

[cumak]

At one time the cable co's were required by law to provide FW if asked for it. There were even posts here that cited the exact FCC regulation. I remember because I used it to get Cox to provide FW ports on my boxes.

This post (http://forums.sagetv.com/forums/showthread.php?p=348435&postcount=1713) points to the FCC rule that you're referring to. However, it's 2 years old and I don't know f anything has changed since then.

[sleonard]

Good find. I can't say for sure if that FCC rule is still valid but I think I would have heard something around here or AVS if it had changed.

If I was the OP I'd call up the cableco and cite this rule and tell them 'sorry, but you're required by law to support the firewire port.'

S

[basset]

I am trying to reason with comcast ... as expected ... not really getting anywhere. I'll keep on trying.

I tried all the things mentioned above ... channel -v ... everything is as it was before. The firewire ports seem active but the box doesn't respond to the commands although channel.exe returns that it worked.

I am not the only one seeing this, mythtv users in texas has also seen this in the last 2 months. It seems the new xfinity update is messing up the firewire ports.

I also tried channel -n, same effect. Now I have to wait a week for a USB-UIRT to arrive .. not easy to record with 2 tuners and no channel changing :(

[evilpenguin]

What model cable box do you have?

[PLUCKYHD]

I am 90% percent positive the FireWire law is still valid. Avsforums would have blown up if it changed because of the dvhs users over there.

I find usually a escalated call and a threat to file a compliant with the FCC does the trick. Simply make sure you have a higher up and manager. Ask for their name because you will be filing a compliant with their name mentioned about them violating said law. Read the law to them if they still refuse do exactly what you said and file a FCC complaint online. It takes a month or so but once the FCC gets to your case you will be amazed how fast the cable company gets you a box with FireWire working.

[MacDaddy]

Started the complanit process as suggested by the Firewire forum about two weeks ago. Comcast actually rolled a tech to come out and verify my issue (poor guy). I'm not actually recording via Firewire, so the 5C isn't as much an issue, but I did use it for channel changing. I've dug out my old USB-UIRT and its working well, just no feedback. Which brings up the next issue in the Houston area Xfinity rollout......

Since the first day of the "upgrade", I have lost 639 (TCM), 659 (Comedy Central), 667 (truTV) and 668 (MSNBC). It has been a total Charlie Foxtrot in navigating the exponentially increasing levels of incompetence/indifference in trying to resolve the issue. They have rolled a tech twice (who continues to verify no equipment/line issues) who have both admitted it's probably a local programming issue. They claim they will submit a problem ticket through their own channels, but so far it has been ineffective.

Oh the joys of being a monopoly.

[Monedeath]

This post (http://forums.sagetv.com/forums/showthread.php?p=348435&postcount=1713) points to the FCC rule that you're referring to. However, it's 2 years old and I don't know f anything has changed since then.

Call/email the FCC and ask them?

Also let them know that Comcast is saying they don't need to support it anymore and you're wanting to verify that what they're saying is the case.

[stevech]

Call/email the FCC and ask them?

Also let them know that Comcast is saying they don't need to support it anymore and you're wanting to verify that what they're saying is the case.
FCC - deaf ear.
County or City office that grants easements and controls the quasi-monopoly... they respond if enough formal complaints are received, people on speakers' agenda at Council meetings, etc.

[mistergq]

I have nothing to add other than to wish you good luck as I think I have woken up in cold sweats fearing this happening to me.

I would also suggest that you should also probably go contact local county/city regulators as well as FCC. I have a feeling that if the FCC gets enough complaints from comcast subscribers, this will just get fixed.

[bcjenkins]

I don't have Comcast but during a recent switch to Insight Cable, I had issues at the call center as well (not related to firewire). I asked for the name of someone in the office of the president who handles complaints and reached out to them via email. I can honestly say that the next day they were very energized to make sure I was a happy camper.

Give this a try: http://consumerist.com/2007/05/contact-comcasts-ceo.html

B

[GbrNole]

i got whacked by the rolling crapout last week and have also lost the ability to channel change with firewire after more than 3 wonderful years of doing just that.

with the ceton card down to 250 bux in a few places now i'm tempted to go to the dark side and use win 7 mc since i have no desire to use satellite or have to channel change with something other than firewire.

not a happy camper at all.... friggin comcast.

[stevech]

Can't use IR (USB-UIRT) for channel-changing?

[mistergq]

Can't use IR (USB-UIRT) for channel-changing?

you could, but once you go firewire...you never want to go back :p

[GbrNole]

ya what mistergq said.

after being pi$$ed off and frustrated i finally managed to get the blaster working with my hd-pvr and while i'm not happy it will hold me over for the moment.

in an impulse i snagged a ceton card and i guess i'll give sagedct a shot and see how bad my local comcrap screws me with the copy once flag - i'd give my left arm for a true sage version of this setup though!