AVS › AVS Forum › HDTV › HDTV Recorders › The Official AVS Dish DTVPal DVR Topic!
New Posts  All Forums:Forum Nav:

The Official AVS Dish DTVPal DVR Topic! - Page 418

post #12511 of 16909
Quote:
Originally Posted by AV Empiricist View Post

Yeah, it's a shame that the Pal has no S-video output. There is no comparison between S-video and composite. My work-around is to route the component output to a Philips dvd recorder and output the Philips S-video to a panasonic dvd recorder. It seems to be as good as a direct S-video connection.

Not familiar with the Philips but why don't you just record on it. Going from component to S-video which is basically only one step up from composite would seem to result in a loss of quality.
post #12512 of 16909
Quote:
Originally Posted by dkreichen1968 View Post

...In the midst of this phenomenon, FCC chairman Julius Genachowski continues to assert that over-the-air broadcasting is no longer needed and consequently should be barred. These assertions are 180 degrees from the reality occurring in living rooms across America. As Antennas Direct's growth demonstrates, the pace of antenna sales are convincingly accelerating as people cut the cord. Viewers appreciate that not only does Digital TV offer improved picture quality, more channels and greater reliability, it's also free to the consumer - an important feature during a time of such economic challenges....

Not to get into politics but my guess would be that they just want to sell the spectrum to cell and other services and so are denigrating the OTA.
post #12513 of 16909
Quote:
Originally Posted by WillN937 View Post
Not familiar with the Philips but why don't you just record on it. Going from component to S-video which is basically only one step up from composite would seem to result in a loss of quality.
Oops , my bad. I was able to use the component output for the Dish 722 Vip. The Pal has no option for 480i via the component and HDMI outputs.

When it was recording properly, the Philips dvd recorder did very well from the component input, but recently my computer has trouble reading the Philips recordings. The reason I run the output through the Philips into the Panasonic S-video is the step down to S-video is much smaller than the step down to composite. The lack of color saturation from the composite input is painfully obvious.
post #12514 of 16909
Quote:
Originally Posted by jrpastore View Post

You're right, the total bandwidth requirement for the TVGOS datastream is a trivial fraction of the total 19 Mbps bandwidth available to every ATSC broadcaster. The problem is not that the TVGOS datastream is hogging the ATSC bandwidth. The problem is that IF the local broadcaster has over-allocated his 19 Mbps and has almost no reserve capacity left in the stream, THEN the ROVI encoder will buffer its TVGOS datastream (guide and clock data) and trickle it out into the 19 Mbps ATSC stream on a "space available" basis (It's like flying standby during during the evening rush, you may have to wait a while). Most broadcasters leave a considerable portion of their 19 Mbps un-allocated, I've seen some up to 25% or more. Our local CBS affiliate typically only has about 1% of their 19 Mbps available as "reserve". These are the kinds of things that can be measured with the free TSREADER-Lite program and an ATSC tuner card (or external USB tuner).

It's been said repeatedly in this thread that CBS stations often or even usually run close to the brink. While some stations in our area have as many as 4 sub-channels, the CBS station has only one (and it's a simple radar display broadcast in SD). Without the need to service many sub-channels, it makes me wonder what they're up to.....
post #12515 of 16909
Quote:
Originally Posted by dkreichen1968 View Post

Both models are made by Echostar, the parent company of Dish. Since Dish no longer markets it there isn't any incentive to upgrade the software until/unless Dish/Echostar starts using them as a streaming device for BlockBuster VOD.

Channel Master/CM now sells it, so whether Echostar markets it or not, from what you've described Echo Star is still the actual manufacturer and supplier to CM. If CM received complaints, I'd think they'd pass the buck up the line to their supplier, Echo Star, as would be done in any seller/supplier situation. Maybe that's naive, or maybe this CBS-related problem is seen by relatively few owners.
post #12516 of 16909
Quote:
Originally Posted by jrpastore View Post

The update from Austin is that this auto-reboot method no longer works reliably so I have stopped using it. I think the timestamps must be skewed sometimes even during prime-time. I say this because even the manual intervention of changing time-zone (or zipcode) and then changing it back, no longer works reliably either. I have attempted several times in the middle of prime-time, with no affect on clock skew. I know I should fire up TSREADER to confirm what's really happening, but I haven't bothered.

What used to work in Austin is what Mark is describing to you in his post. Under those conditions, timestamps from about 5pm to 11pm were not skewed while timestamps at all other times were skewed. The clock smoothing algorithm in the DVR prevents it from taking immediate advantage of the clean timestamps starting at 5pm so what was needed was a way to force the DVR to drop its TVGOS time lock and re-acquire it during the "clean zone". This could be done manually using the zipcode or time zone trick but that required manual intervention every day sometime after 5pm but before the desired evening recordings started. Mark suggested a way to automate this process using the auto-update feature and that worked pretty well for a while...

So to answer your question, no harm will come from triggering the auto-reboots, but if you've found a solution that doesn't require it I certainly wouldn't recommend it. Also, if the WUSA clock skew issue is some completely different animal than the KEYE clock skew issue, the auto-reboot solution might not do you any good anyway. But it terms of recommended timing the auto-reboot would have to happen AFTER the "clean zone" of unskewed timestamps started (thought to be around 6:30pm now), but at least 5 min BEFORE the intended recording starts. Doing the reboot after primetime would be pointless. You might fix the clock for a brief time, but it will be hosed up again by the following morning and it will remain hosed up when your intended recordings begin that following evening. Confusing I know...

Okay, updates are now disabled and spot checks against a NIST clock show that all it still well with the clock (always within a few seconds). By watching what happens when removing from the channel listing either the CBS station in Wash DC, Baltimore, both, or neither, it appears my TVGOS data is now coming from Baltimore. Evidently that station is not over-allocating (assuming that's what's truly going on with the Wash DC area CBS station).

Another matter is that we don't see much future TVG programming information, nothing beyond maybe 2 days. At first I thought this might be a byproduct of having the TVG data source coming from a remote city. However, I'm no longer sure since this may have been the case all along, even before this clock fiasco began and when our TVG data came from the local CBS affiliate WUSA. The problem is that we used to very infrequently check the advance programming info so we can't be sure.
post #12517 of 16909
Quote:
Originally Posted by WillN937 View Post

I have had a number of people like telephone repair men and other technicians who see my antenna and assume I have some sort of transmitter. I said something to one person about free HDTV and he assumed I was stealing cable some how.

Funny! But also sort of sad!
post #12518 of 16909
Quote:
Originally Posted by mabuttra View Post

It is easy to tell whether enabling updates is needed or not. Turn on the DTVPal at 6:15 pm. If the clock is right, then no 6:30pm reboot is needed. You could even do this two days in a row, just to be certain.

Mark

The clock is always right (now), so I've disabled updates.
post #12519 of 16909
Quote:
Originally Posted by J-D-H View Post

It's been said repeatedly in this thread that CBS stations often or even usually run close to the brink. While some stations in our area have as many as 4 sub-channels, the CBS station has only one (and it's a simple radar display broadcast in SD). Without the need to service many sub-channels, it makes me wonder what they're up to.....

Number of subs does not correlate very well with bandwidth utilization. I've seen stations with 3-4 subs and 10-20% reserve capacity. I've also seen KEYE which has only one sub and only 1% reserve capacity. I haven't seen any references to CBS affiliates routinely running "close to the edge", can you point me to one. Actually we've turned up just the opposite, a published rule from CBS that places caps on the bandwidth that their "owned and operated" local broadcasters can allocate. Unfortunately KEYE is not "owned and operated" by CBS.
post #12520 of 16909
Quote:
Originally Posted by mabuttra View Post

Your channel estimate is off by about 500. The DTVPal is one of the few TVGOS devices that does not support cable. Cable channels can number in the hundreds. The TVGOS data includes all cable channels as well as OTA channels. Even though I'm OTA only, my channel lineup on the Sony DHG contains over 500 channels.

Mark

So the CM-7000PAL must always fetch 500 times more data than it needs? If CBS station over-allocation is what's going on here, it's a shame the TVGOS data isn't sub-divided into separate OTA and cable segments so the DVR could get only what it needs.
post #12521 of 16909
Quote:
Originally Posted by J-D-H View Post

Okay, updates are now disabled and spot checks against a NIST clock show that all it still well with the clock (always within a few seconds). By watching what happens when removing from the channel listing either the CBS station in Wash DC, Baltimore, both, or neither, it appears my TVGOS data is now coming from Baltimore. Evidently that station is not over-allocating (assuming that's what's truly going on with the Wash DC area CBS station).

Another matter is that we don't see much future TVG programming information, nothing beyond maybe 2 days. At first I thought this might be a byproduct of having the TVG data source coming from a remote city. However, I'm no longer sure since this may have been the case all along, even before this clock fiasco began and when our TVG data came from the local CBS affiliate WUSA. The problem is that we used to very infrequently check the advance programming info so we can't be sure.

