2013-07-20, 08:54 AM
A suggestion regarding the way recording scheduling is handled:
Make automatic recording schedule updates based on EPG data optional. (Either as a general or a per recording setting).
Reasons:
(1) Automatic EPG based recording schedule updates are catering mainly to a use case where the hardware allows for multiple parallel recordings. As soon as multiple parallel recordings are not possible, the automatic updates result in all sorts of unresolvable conflicts and, more importantly, in a fairly unpredictable recording behavior unless some fancy conflict handling management is introduced.
(2) EGP updates may result in 'no show details'. If this happens to a slot the user scheduled for recording, the recording is canceled. This problem cannot be solved by introducing recording conflict management.
From my point of view the main issue here is not the lack of conflict handling management but the lack of predictable behavior when it comes to 'dynamically' scheduled recordings. As currently implemented, NPNV recording scheduling is designed for a use case that assumes (1) perfectly reliable EPG data and (2) multi-recording capable hardware. While this use case certainly is a valid one, I would suggest to make the software more robust by taking into account less 'happy' use cases too.
Seeing that a 'manual recording' schedule mode is already implemented and that this works completely independent from EPG data, the option to create a statically scheduled recording from the TV Guide should be easy to implement by just pre-filling the manual recording form with EPG data (once, when the recording is set up) and treating the recording as a 'manual recording' afterwards.
P.S.
It would be nice to have a documentation of the recording (scheduling) behavior in the WIKI:
- automatic updates based on EPG
- what happens in case of recording schedule conflicts?
- how is padding treated when scheduling conflicts occur?
Unless I missed something, there is currently no way to find out about these things other than experimenting with settings and/or consulting this forum.
Make automatic recording schedule updates based on EPG data optional. (Either as a general or a per recording setting).
Reasons:
(1) Automatic EPG based recording schedule updates are catering mainly to a use case where the hardware allows for multiple parallel recordings. As soon as multiple parallel recordings are not possible, the automatic updates result in all sorts of unresolvable conflicts and, more importantly, in a fairly unpredictable recording behavior unless some fancy conflict handling management is introduced.
(2) EGP updates may result in 'no show details'. If this happens to a slot the user scheduled for recording, the recording is canceled. This problem cannot be solved by introducing recording conflict management.
From my point of view the main issue here is not the lack of conflict handling management but the lack of predictable behavior when it comes to 'dynamically' scheduled recordings. As currently implemented, NPNV recording scheduling is designed for a use case that assumes (1) perfectly reliable EPG data and (2) multi-recording capable hardware. While this use case certainly is a valid one, I would suggest to make the software more robust by taking into account less 'happy' use cases too.
Seeing that a 'manual recording' schedule mode is already implemented and that this works completely independent from EPG data, the option to create a statically scheduled recording from the TV Guide should be easy to implement by just pre-filling the manual recording form with EPG data (once, when the recording is set up) and treating the recording as a 'manual recording' afterwards.
P.S.
It would be nice to have a documentation of the recording (scheduling) behavior in the WIKI:
- automatic updates based on EPG
- what happens in case of recording schedule conflicts?
- how is padding treated when scheduling conflicts occur?
Unless I missed something, there is currently no way to find out about these things other than experimenting with settings and/or consulting this forum.