home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Products
TV-Server
For The Record - The rule-based scheduling suite
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="marmite" data-source="post: 206674" data-attributes="member: 48853"><p>Thanks for your replies dvdfreak,</p><p></p><p></p><p></p><p>I understand (and agree) that you want to compartmentalize the 'scheduling' functionality as much as possible, to keep it simple yet powerful.</p><p></p><p>So conflict management (CM) can be self contained also, but must work closely with the scheduler.</p><p>The CM would need to be aware of:</p><p>i) the net results of the scheduled rules</p><p>ii) be made aware of a change to these results, e.g. if new schedule, or program slot moves.</p><p>ii) have resource definitions for the available tuners, so it can attempt to fulfil the requirements. </p><p></p><p>It then has the necessary information, to produce a list of unresourcable schedule items.</p><p></p><p>But to alert the user proactively, or passively via a conflicts view, it will need to make the user aware of the rule(s) that led to these conflicting items _and_ if applicable look at what other alternative programming is available that satisfy the rules and do not clash (or perhaps even present other alternatives that do clash - they may be better).</p><p>And then present the user with some choices:</p><p>i) >=1 scheduled rule that led to be cancelled</p><p>ii) allow a specific result(s) (upcoming program(s) matched by rules in conflict set) to be ignored. I suspect this will be normal choice if presented correctly, so will allow </p><p></p><p>Sorry I'm rambling, I guess I've very excited that this scheduler is finally tacking the problem the way it should be done _and_ I hate to refer to it but, one day it may be as easy to use and as logical as Tivo was 7+ years ago!</p><p></p><p>CM is pretty important I think to avoid frustration at unclear choices being made by recording system when conflicts occur. (Btw - what on earth does the MP "ConflictsManager" server plugin actually do??)</p><p></p><p>I have a single tuner DVB-T system - I wouldn't think twice about going out and getting another tuner, but one of the main reasons I don't to be honest, apart from having a backup recording system, is that I feel if I can't get to work satisfactorily with 1 tuner, meaning clearly/logically, then I will compound problems with 2.</p><p></p><p>A real world example of need and requirements for CM for me is, in our household we record:</p><p>A) Daily "Neighbours" on BBC1 ( shown twice daily )</p><p>B) CBeebies progs, or "Working Lunch" [BBC2] </p><p></p><p>When a B) schedule occurs that overlaps the 1st showing of A) - (which occurs regularly occurs)</p><p>I'd expect CM to kick in and silently choose to ignore one of the showing of A) if it finds free to record other.</p><p></p><p>Bit concerned that MP-II development will mean MP-I/TVE3 - will mean MP-I will not change significantly now and we'll be in for a long wait for MP-II and will make all this difficult, but perhaps can all be done via plugin / console.</p><p></p><p>The scheduler work you've done is excellent dvdfreak, what's your thoughts on CM?</p></blockquote><p></p>
[QUOTE="marmite, post: 206674, member: 48853"] Thanks for your replies dvdfreak, I understand (and agree) that you want to compartmentalize the 'scheduling' functionality as much as possible, to keep it simple yet powerful. So conflict management (CM) can be self contained also, but must work closely with the scheduler. The CM would need to be aware of: i) the net results of the scheduled rules ii) be made aware of a change to these results, e.g. if new schedule, or program slot moves. ii) have resource definitions for the available tuners, so it can attempt to fulfil the requirements. It then has the necessary information, to produce a list of unresourcable schedule items. But to alert the user proactively, or passively via a conflicts view, it will need to make the user aware of the rule(s) that led to these conflicting items _and_ if applicable look at what other alternative programming is available that satisfy the rules and do not clash (or perhaps even present other alternatives that do clash - they may be better). And then present the user with some choices: i) >=1 scheduled rule that led to be cancelled ii) allow a specific result(s) (upcoming program(s) matched by rules in conflict set) to be ignored. I suspect this will be normal choice if presented correctly, so will allow Sorry I'm rambling, I guess I've very excited that this scheduler is finally tacking the problem the way it should be done _and_ I hate to refer to it but, one day it may be as easy to use and as logical as Tivo was 7+ years ago! CM is pretty important I think to avoid frustration at unclear choices being made by recording system when conflicts occur. (Btw - what on earth does the MP "ConflictsManager" server plugin actually do??) I have a single tuner DVB-T system - I wouldn't think twice about going out and getting another tuner, but one of the main reasons I don't to be honest, apart from having a backup recording system, is that I feel if I can't get to work satisfactorily with 1 tuner, meaning clearly/logically, then I will compound problems with 2. A real world example of need and requirements for CM for me is, in our household we record: A) Daily "Neighbours" on BBC1 ( shown twice daily ) B) CBeebies progs, or "Working Lunch" [BBC2] When a B) schedule occurs that overlaps the 1st showing of A) - (which occurs regularly occurs) I'd expect CM to kick in and silently choose to ignore one of the showing of A) if it finds free to record other. Bit concerned that MP-II development will mean MP-I/TVE3 - will mean MP-I will not change significantly now and we'll be in for a long wait for MP-II and will make all this difficult, but perhaps can all be done via plugin / console. The scheduler work you've done is excellent dvdfreak, what's your thoughts on CM? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Products
TV-Server
For The Record - The rule-based scheduling suite
Contact us
RSS
Top
Bottom