If you have NO guide data out past 48 hrs for ANY channel then I think you're probably looking at PSIP data. I'm not sure that the presence/absence of the TVGuide logo in the top-right corner of the guide display is an accurate "real-time" indicator of the guide source data. I think there may be some lag between when you lose TVGuide data and when that logo disappears.
post #12522 of 16909
Quote:
Originally Posted by AV Empiricist View Post

After the official analog-to-digital changeover, Channel 7,9,11 and 13 (ATSC broadcasts) returned from UHF to their VHF High Band frequencies. All of my antennas are well designed for the UHF band but all have been demonstrated to fall-off as frequencies approach the VHF Band. In spite of this, reception on 7 & 9 are perfect because I'm only 12 miles from the DC towers. Channels 11 & 13 are 27 miles away. That's a significant distance for an attic-mounted UHF antenna to reach into the VHF High Band. With perfect positioning, 13 registers an SS of 86. (2,45,& 54 can hit 98-100) . But to optimize other channels, I accept a clean SS of 73. There's no trouble receiving my Guide info from the weaker station.

I would hope the Pal was designed to lock onto the time according to zip code. People near the time zone boundaries might otherwise be stuck with the wrong time from a strong signal across the boundary.

It will be interesting to see how this resolves for you and gary-in-dc.

I understand how the channel shuffle happened with ATSC and was only referring to the two CBS stations we've been discussing, Ch 9 and Ch 13. With our rooftop beam pointed north, we now get Ch 13 with a strength of around 92. With Wash DC off the back, Ch 9 is almost as good, usually around 88 or so.

Just changing the zip code to Baltimore did nothing to help our clock error here. Maybe some other factor crept in, something I'm unaware of, but it sure looked like a signal strength issue was at play since only rotating the antenna 180 degrees to face Baltimore "fixed" the clock.
post #12523 of 16909
Quote:
Originally Posted by dkreichen1968 View Post

Antennas Direct is only one company. (Channel Master, AntennaCraft, Winegard, Digitenna, etc.) They probably do have the most aggressive marketing though.

Thanks for sending that very interesting article!

If the other stats are true, I can't believe the out-of-touch words of the FCC chairman. How clueless. What he said makes me wonder about his agenda (selling bandwidth? -- that's what's threatening with some amateur radio bands). OTOH, if it's lack of knowledge, unbelievable as that might be, I hope someone educates the man.

The other aspect of OTA broadcasting making a turnaround and becoming more popular might be that we users might finally begin to see some quality TV shows for a change. Can't wait!
post #12524 of 16909
Quote:
Originally Posted by jrpastore View Post

Number of subs does not correlate very well with bandwidth utilization. I've seen stations with 3-4 subs and 10-20% reserve capacity. I've also seen KEYE which has only one sub and only 1% reserve capacity. I haven't seen any references to CBS affiliates routinely running "close to the edge", can you point me to one. Actually we've turned up just the opposite, a published rule from CBS that places caps on the bandwidth that their "owned and operated" local broadcasters can allocate. Unfortunately KEYE is not "owned and operated" by CBS.

Of course you're right about the bandwidth (lots of variables!). My point was only that a station with many sub-channels might have more of an incentive to stretch the limits of their FCC bandwidth allocation than would station with few or no sub-channels. Regardless, I'd still like to know why CBS feels the need to play these games (if in fact they are).
post #12525 of 16909
Quote:
Originally Posted by jrpastore View Post

If you have NO guide data out past 48 hrs for ANY channel then I think you're probably looking at PSIP data. I'm not sure that the presence/absence of the TVGuide logo in the top-right corner of the guide display is an accurate "real-time" indicator of the guide source data. I think there may be some lag between when you lose TVGuide data and when that logo disappears.

It's not just the logo. The menu system's time setting screen is ~always~ grayed out and says "time obtained from TV Guide". This has varied exactly once when I deleted both CBS stations (WUSA and WJZ) from the channel listing. On that occasion only, the time setting screen became available, un-grayed out, and no longer said TV Guide was the source.

With all the above, we seldom if ever see TV Guide data beyond 2 days.
post #12526 of 16909
Quote:
Originally Posted by J-D-H View Post

It's not just the logo. The menu system's time setting screen is ~always~ grayed out and says "time obtained from TV Guide". This has varied exactly once when I deleted both CBS stations (WUSA and WJZ) from the channel listing. On that occasion only, the time setting screen became available, un-grayed out, and no longer said TV Guide was the source.

