L211 - can't create any OTA timer

[Jim_R]

Problem creating ANY OTA HD timer. After noticing 211, I powered the 921 down as suggested. I then deleted and rescanned all Digital channels. I tried to recreate a weekly timer for WPWR OTA-HD UPN. A conflict with an old timer (setup prior to 211) was detected. I attempted to resolve the conflict by deleting the old timer. The weekly timer (selected from the Guide) did not show a red dot in the guide. I went to the timer screen, and no timers were selected. Ever since, every attempt to setup a timer either through the guide or manually does not function. I can get to the step where you press select to create the timer, but at that point nothing happens. The Create button briefly changes color, but that's it. Any suggestions? - I'm thinking reboot.

[TowJumper]

FWIW: I created a local OTA HD timer and it fired correctly with 2.11.

I also went to my previous timers and set them for the new remapped channels no problem - though none has fired yet - it did let me make the changes. I did power plug reboot per Mark - maybe that will work for you.

[Jim_R]

FWIW: I created a local OTA HD timer and it fired correctly with 2.11.

I also went to my previous timers and set them for the new remapped channels no problem - though none has fired yet - it did let me make the changes. I did power plug reboot per Mark - maybe that will work for you.

My issue was creating a new timer via the guide that led to the conflict screen. The bug appeared after I attempted to resolve the conflict. I rebooted, and can now create timers, but I have a remaining symptom - the indication that a timer has been setup, does not appear in the guide (the red dot in the listing) as it used to. I'm waiting to see if the timer I set via the guide fires at 1:30 Central. They do appear on the timer management screen.

[mcglauch]

I tried creating a OTA HD recording in the guide and it shows it will record from the Dish local channel 7 instead of 007-01. My timer list says 007-01 which is correct. I'll have to see what happens when the timer fires.

[Mark Lamutt]

Ah yes, that was another caveat that I forgot - if you have your local channels downmapped, you may see the red dot show up on those local channels, even if you set the timer from the digital channel. Another effect of mapping the guide data over, and something that wasn't a big enough deal to get fixed before sending this out.

[Jim_R]

Interesting. I looked in the 8000 series for the red dots for the timers I setup using the guide and do not find them. But when I setup a timer using the timer screen (Menu, 7), a red dot does appear in the guide for the correct digital channel.

*edit - I also notice that the search function presents two match items, one for the 8000 series local, and another for a channel number local (e.g. 32 WFLD, which doesn't appear in my guide). I had to edit the timer to change it to 032-01, the digital broadcast for WFLD-HD. If I didn't do this edit, would I have recorded analog?

[Jim_R]

I also notice that the search function presents two match items, one for the 8000 series local, and another for a channel number local (e.g. 32 WFLD, which doesn't appear in my guide). I had to edit the timer to change it to 032-01, the digital broadcast for WFLD-HD. If I didn't do this edit, would I have recorded analog?

I tested for the answer to my above question. My local PBS station WTTW, has it's primary digital channel 011-01 mapped to it's HD programming feed, and normal broadcasting mapped to 011-02. I searched the guide for the next program scheduled, was returned two options, an 8000 listing and a 11 WTTW listing. I set a timer for the 11 WTTW listing, selected a different HD OTA channel and waited. The timer fired up, but an analog station was recorded, not the digital station with the remapped guide data, I was able to continue watching the OTA-HD channel I was switched to while the recording was taking place in the background. I have a feeling that this is going to cause a large number of missed HD recordings. I would have expected that the second listing would have recorded the primary OTA HD channel.

[TowJumper]

Jim_R: It worked for me.

I found the erroneous red button bug also. When I selected an OTA (remaped) item to record, the red button showed up on the remapped SAT (SD) local channel instead. However, the timer DID fire and record on the OTA HD channel - so it seems to not be a big problem.

Curiously, when I edited my existing (pre 2.11) timers to the new remapped HD numbers, the buttons show correctly.

[Jim_R]

Doh - found it. With the (menu, 4, 2, more) View Preferences remap locals set to enable, the remapped locals do not appear in the guide. Disable them and they appear. Unfortunately, when one uses the search feature for a program title, they have the option of recording the 8000 SAT local, or the remapped local, but not the OTA Digital local.

I'll retest, but it seems that when the new OTA Digital channel guide data is used to select a program for recording, the digital channel will record, and the red dot appears on the remapped analog channel (when not hidden). But, when using the Menu, TV Listing, Search feature, selecting the remapped analog local returned in the search results causes the analog local to be recorded (not the digital) and also displays the red dot next to the remapped analog local.

[Jim_R]

I'll retest, but it seems that when the new OTA Digital channel guide data is used to select a program for recording, the digital channel will record, and the red dot appears on the remapped analog channel (when not hidden). But, when using the Menu, TV Listing, Search feature, selecting the remapped analog local returned in the search results causes the analog local to be recorded (not the digital) and also displays the red dot next to the remapped analog local.

Verified! The search feature does record the SAT remapped local channel, not the OTA Digital. Mark, do you agree that this should be changed to allow selection of SAT or Digital subchannels?

[Mark Lamutt]

Jim - definitely, and I'm embarassed to say that that was something that I never tested myself. I will definitely be doing so tonight and reporting it, though.

Please post your procedure and results as the first L211 Bug Report in the bug reports forum.