Recordings doesn't use same channel tuners

[Handy.Man]

If you'd rather retain the duplicate detection, but still want to be able to schedule extra airings without affecting the recordings created by the recurring scheduler, then you should use the "Forget" function which is on the hidden menu at the top of the Recordings screens. The basic idea is if you have a recurring recording for "ShowX", which schedules an episode for Tuesday but you then decide you want to go add a Quick Recording for the same episode of "ShowX" on Wednesday, you go to the Pending Recording you've created and "Forget" it. Behind the scenes this wipes out the Unique_ID field for that specific recording, so that it no longer matches against the Recurring Recording being scheduled during the EPG update each night.

This is not a easy thing to do. First you have to go thru the guide to program the on-off recording. Then switch to Recording, Pending Recordings to find those recordings. I try to change the sort order of the pending recordings but that doesn't change anything, I have to scroll down to find them . I try using the Find All, but it doesn't have the forget option .

Before 3.6.6 I was able to scheduled multiple Recurring Recordings for the same program, it would scheduled them as long as they were on the same day. Now as soon as I have a recordings of the same program scheduled anytime after the first one, it will not program the first airing.

A feature for "my" scenario would be to have a "avoid duplicates" per channel or even by program.

Best option for now is to schedule the on-off recordings after the EPG update on the day of the first airing. Or reprogram the first airing as a on-off recordings on that day.

[johnsonx42]

I try to change the sort order of the pending recordings but that doesn't change anything

you're right, that seems to be a bug... only the ascending/descending by date sort works, the alpha sorts do nothing

Before 3.6.6 I was able to scheduled multiple Recurring Recordings for the same program, it would scheduled them as long as they were on the same day. Now as soon as I have a recordings of the same program scheduled anytime after the first one, it will not program the first airing.

that should never have been possible, but there was a bug that allowed this. what is that they say, a beneficial bug is a feature? (at least until the bug is resolved, then someone complains their feature has been removed!)

A feature for "my" scenario would be to have a "avoid duplicates" per channel or even by program.

by channel wouldn't make sense, but having a way to allow it per recording has been requested before. it would be helpful to some. there is a setting in config.xml to <AllowCrossChannelDuplicates> which in effect ties the duplicate detection to the channel as well. if any of your programs air on multiple channels you could use that to get one recording of the same episode on each channel. since you're OTA though I suspect that won't help much.

Best option for now is to schedule the on-off recordings after the EPG update on the day of the first airing. Or reprogram the first airing as a on-off recordings on that day.

From everything you've said, I still think you'd be better off turning off duplicate detection and using day and time specific recurring recordings (i.e. the "Weekly, this timeslot" recurring type). This would be a bit more work to get all your recordings set initially, but it wouldn't require daily maintenance and manipulation.

[Handy.Man]

From everything you've said, I still think you'd be better off turning off duplicate detection and using day and time specific recurring recordings (i.e. the "Weekly, this timeslot" recurring type). This would be a bit more work to get all your recordings set initially, but it wouldn't require daily maintenance and manipulation.

Like I said before, this would generate too many recordings on other channels and creating conflicts or messing with the tuning of Recurring Recordings priority and tuner priority.

BTW my setup is working fine now, I am able to get the pre/post paddings on all the recordings now.

[johnsonx42]

if you then me

[ElihuRozen]

I'm not going to change it to display or select the tuner, because there is so many situations that can cause it to move the recording to another tuner at recording time, that it'll just lead to numerous support posts saying 'it didn't record on the tuner it said it would' or 'it didn't record on the tuner I asked it to'.

At the end of the day, the app tries it's best to make sure it can do all the recordings requested. The tuner it'll ends up using is not always known in advance.

Given what sub has said here, if you want to see what tuners are currently scheduled, you could save the following as a batch file:

Code:

@echo off
echo Recording:
"sqlite3.exe" -separator " -- " "..\npvr.db3" "SELECT SCHEDULED_RECORDING.name, strftime('%%m/%%d %%H:%%M',SCHEDULED_RECORDING.start_time,'localtime'), strftime('%%m/%%d %%H:%%M',SCHEDULED_RECORDING.end_time,'localtime'), SCHEDULED_RECORDING.channel_name, CAPTURE_SOURCE.name from SCHEDULED_RECORDING LEFT JOIN CAPTURE_SOURCE ON SCHEDULED_RECORDING.capture_source_oid=CAPTURE_SOURCE.oid where (status = '1') order by start_time;"