With all the above, we seldom if ever see TV Guide data beyond 2 days.

jrpastore is right. For whatever reason, you are not getting TVGOS listings. The data you are seeing is PSIP only. TVGOS data is always 8 complete days. It is probably getting the clock from TVGOS, and it may even show the TV Guide logo, but you are not getting listings.

I have had my DTVPal for almost a year now, and for the first time last Tuesday, I turned it on, checked the end of the schedule, and found 100% 'No Information'. I then moved back 24 hours, and stilll 100% 'No Information'. I moved back another 24 hours, and had listings. I checked my Sony DHG, and it had 100% listings across the board. On the Pal, it still showed the TV Guide logo, and that the clock was set by TVGOS, but it was not getting new listings. I changed the zip code to another zip code in my area, and the next morning listings were back to 100%. On other TVGOS devices (with Gemstar/Rovi written software) the zip code change causes the device to start searching for a host channel. This sometimes helps when the device becomes confused, and although it still reports the correct host channel, it isn't getting listings. Who knows what the DTVPal software does, but in this case it seemed to work.

Mark
post #12527 of 16909
Quote:
Originally Posted by AV Empiricist View Post

To differentiate between TV Guide listings and PSIP, I simply looked 4-7 days forward. No flaky info disappearing acts have ever occurred in my guide listings.

All three dvrs are keeping perfect time. (One is still set to a Baltimore zip as a precaution). So, among three of us (i.e., gary-in -dc, J-D-H, and me), the attempts at resolving the time skew for DC have met with dramatically different results. All of my antennas are essentially UHF. At 12 miles from VHF 7 & 9, it's no problem but VHF 11 & 13 are more than twice the distance so it takes more effort to bring them in cleanly (with UHF antennas). There could be more than one source of this time skew problem, but I'm suspicious it has to do with each Pal's schedule for time updates. Since one of my dvrs never skewed and another was corrected by changing my zip back and forth, is the solution to revert to a DC zip at an optimum time of day? My update option is disabled and has been forever. Why ask for trouble?

J-D-H, since my time skew was resolved with 0 reboots, I suspect resetting the zip is the key element here. The prima-fascia evidence is that signal quality may be a factor in setting the TV Guide station but signal strength isn't. For me, 9 was at 98-100 and 13 was at 73. I picked up the Baltimore time and Guide on the first try without a hiccup. Although, when I attempted the same exercise a while later, the change wasn't immediate.

If you're picking up a clean enough signal from 13, I doubt the DC time will wander back of its own accord. My guess is, if you change the zip back at the right time of day, the DC time will be fine. I'm still wondering if gary-n-dc would benefit from some signal attenuation.

I have been rotating my antenna slightly away from my DC line of sight but I think I'm going to rotate it around to Baltimore and try your tip on setting the Baltimore zip to get Ch 13 to provide TVGOS. I also don't want to delete Ch 9 from my lineup, so I'll see how it works.
post #12528 of 16909
Quote:
Originally Posted by mabuttra View Post

Your channel estimate is off by about 500. The DTVPal is one of the few TVGOS devices that does not support cable. Cable channels can number in the hundreds. The TVGOS data includes all cable channels as well as OTA channels. Even though I'm OTA only, my channel lineup on the Sony DHG contains over 500 channels.

Mark

I agree. I remember first setting up my PAL DVR (using the instructions in the manual for setting up TVGOS - which disables the DVR and turns it into a converter box - not exactly what you got the DVR for!) Anyway, I thought I could keep the old TVGOS screen for my lineup (instead of the boring blue screen we all see) and still use the DVR...you can't!. After waiting 48 hrs. or so, I pressed my TVGuide button on my TV and saw that the guide displayed a lot of incorrect channel entries. Correcting those entries forced me to scroll thru almost 600 different OTA and cable channels! (Obviously, my TV has the old analog TVGOS - which stopped working shortly before the digital conversion - but utilizing the PAL DVR in its' "converter box" mode, it received the post-coversion digital TVGOS data and converted it to analog and sent it to the TV.)
Of course, this was all for naught since I can't use the DVR as a DVR, so I undid it. But the point is, data for over 600 channels now is being sent out.
post #12529 of 16909
Greetings,
In the past several weeks, my DTVPal has been starting to record shows about 2 minutes too early. The results are that I miss the endings of the shows. It does not seem to happen to every show. I have checked the times and all looks correct. What might be causing this? Can I fix this problem? The clock time is coming from TVGOS. The clock time is correct.
Gary
post #12530 of 16909
Quote:
Originally Posted by goddi1 View Post

