Beta [Real-time scheduling] schedule without rebooting

Status
Not open for further replies.
Terrahawk said:
First class af123, many thanks. :D I've done a number of series recordings and all seems good :thumbsup:

Out of interest, when do reminders get removed from the schedule? Should it be removed when the programme start time is reached, or at the end of the programme. I seen a reminder was still in the schedule after the programme has started. I've not looked before to see what the normal behavior is. It was removed after the box was put into standby and woken up again.
Click to expand...
I think reminders are removed at the end of the reminder period or when another recording or reminder starts before the end of the period
 
I use 1.02.32 and had the crashes on the webif update but the nugget update sorted it out. Thanks.

af123 said:
the internal data structure used to hold schedule entries is four bytes bigger in 1.03.12 than previous versions so the offset of the EPG data is different between the versions. When I get some time I'll look to see what the difference is.
Click to expand...

Apologies for going off thread but could this be the reason for the lag in EPG in 1.03.xx

Back to thread. Brilliant to be able to use as it to schedule recordings instantly without interruption of viewing or needing a reboot!
 
An updated nugget 0.94 is available now. This is mainly an overhaul and code clean-up but I've also fixed a problem where it didn't like a schedule becoming empty. I've improved the API used between the nugget and rsvsync components (it's a private API so no visible changes there) which means that a reboot is required after upgrading and before attempting to schedule anything.

I've also released an updated rs package which works slightly better with this. RS can apply a set of schedule changes in one go and this change allows them to be batched up and then applied to the live schedule all at once rather than incrementally. The 'reboot required' flag is also no longer set by RS if it isn't needed.

There is still more testing to do with this version before I'm happy with it - I'm still unsure if the runaway recordings are completely fixed and I have a slight suspicion that episode skip may not work quite as intended with real-time turned on.

Please carry on testing. I'm not planning to do much work on the code over the long weekend but I'll pick it up again next week.
 
What do you mean by "episode skip"?

I've set up a few testing test entries on my machines, including a daily manual timer, all looks good so far - no hiccups. I have set The Bourne Ultimatum for ITV tonight - it is spilt by The News and correctly has the split flag, the recording schedule appears to be correct when inspected through the SUI.
 
I see the RS site still offers to "Schedule Reboot". Maybe the rs package needs to communicate back that RTS is active.
 
Black Hole said:
What do you mean by "episode skip"?
Click to expand...
The RS facility to resolve conflicts by skipping an episode or scheduling an alternative recoding.
I haven't need to try it yet with the new support
Black Hole said:
I've set up a few testing test entries on my machines, including a daily manual timer, all looks good so far - no hiccups. I have set The Bourne Ultimatum for ITV tonight - it is spilt by The News and correctly has the split flag, the recording schedule appears to be correct when inspected through the SUI.
Click to expand...
I haven't tried it extensively but so far no run on recordings or dropped schedules
 
af123 said:
I have a slight suspicion that episode skip may not work quite as intended with real-time turned on.

Please carry on testing. I'm not planning to do much work on the code over the long weekend but I'll pick it up again next week.
Click to expand...
I thought I would give it a try but the Skip/Cancel... options have gone AWOL from the RS menu :(

I presume this is a safety precaution until you get a chance for deeper investigation

Enjoy the Bank Holiday
 
af123 said:
Not deliberate - they only appear on the visual view though.
Click to expand...
Senior moment, but it really would be nice if they were also available on the EPG display, Pretty Please.

I did use RT scheduling to schedule a series with back to back episodes and then skipped one of the episodes and rescheduled another and it appears from the schedule display all the changes have been applied correctly. However it is currently recording the first of the 'skipped' episodes so as you suspected it doesn't appear to be working correctly

Update: Looking at what actually happened the first episode in the series, started in mid programme, is actually a run on recording and I only have failed recording .hmts for the subsequent episodes including those that should have been skipped.

In case it helps this the relevant part of nugget log
Code: 
[nugget]: Sat Aug 27 19:26:50 2016: Re-loading schedule database (64).
[nugget]: Sat Aug 27 19:26:50 2016: schedule.stash 16 = 2
[nugget]: Sat Aug 27 19:26:50 2016: schedule reload starting (63).
[nugget]: Sat Aug 27 19:26:50 2016: Schedule count failed.
[nugget]: Sat Aug 27 19:26:50 2016: schedule reload complete (-1).
[nugget]: Sat Aug 27 19:26:50 2016: Schedule failed to reload, deferring.
[nugget]: Sat Aug 27 19:26:50 2016: Deferred thread starting for '64:42:-' (attempt 1)
[nugget]: Sat Aug 27 19:26:55 2016: Re-loading schedule database (64).
[nugget]: Sat Aug 27 19:26:55 2016: Schedule count failed.
[nugget]: Sat Aug 27 19:26:55 2016: schedule reload starting (0).
[nugget]: Sat Aug 27 19:26:55 2016: schedule.restore 16 = 2
[nugget]: Sat Aug 27 19:26:55 2016: schedule reload complete (64).
[nugget]: Sat Aug 27 19:26:55 2016: slots(64, 42, -)
[nugget]: Sat Aug 27 19:26:55 2016: Adding/updating slot 42
[nugget]: Sat Aug 27 19:26:55 2016: Populating EPG data for slot 42
[nugget]: Sat Aug 27 19:26:55 2016:  Wake 1472319900 - Sat Aug 27 18:45:00 2016
[nugget]: Sat Aug 27 19:26:55 2016: Ready 1472319870 - Sat Aug 27 18:44:30 2016
[nugget]: Sat Aug 27 19:26:55 2016: In the past.
[nugget]: Sat Aug 27 19:26:55 2016: Running, best effort.
[nugget]: Sat Aug 27 19:26:55 2016: Adding timer(1472322420)
[nugget]: Sat Aug 27 19:26:55 2016: Deferred thread exiting.
[nugget]: Sat Aug 27 19:29:40 2016: Re-loading schedule database (64).
[nugget]: Sat Aug 27 19:29:40 2016: schedule.stash 42 = 2
[nugget]: Sat Aug 27 19:29:40 2016: schedule.stash 16 = 2
[nugget]: Sat Aug 27 19:29:40 2016: schedule reload starting (64).
[nugget]: Sat Aug 27 19:29:40 2016: schedule.restore 42 = 2
[nugget]: Sat Aug 27 19:29:40 2016: schedule.restore 16 = 2
[nugget]: Sat Aug 27 19:29:40 2016: schedule reload complete (64).
[nugget]: Sat Aug 27 19:29:40 2016: slots(64, 42, -)
[nugget]: Sat Aug 27 19:29:40 2016: Adding/updating slot 42
[nugget]: Sat Aug 27 19:29:40 2016: Good EPG data, retaining.
[nugget]: Sat Aug 27 19:29:40 2016:  Wake 1472319900 - Sat Aug 27 18:45:00 2016
[nugget]: Sat Aug 27 19:29:40 2016: Ready 1472319870 - Sat Aug 27 18:44:30 2016
[nugget]: Sat Aug 27 19:29:40 2016: In the past.
[nugget]: Sat Aug 27 19:29:40 2016: Running, best effort.
[nugget]: Sat Aug 27 19:29:40 2016: Adding timer(1472322585)
[nugget]: Sat Aug 27 19:30:34 2016: Re-loading schedule database (65).
[nugget]: Sat Aug 27 19:30:34 2016: schedule.stash 42 = 1
[nugget]: Sat Aug 27 19:30:34 2016: schedule.stash 16 = 2
[nugget]: Sat Aug 27 19:30:34 2016: schedule reload starting (64).
[nugget]: Sat Aug 27 19:30:34 2016: schedule.restore 42 = 1
[nugget]: Sat Aug 27 19:30:35 2016: schedule.restore 16 = 2
[nugget]: Sat Aug 27 19:30:35 2016: schedule reload complete (65).
[nugget]: Sat Aug 27 19:30:35 2016: slots(65, 64, -)
[nugget]: Sat Aug 27 19:30:35 2016: Adding/updating slot 64
[nugget]: Sat Aug 27 19:30:35 2016: Populating EPG data for slot 64
[nugget]: Sat Aug 27 19:30:35 2016:  Wake 1472327100 - Sat Aug 27 20:45:00 2016
[nugget]: Sat Aug 27 19:30:35 2016: Ready 1472327070 - Sat Aug 27 20:44:30 2016
[nugget]: Sat Aug 27 19:30:35 2016: Adding timer(1472327070)
[nugget]: Sat Aug 27 19:30:36 2016: Re-loading schedule database (65).
[nugget]: Sat Aug 27 19:30:36 2016: schedule.stash 42 = 1
[nugget]: Sat Aug 27 19:30:36 2016: schedule.stash 16 = 2
[nugget]: Sat Aug 27 19:30:36 2016: schedule reload starting (65).
[nugget]: Sat Aug 27 19:30:36 2016: schedule.restore 42 = 1
[nugget]: Sat Aug 27 19:30:36 2016: schedule.restore 16 = 2
[nugget]: Sat Aug 27 19:30:36 2016: schedule reload complete (65).
[nugget]: Sat Aug 27 19:30:36 2016: slots(65, 42, -)
[nugget]: Sat Aug 27 19:30:36 2016: Adding/updating slot 42
[nugget]: Sat Aug 27 19:30:36 2016: Good EPG data, retaining.
[nugget]: Sat Aug 27 19:30:36 2016:  Wake 1472321700 - Sat Aug 27 19:15:00 2016
[nugget]: Sat Aug 27 19:30:36 2016: Ready 1472321670 - Sat Aug 27 19:14:30 2016
[nugget]: Sat Aug 27 19:30:36 2016: In the past.
[nugget]: Sat Aug 27 19:30:36 2016: Running, best effort.
[nugget]: Sat Aug 27 19:30:36 2016: Adding timer(1472322641)
[nugget]: Sat Aug 27 19:36:43 2016: Re-loading schedule database (65).
[nugget]: Sat Aug 27 19:36:43 2016: schedule.stash 42 = 1
[nugget]: Sat Aug 27 19:36:43 2016: schedule.stash 16 = 2
[nugget]: Sat Aug 27 19:36:43 2016: schedule reload starting (65).
[nugget]: Sat Aug 27 19:36:43 2016: schedule.restore 42 = 1
[nugget]: Sat Aug 27 19:36:43 2016: schedule.restore 16 = 2
[nugget]: Sat Aug 27 19:36:43 2016: schedule reload complete (65).
[nugget]: Sat Aug 27 19:36:43 2016: slots(65, 42, -)
[nugget]: Sat Aug 27 19:36:43 2016: Adding/updating slot 42
[nugget]: Sat Aug 27 19:36:43 2016: Good EPG data, retaining.
[nugget]: Sat Aug 27 19:36:43 2016:  Wake 1472321700 - Sat Aug 27 19:15:00 2016
[nugget]: Sat Aug 27 19:36:43 2016: Ready 1472321670 - Sat Aug 27 19:14:30 2016
[nugget]: Sat Aug 27 19:36:43 2016: In the past.
[nugget]: Sat Aug 27 19:36:43 2016: Running, best effort.
[nugget]: Sat Aug 27 19:36:43 2016: Adding timer(1472323008)
 
Last edited:
I set a load of tests on Saturday morning, most of which have completed successfully (including the split Bourne Ultimatum) or have yet to mature. However, I think I set the same series recording for Storage Hunters UK (just because it was handy) on all three HDRs, and it only occurred on two of them. I can find no sign of it on my 1.02.32 machine, and therefore have doubts whether I actually set it up at all.

I was hoping the nugget log would confirm whether I set the recording up at all, but if it does I don't understand the entries:

Code: 
[nugget]: Sat Aug 27 09:41:37 2016: Persistent log starting, v0.94
[nugget]: Sat Aug 27 09:41:37 2016: Re-loading schedule database (15).
[nugget]: Sat Aug 27 09:41:37 2016: schedule reload starting (14).
[nugget]: Sat Aug 27 09:41:37 2016: Schedule count failed.
[nugget]: Sat Aug 27 09:41:37 2016: schedule reload complete (-1).
[nugget]: Sat Aug 27 09:41:37 2016: Schedule failed to reload, deferring.
[nugget]: Sat Aug 27 09:41:37 2016: Deferred thread starting for '15:13:-' (attempt 1)
[nugget]: Sat Aug 27 09:41:43 2016: Re-loading schedule database (15).
[nugget]: Sat Aug 27 09:41:43 2016: Schedule count failed.
[nugget]: Sat Aug 27 09:41:43 2016: schedule reload starting (0).
[nugget]: Sat Aug 27 09:41:43 2016: schedule reload complete (15).
[nugget]: Sat Aug 27 09:41:43 2016: slots(15, 13, -)
[nugget]: Sat Aug 27 09:41:43 2016: Adding/updating slot 13
[nugget]: Sat Aug 27 09:41:43 2016: Populating EPG data for slot 13
[nugget]: Sat Aug 27 09:41:43 2016:  Wake 1472592540 - Tue Aug 30 22:29:00 2016
[nugget]: Sat Aug 27 09:41:43 2016: Ready 1472592510 - Tue Aug 30 22:28:30 2016
[nugget]: Sat Aug 27 09:41:43 2016: Adding timer(1472592510)
[nugget]: Sat Aug 27 09:41:43 2016: Deferred thread exiting.
[nugget]: Sat Aug 27 09:42:22 2016: Re-loading schedule database (16).
[nugget]: Sat Aug 27 09:42:22 2016: schedule reload starting (15).
[nugget]: Sat Aug 27 09:42:22 2016: Schedule count failed.
[nugget]: Sat Aug 27 09:42:22 2016: schedule reload complete (-1).
[nugget]: Sat Aug 27 09:42:22 2016: Schedule failed to reload, deferring.
[nugget]: Sat Aug 27 09:42:22 2016: Deferred thread starting for '16:14:-' (attempt 1)
[nugget]: Sat Aug 27 09:42:27 2016: Re-loading schedule database (16).
[nugget]: Sat Aug 27 09:42:27 2016: Schedule count failed.
[nugget]: Sat Aug 27 09:42:27 2016: schedule reload starting (0).
[nugget]: Sat Aug 27 09:42:28 2016: schedule reload complete (16).
[nugget]: Sat Aug 27 09:42:28 2016: slots(16, 14, -)
[nugget]: Sat Aug 27 09:42:28 2016: Adding/updating slot 14
[nugget]: Sat Aug 27 09:42:28 2016: Populating EPG data for slot 14
[nugget]: Sat Aug 27 09:42:28 2016:  Wake 1472592540 - Tue Aug 30 22:29:00 2016
[nugget]: Sat Aug 27 09:42:28 2016: Ready 1472592510 - Tue Aug 30 22:28:30 2016
[nugget]: Sat Aug 27 09:42:28 2016: Adding timer(1472592510)
[nugget]: Sat Aug 27 09:42:28 2016: Deferred thread exiting.
[nugget]: Sat Aug 27 09:43:45 2016: Re-loading schedule database (16).
[nugget]: Sat Aug 27 09:43:45 2016: schedule reload starting (16).
[nugget]: Sat Aug 27 09:43:45 2016: schedule reload complete (16).
[nugget]: Sat Aug 27 09:43:45 2016: slots(16, 13, -)
[nugget]: Sat Aug 27 09:43:45 2016: Adding/updating slot 13
[nugget]: Sat Aug 27 09:43:45 2016: Good EPG data, retaining.
[nugget]: Sat Aug 27 09:43:45 2016:  Wake 1472592540 - Tue Aug 30 22:29:00 2016
[nugget]: Sat Aug 27 09:43:45 2016: Ready 1472592510 - Tue Aug 30 22:28:30 2016
[nugget]: Sat Aug 27 09:43:45 2016: Adding timer(1472592510)
[nugget]: Sat Aug 27 09:44:01 2016: Re-loading schedule database (16).
[nugget]: Sat Aug 27 09:44:01 2016: schedule reload starting (16).
[nugget]: Sat Aug 27 09:44:01 2016: schedule reload complete (16).
[nugget]: Sat Aug 27 09:44:01 2016: slots(16, 14, -)
[nugget]: Sat Aug 27 09:44:01 2016: Adding/updating slot 14
[nugget]: Sat Aug 27 09:44:01 2016: Good EPG data, retaining.
[nugget]: Sat Aug 27 09:44:01 2016:  Wake 1472592540 - Tue Aug 30 22:29:00 2016
[nugget]: Sat Aug 27 09:44:01 2016: Ready 1472592510 - Tue Aug 30 22:28:30 2016
[nugget]: Sat Aug 27 09:44:01 2016: Adding timer(1472592510)
 
You're right, the logging isn't useful for checking what you want (that is something I plan to fix in the next version).
 
Black Hole said:
I set a load of tests on Saturday morning, most of which have completed successfully (including the split Bourne Ultimatum) or have yet to mature. However, I think I set the same series recording for Storage Hunters UK (just because it was handy) on all three HDRs, and it only occurred on two of them. I can find no sign of it on my 1.02.32 machine, and therefore have doubts whether I actually set it up at all.

I was hoping the nugget log would confirm whether I set the recording up at all, but if it does I don't understand the entries:

Code: 
[nugget]: Sat Aug 27 09:41:37 2016: Persistent log starting, v0.94
[nugget]: Sat Aug 27 09:41:37 2016: Re-loading schedule database (15).
[nugget]: Sat Aug 27 09:41:37 2016: schedule reload starting (14).
[nugget]: Sat Aug 27 09:41:37 2016: Schedule count failed.
[nugget]: Sat Aug 27 09:41:37 2016: schedule reload complete (-1).
[nugget]: Sat Aug 27 09:41:37 2016: Schedule failed to reload, deferring.
[nugget]: Sat Aug 27 09:41:37 2016: Deferred thread starting for '15:13:-' (attempt 1)
[nugget]: Sat Aug 27 09:41:43 2016: Re-loading schedule database (15).
[nugget]: Sat Aug 27 09:41:43 2016: Schedule count failed.
[nugget]: Sat Aug 27 09:41:43 2016: schedule reload starting (0).
[nugget]: Sat Aug 27 09:41:43 2016: schedule reload complete (15).
[nugget]: Sat Aug 27 09:41:43 2016: slots(15, 13, -)
[nugget]: Sat Aug 27 09:41:43 2016: Adding/updating slot 13
[nugget]: Sat Aug 27 09:41:43 2016: Populating EPG data for slot 13
[nugget]: Sat Aug 27 09:41:43 2016:  Wake 1472592540 - Tue Aug 30 22:29:00 2016
[nugget]: Sat Aug 27 09:41:43 2016: Ready 1472592510 - Tue Aug 30 22:28:30 2016
[nugget]: Sat Aug 27 09:41:43 2016: Adding timer(1472592510)
[nugget]: Sat Aug 27 09:41:43 2016: Deferred thread exiting.
[nugget]: Sat Aug 27 09:42:22 2016: Re-loading schedule database (16).
[nugget]: Sat Aug 27 09:42:22 2016: schedule reload starting (15).
[nugget]: Sat Aug 27 09:42:22 2016: Schedule count failed.
[nugget]: Sat Aug 27 09:42:22 2016: schedule reload complete (-1).
[nugget]: Sat Aug 27 09:42:22 2016: Schedule failed to reload, deferring.
[nugget]: Sat Aug 27 09:42:22 2016: Deferred thread starting for '16:14:-' (attempt 1)
[nugget]: Sat Aug 27 09:42:27 2016: Re-loading schedule database (16).
[nugget]: Sat Aug 27 09:42:27 2016: Schedule count failed.
[nugget]: Sat Aug 27 09:42:27 2016: schedule reload starting (0).
[nugget]: Sat Aug 27 09:42:28 2016: schedule reload complete (16).
[nugget]: Sat Aug 27 09:42:28 2016: slots(16, 14, -)
[nugget]: Sat Aug 27 09:42:28 2016: Adding/updating slot 14
[nugget]: Sat Aug 27 09:42:28 2016: Populating EPG data for slot 14
[nugget]: Sat Aug 27 09:42:28 2016:  Wake 1472592540 - Tue Aug 30 22:29:00 2016
[nugget]: Sat Aug 27 09:42:28 2016: Ready 1472592510 - Tue Aug 30 22:28:30 2016
[nugget]: Sat Aug 27 09:42:28 2016: Adding timer(1472592510)
[nugget]: Sat Aug 27 09:42:28 2016: Deferred thread exiting.
[nugget]: Sat Aug 27 09:43:45 2016: Re-loading schedule database (16).
[nugget]: Sat Aug 27 09:43:45 2016: schedule reload starting (16).
[nugget]: Sat Aug 27 09:43:45 2016: schedule reload complete (16).
[nugget]: Sat Aug 27 09:43:45 2016: slots(16, 13, -)
[nugget]: Sat Aug 27 09:43:45 2016: Adding/updating slot 13
[nugget]: Sat Aug 27 09:43:45 2016: Good EPG data, retaining.
[nugget]: Sat Aug 27 09:43:45 2016:  Wake 1472592540 - Tue Aug 30 22:29:00 2016
[nugget]: Sat Aug 27 09:43:45 2016: Ready 1472592510 - Tue Aug 30 22:28:30 2016
[nugget]: Sat Aug 27 09:43:45 2016: Adding timer(1472592510)
[nugget]: Sat Aug 27 09:44:01 2016: Re-loading schedule database (16).
[nugget]: Sat Aug 27 09:44:01 2016: schedule reload starting (16).
[nugget]: Sat Aug 27 09:44:01 2016: schedule reload complete (16).
[nugget]: Sat Aug 27 09:44:01 2016: slots(16, 14, -)
[nugget]: Sat Aug 27 09:44:01 2016: Adding/updating slot 14
[nugget]: Sat Aug 27 09:44:01 2016: Good EPG data, retaining.
[nugget]: Sat Aug 27 09:44:01 2016:  Wake 1472592540 - Tue Aug 30 22:29:00 2016
[nugget]: Sat Aug 27 09:44:01 2016: Ready 1472592510 - Tue Aug 30 22:28:30 2016
[nugget]: Sat Aug 27 09:44:01 2016: Adding timer(1472592510)
Click to expand...
I have doubts about what I am doing with only one box to deal with:confused:

The log deals in database slot numbers so you would have to look at rsv.db to see which programs were in each slot, and slots may have been reused by activity since Saturday
 
0.95 will include more detail in the log. Any other fields you think worth logging?

Code: 
[nugget]: Mon Aug 29 21:42:11 2016: Persistent log starting, v0.95
[nugget]: Mon Aug 29 21:42:11 2016: Re-loading schedule database (1).
[nugget]: Mon Aug 29 21:42:11 2016: schedule reload starting (0).
[nugget]: Mon Aug 29 21:42:11 2016: schedule reload complete (1).
[nugget]: Mon Aug 29 21:42:11 2016: slots(1, +0)
[nugget]: Mon Aug 29 21:42:11 2016: Processing slot +0 (0)
[nugget]: Mon Aug 29 21:42:11 2016:   Family Guy
[nugget]: Mon Aug 29 21:42:11 2016:       @ 1472504400 (Mon Aug 29 22:00:00 2016)
[nugget]: Mon Aug 29 21:42:11 2016:   CRID: 2/[WWW.ITV.COM/203079386]
[nugget]: Mon Aug 29 21:42:11 2016:  Wake 1472503500 - Mon Aug 29 21:45:00 2016
[nugget]: Mon Aug 29 21:42:11 2016: Ready 1472503470 - Mon Aug 29 21:44:30 2016
[nugget]: Mon Aug 29 21:42:11 2016: Adding timer(1472503470)
 
Having just returned home from a few days away, I see that one of my boxes has a runaway recording in progress. This has been recording since 9am on Saturday, and is currently 66.35GiB, and growing. Will there be anything useful in any of the logs? and what is the recommended way to stop such a recording?
I would like to be able to watch parts of this recording, because the elapsed time contains two additional recordings that have been reported by the RS Failed Recording Checker.
 
Brian said:
Having just returned home from a few days away, I see that one of my boxes has a runaway recording in progress. This has been recording since 9am on Saturday, and is currently 66.35GiB, and growing. Will there be anything useful in any of the logs? and what is the recommended way to stop such a recording?
I would like to be able to watch parts of this recording, because the elapsed time contains two additional recordings that have been reported by the RS Failed Recording Checker.
Click to expand...
The Stop button on the remote kills the runaways.

You may want to try using NiceSplice to extract the useful parts of the recording or just set bookmarks where you calculate the required programs are if you don't want to keep them longer than a single viewing
 
MymsMan said:
The Stop button on the remote kills the runaways.

You may want to try using NiceSplice to extract the useful parts of the recording or just set bookmarks where you calculate the required programs are if you don't want to keep them longer than a single viewing
Click to expand...
Thanks, I had already tried using the stop button, but didn't have my TV turned on, so forgot that you have to confirm which recording to stop, using the OK button.
The recordings are only watch once then delete, so it's not worth going to any trouble with them.
 
Brian said:
Thanks, I had already tried using the stop button, but didn't have my TV turned on, so forgot that you have to confirm which recording to stop, using the OK button.
The recordings are only watch once then delete, so it's not worth going to any trouble with them.
Click to expand...
Setting bookmarks with webif bookmark option from browse menu will save a lot of fast forwarding through the recording
 
I haven't been on this forum for a few weeks so I wasn't aware this development had been going on. So I'm still running with this new feature turned off, but I have just noticed a problem with the usually rock-solid RS, which I'm guessing is as a result of changes in RS to accommodate this exciting new facility.

Basically, I can't unschedule a series from RS - I get this:

Capture.JPG

I can schedule new entries ok, so it looks like just deleting ones isn't working. I haven't tried it from Webif yet just in case more diags are needed. I can't see anything in the rs.log related to this event.
 
Status
Not open for further replies.
Back
Top