Any way to temporarily suspend scheduled recordings?

[tinstaafl]

I am asking because I usually shut down my computer when I am going to be away for several days or more.

Then when I return I am greeted with a long list of failed recordings because the recording service was (obviously) not active at the scheduled recording times.

After manually deleting the failed recordings, all is well again.

So I was wondering if there is a way to manually suspend/pause all scheduled NPVR recordings for my "away" time, other than deleting them from the scheduled recordings list?

[sub]

Sorry, no there isn't.

[tinstaafl]

Sorry, no there isn't.

Aha! Thanks!

Alternatively, how difficult would it be to export the active recording schedule data to a backup location, then delete the active schedule, followed by restoring the previously active schedule data at a later date?

[sub]

Aha! Thanks!

Alternatively, how difficult would it be to export the active recording schedule data to a backup location, then delete the active schedule, followed by restoring the previously active schedule data at a later date?

It's probably easier to just execute a one line sql statement when you get back, to delete all the failed recordings between two dates.

[sub]

If it's only a short period, you're only gonna have a handful of recordings, and it'd be simple to just manually delete them.

[mvallevand]

It's probably easier to just execute a one line sql statement when you get back, to delete all the failed recordings between two dates.

What about sqlite

update recurring_recording set enabled = 'N'

assuming NextPVR respects the enabled field.

Martin

[BrettB]

What about sqlite

update recurring_recording set enabled = 'N'

assuming NextPVR respects the enabled field.

In the OP's use case, though, when he got back, he'd have to use sqlite again to re-enable the recurring recordings. So, sub's suggestion:

It's probably easier to just execute a one line sql statement when you get back, to delete all the failed recordings between two dates.

probably fits his case better. Then he doesn't have to do anything with the recurring recordings. And would just need to do one sql command to delete all the failed recordings.

[BrettB]

In the OP's use case, though, when he got back, he'd have to use sqlite again to re-enable the recurring recordings. So, sub's suggestion probably fits his case better. Then he doesn't have to do anything with the recurring recordings. And would just need to do one sql command to delete all the failed recordings.

Thinking about it a bit more. If he didn't care about ever saving failed recordings, he could probably even put the sql command in the PostStartup script file and just have it automatically clear out any failed recording each time the server was started. (This presumes that the server has already marked all of the missed recordings as failed at startup before PostStartup gets called. If not, maybe add a delay/wait in PostStartup before running the sql.)

[mvallevand]

I agree that sub's suggestion is best I was answering the question. Leaving the service as it will allow some unique id recording possibilities too.

Martin

[mvallevand]

As someone who loads other database, I think there is another risk of NextPVR creating empty folders in the recording directory before they are marked failed.

Martin