Greetings,
In the past several weeks, my DTVPal has been starting to record shows about 2 minutes too early. The results are that I miss the endings of the shows. It does not seem to happen to every show. I have checked the times and all looks correct. What might be causing this? Can I fix this problem? The clock time is coming from TVGOS. The clock time is correct.
Gary

The DVR doesn't utilize Name Based Scheduling, it works as Time based schedule device, so you do set in advance a TIME/DURATION and in case if the show start early or delayed, the DVR will NOT correct your initial schedule, hence missing ending or beginning, etc.
post #12531 of 16909
Quote:
Originally Posted by P Smith View Post

The DVR doesn't utilize Name Based Scheduling, it works as Time based schedule device, so you do set in advance a TIME/DURATION and in case if the show start early or delayed, the DVR will NOT correct your initial schedule, hence missing ending or beginning, etc.

Basically like a VCR.
post #12532 of 16909
Quote:
Originally Posted by P Smith View Post

The DVR doesn't utilize Name Based Scheduling, it works as Time based schedule device, so you do set in advance a TIME/DURATION and in case if the show start early or delayed, the DVR will NOT correct your initial schedule, hence missing ending or beginning, etc.

===========================
Greetings,
But the actual show is not really starting early. If there is a show that is to run, say, from 8pm to 9pm, the TVGOS shows it will run from 8-9. However, the DTVPal start recording at about 7:58pm and stops about 8:58pm. It is not the show that is changing its starting time. The recorder is not starting at the correct time.
Gary
post #12533 of 16909
Set the DVR to record 2 extra minutes.
post #12534 of 16909
Quote:
Originally Posted by goddi1 View Post

===========================
Greetings,
But the actual show is not really starting early. If there is a show that is to run, say, from 8pm to 9pm, the TVGOS shows it will run from 8-9. However, the DTVPal start recording at about 7:58pm and stops about 8:58pm. It is not the show that is changing its starting time. The recorder is not starting at the correct time.
Gary

Oops. My description is still valid, but what happening at your home ... poltergeist !
I would check the default and current schedules setting of the DVR.
post #12535 of 16909
Quote:
Originally Posted by ss_sea_ya View Post

I'd rather miss the beginning of the show rather than the end. Who would want to see two extra minutes of commercials at the beginning, only to miss who the mystery and unlikely killer was!

As for the clock skew, I think switch to B'more zip code did work, just not right away.

With ss_sea_ya from Alexandria, we have 4 people to help gather empirical evidence about the DC clock issue. The guys in Austin seem confident the TV Guide info is broadcast before 6:15 PM. My experience seems to corroborate this notion.

Whenever I had corrupt Guide data on my LG & Sony dvrs, I would reset to a Baltimore zip code and then return to a DC zipcode the next day. When I read about our DC time skew, I checked my CM-7000. It was slow by 5+ minutes.

At about 5:30 PM, I set the zip code (for the CM Pal) to 21210 (downtown Baltimore). The time corrected almost immediately.
Minutes later I reset my zip (close to DC) and the clock almost immediately skewed 5 minutes slow.
Resetting to Baltimore again corrected the time almost immediately.

At about 6:00PM I checked Dish Pal #1. The time was fine.

Then I checked Dish Pal #2. 5+ minutes slow.
Set the Zip to 21210 and the clock corrected almost immediately.
At this point, it was approaching 6:15PM. Resetting the zip to DC resulted in 3+ minute slow.
Going back to 21210 then forth to DC resulted in 1+ minute slow.
It was approaching 6:30PM, when I finalized the 21210 zip but the time correction wasn't immediate. I might have confirmed it later that night, but certainly the next day. Dish Pal #2 is the only dvr that remained 21210 for the last 2 ½ weeks.

Two weeks ago, I reset the CM-7000 to my zip and it has kept perfect DC time ever since. I believe that I reset the zip in the evening.

Tonight at 7:10PM, (in the pursuit of empirical evidence) I reset Dish Pal #2 to my zip. As of 8:50PM, no DC Guide data has appeared and the time is still correct.

