View Full Version : DCT6412 III not recording properly?


Babaganoosh
04-30-09, 12:57 AM
I am having an odd problem trying to set up a recording on my DCT6412 III.

The program I am trying to record is the Mets/Phillies game on FOX this Saturday afternoon. When I set up the recording - either by bringing up the channel guide, navigating to Saturday at 2:30, and hitting record, or by searching for all programs called 'MLB Baseball' and choosing the one I want from that list - I get this:

- The upcoming program appears in the Scheduled Recordings list.

- When I then bring up the Guide and go to Saturday at 2:30, the box for 'MLB Baseball' at that time is highlighted in red.

- But when I search for 'MLB Baseball', the specific entry for the game I want to record is NOT highlighted in red. I know it should be. Why isn't it?

And what's weird is this is the only episode for which this happens! I tried setting up recordings for other games, and when I do that, the episodes will highlight in red when I search for 'MLB Baseball'. It's only for this one specific episode that it doesn't happen.

Now I have a dilemma...I don't know if the game I want, will actually record or not. I figure it's gotta count for something that the game appears in the 'Scheduled Recordings' list, and that (in the channel guide) the box for this game is highlighted in red. But why wouldn't the search function also show it as highlighted? And why only for this specific game? :confused:

I know it's not a space problem. I only have one recording on my entire DVR at the moment, and it's only 1 hour of SD programming. (The game I am trying to record is in HD.)

EDIT: Well, this is really weird. Apparently it's a *channel* problem. Just for laughs, I set a season pass recording for 'MLB Baseball' to record every episode. All of the entries lit up - *except one channel*, which happened to be the one I wanted to record from. Anyone can explain? :confused:

ANOTHER EDIT: Never mind. The program I set to record, *is* recording as we speak. It must be some kind of display problem. :confused: