How's this even possible??

[encoder]

I did a search for "window to the sea" in the web admin, and then clicked on the "Record Once" button. I got two entries for the same time slot:

Window to the Sea 1872 12/9/2007 11:00 AM-12:00 PM Sunday
Window to the Sea 1872 12/9/2007 11:00 AM-12:00 PM Sunday

What could possibly cause this?

[encoder]

I went into Viewscape and confirmed that there's only one upcoming showing. So I deleted this show in web admin and scheduled it in Viewscape. I now get only one entry for this show when viewing upcoming recordings in the web admin as expected.

There's clearly some bugs with scheduling through the Search Guide page (this is a new feature in 4.7.1). I'm wondering if the bogus conflicts I reported in another thread is related to this somehow (I scheduled all the recordings through the web admin).

[encoder]

Looking at the database I see two program lines for the same show with the same stationcallsign/stationname. But the channels have different uniquechannelid, tmschan, and majorchannel/minorchannel.

I'm guessing Viewscape does the right thing by using the uniquechannelid whereas the web admin incorrectly uses the stationcallsign/stationname, thus picking up multiple lines.

[encoder]

In addition to using Viewscape, I used snaptream.net to schedule the show. I also got the correct behavior.

In addition, I encountered another bogus conflicts report and have confirmed that it was caused by the same bug in the scheduler in Search Guide.

For years I had been using snapstream.net's Guide to schedule recordings until the release of 4.7.1 when I scheduled all my recordings using Guide Search. Now I have to face the prospect of re-scheduling 80 of recordings in my schedule since I now know everything scheduled with Guide Search is suspect.

Curiosity kills the cat, I guess. I should have let others beta test new features first before using them.

[encoder]

One more thing: You can schedule a good recording using snapstream.net or Viewscape. But if you do anything with it using web admin, like changing its priority or setting the "Create fixed content" flag, then web admin would screw up in the same way that scheduling a show using the Guide Search would.

In conclusion: Avoid using the web admin to 1. schedule recordings (i.e. scheduling through Guide Search) or 2. modify your schedules (i.e. doing anything with your schedules in Recording Manager).

I can live with 1., but 2. is hard for me to accept.

[encoder]

More info: If I scheduled the said show in snapstream.net, the Upcoming Recordings page showed the scheduled recording as expected. The Conflcting Recordings page also came up empty as expected. However the conflict (2 days in the future) resurfaced once BTV started to record the next show (it didn't matter what the show was) and the show in question was no longer scheduled. In other words, once the recording manager started running, it messed things up again. There's definitely some serious issue with the recording manager. I can reproduce this bug at will.

What good is the Upcoming Recordings and Show Conflicting Recordings if they don't reliably reflect what really will be recorded or not recorded? In fact, the reports are downright misleading and give the user the false assurance that BTV would record the shows it said it would, only to disappoint him/her when it didn't record the shows due to conflicts not reported to the user.