These facts may corroborate the 6:15PM witching hour scenario. So now, all three units are set to DC and tomorrow, I will report on the time and Guide results for the Dish Pal #2. My suspicion is that the Pal checks the clock once a day. That is a possible explanation why some machines are still exhibiting a time skew and mine are not.
post #12536 of 16909
Here is some information direct from Gemstar (now Rovi) about how the clock gets set in TVGOS devices. Remember that since Gemstar did not write the DTVPal code, it may use a different method for setting the clock.

Gemstar clock info

Mark
post #12537 of 16909
Quote:
Originally Posted by mabuttra View Post

Here is some information direct from Gemstar (now Rovi) about how the clock gets set in TVGOS devices. Remember that since Gemstar did not write the DTVPal code, it may use a different method for setting the clock.

Gemstar clock info

Mark

Thanks Mark. That clarifies one issue: A device which was sanctioned by Gemstar (post v7) sets the clock by zip code (to avoid time zone errors).

Each day it checks again and adjusts the number of beats per minute.

Is it too much of a stretch to infer: once each day? If not, the firmware could be written with a specific time of day to check, or a specific interval of time between each adjustment. In other words, if you force a zip code reset at a certain time, the latter design, might simply check at 24 hour intervals from that reset. Whereas in the first case, it's out of our domain.
post #12538 of 16909
Quote:
Originally Posted by AV Empiricist View Post

Thanks Mark. That clarifies one issue: A device which was sanctioned by Gemstar (post v7) sets the clock by zip code (to avoid time zone errors).

Each day it checks again and adjusts the number of beats per minute.

Is it too much of a stretch to infer: once each day? If not, the firmware could be written with a specific time of day to check, or a specific interval of time between each adjustment. In other words, if you force a zip code reset at a certain time, the latter design, might simply check at 24 hour intervals from that reset. Whereas in the first case, it's out of our domain.

One advantage to having one of these Gemstar devices is that you can see how many clock sets have happened over time (another advantage is that it shows you the clock set channel so you don't have to guess what station the clock is being set from). Four days ago, I cleared out all the diagnostic data on my Sony DHG. As of tonight there have been 20 clock sets, which means it has been setting the clock about 5 times a day. I agree though that the way that reads, it sounds like it does some kind of calculation once a day, to figure out how far the clock drifts. One thing I have noticed with Gemstar documents, is that they can be kind of vague, and raise more questions than they give answers.

Mark
post #12539 of 16909
Quote:
Originally Posted by mabuttra View Post

jrpastore is right. For whatever reason, you are not getting TVGOS listings. The data you are seeing is PSIP only. TVGOS data is always 8 complete days. It is probably getting the clock from TVGOS, and it may even show the TV Guide logo, but you are not getting listings.

I have had my DTVPal for almost a year now, and for the first time last Tuesday, I turned it on, checked the end of the schedule, and found 100% 'No Information'. I then moved back 24 hours, and stilll 100% 'No Information'. I moved back another 24 hours, and had listings. I checked my Sony DHG, and it had 100% listings across the board. On the Pal, it still showed the TV Guide logo, and that the clock was set by TVGOS, but it was not getting new listings. I changed the zip code to another zip code in my area, and the next morning listings were back to 100%. On other TVGOS devices (with Gemstar/Rovi written software) the zip code change causes the device to start searching for a host channel. This sometimes helps when the device becomes confused, and although it still reports the correct host channel, it isn't getting listings. Who knows what the DTVPal software does, but in this case it seemed to work.

Mark

Maybe I'm getting PSIP clock setting data even though the screen always says it uses TV Guide for the clock. Alternatively, maybe I'm getting only a few days of Wash DC programming because my zip code is set for Baltimore. Either way, it appears I'm stuck where I am as long as I want an accurate clock. That is, as long as WUSA Ch 9 continues to apparently have trouble. From time to time I may try switching the zip code back to Wash DC and see what happens, but given the recent hassles, I believe I'll wait awhile .
post #12540 of 16909
Quote:
Originally Posted by jrpastore View Post

If you have NO guide data out past 48 hrs for ANY channel then I think you're probably looking at PSIP data. I'm not sure that the presence/absence of the TVGuide logo in the top-right corner of the guide display is an accurate "real-time" indicator of the guide source data. I think there may be some lag between when you lose TVGuide data and when that logo disappears.

Do you know whether Baltimore, a remote city from my point of view, transmit extended TV Guide data for my Wash DC area? I believe someone said that they would not, but I'm not sure that this is so.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: HDTV Recorders
AVS › AVS Forum › HDTV › HDTV Recorders › The Official AVS Dish DTVPal DVR Topic!