echo.
echo Pending:
"sqlite3.exe" -separator " -- " "..\npvr.db3" "SELECT SCHEDULED_RECORDING.name, strftime('%%m/%%d %%H:%%M',SCHEDULED_RECORDING.start_time,'localtime'),  strftime('%%m/%%d %%H:%%M',SCHEDULED_RECORDING.end_time,'localtime'), SCHEDULED_RECORDING.channel_name, CAPTURE_SOURCE.name from SCHEDULED_RECORDING LEFT JOIN CAPTURE_SOURCE ON SCHEDULED_RECORDING.capture_source_oid=CAPTURE_SOURCE.oid where (status = '0') order by start_time;"
echo.

if not "x%1x" == "xNoPausex" pause

Understand that it is not supported & if anybody runs this and posts a support question about why it changed tuners from what is listed, sub will get upset at me.

I have a shortcut to this on my desktop and also run it from PostUpdateEPG.bat, with the NoPause flag, and pipe the output to a log file. I schedule everything manually and have no recurring recordings. So, for me, this is very useful.

[Handy.Man]

That could be useful but it I get a better formatted view with SQLiteDatabaseBrowser.

For now i copy the db3 to the client and browse from there, maybe I could just open the db3 on the server to save some time but i really don't want to mess with the server. I am not changing the db3, I just look at the results. To align the channel on the right tuner, I just adjust the Recurring Recordings priority. For one-off recordings, I schedule them using the tuner priority. Once the channels are on the right tuner, I cancel the recordings I don't need.

Some tuner name are pretty long and displaying them in the GUI would probably mess a few things, however displaying the capture_source_oid (2 digits) in TV Guide or Recordings would be a nice enhancement. We could see what is happening and reorder the recordings during the day to align them.

As long as I have a way to see what is happening beforehand I am happy.

[Handy.Man]

If you'd rather retain the duplicate detection, but still want to be able to schedule extra airings without affecting the recordings created by the recurring scheduler, then you should use the "Forget" function which is on the hidden menu at the top of the Recordings screens. The basic idea is if you have a recurring recording for "ShowX", which schedules an episode for Tuesday but you then decide you want to go add a Quick Recording for the same episode of "ShowX" on Wednesday, you go to the Pending Recording you've created and "Forget" it. Behind the scenes this wipes out the Unique_ID field for that specific recording, so that it no longer matches against the Recurring Recording being scheduled during the EPG update each night.

Well it is easier to forget the first airing, then at next EPG Update, it will reschedule the next airing

[johnsonx42]

Well it is easier to forget the first airing, then at next EPG Update, it will reschedule the next airing

I don't see how it could, and certainly doesn't do that here (tested it just to make sure I wasn't missing something). If you "Forget" a pending recurring recording, all it does it clear the unique_id. When the EPG update runs, the pending recording is cleared and then rescheduled again with the unique_id restored again.

For that to work the "Forget" function would also have to clear the recurence_oid of the pending recording, but it doesn't do that. Perhaps "Forget" should do that too, I guess it depends on precisely what people using the "Forget" function are trying to accomplish.

[BrettB]

For that to work the "Forget" function would also have to clear the recurence_oid of the pending recording, but it doesn't do that. Perhaps "Forget" should do that too, I guess it depends on precisely what people using the "Forget" function are trying to accomplish.

The "Forget" function doesn't really make sense to me for a pending recording. I use it when a recording ends up either being something different (i.e. because the broadcaster changed the schedule after the last EPG update or the scheduled programming gets preempted by some news event, etc.) or if a recording is "bad" for some reason. In either case, I want the EPG update to re-schedule that episode to record when it (next) airs.

[johnsonx42]

The primary use with Pending recordings is to allow you to cancel a Pending recording without the unique_id being added to the recently_deleted list. I mostly use it when testing things, but I can see cases where I might want to do that in normal use too. The second use I can think of is what I proposed to Handy.Man - you want to pre-emptively schedule an extra recording of a show in case the original recurring recording has glitches; you have to "Forget" the new recording else the original recurring recording will disappear at the next EPG update.