CBS 1-1 (58-1) down???

[StarvingForHDTV]

I was thinking the switching was a network problem.  They plopped us on the SD feed because that was the only way to get the Packer game on.  They figured Packers were more important than HD.  Then they checked the national feed every so often to see if they were finally done with the commercials and showing the HD Packer game.  Once the national HD feed was showing Packers, we were switched there for good.

At least that's how it appeared to me.  I think CBS caused the problem this time, not our local station.  It's tough to say for sure without open communication from the local station.....

Lousy game anyway.  

I wasn't impressed with the 1080i versus our normal 720p Packer games.  I think there is a difference in camera quality and also camera operators skill levels.

[Malamute]

I had the game in HD.   I found it on satellite with the FTA system.  The satellite the game was on is Intelsat America's 6 at 93.oW,  C-Band transponder 19 CBS East HD national feed.  They also have on tp 21 CBS West HD.  But remember its in DVB format, and it was In The Clear.  I had 99.8% signal strengh on the Intergra reciever hooked to the big dish.  Sorry all of you guys missed the game in HD.

Its been very quiet on the FTA front lately so that's why I haven't posted anything for awhile.

Malamute

[tazman]

Hmmmm... Greenbay Jacksonville,  CBS-58 right?  All I know, I had the game in wide screen on CBS and I could see the sweat rolling off of Favre's forhead when he popped the ref in the shoulder with the football.  The game looked pretty much like HD to me for the whole time that I was watching it.  Of course I didn't get to the TV until the 2nd quarter.  Hey Malamute, you bugger,  I got BIG DISH envy.  Sured be nice if they would put some of those feeds on the Ku side of IA-6.:p

[Gregg Lengling]

I know this is a little late but the network feed from CBS was the problem for the game the other day.  WDJT made a decision to feed SD material until the feed was corrected by CBS.  So needless to say this was not a local problem, but once again further up the chain.