Eirik Meland wrote: > I think we should go to the root of this problem, and let the user
decide how to resolve conflicts during scheduling.
We still need logic to resolve schedule conflicts and priorities and such but we are not talking about a scheduling conflict here. These shows are in unoverlapping timeslots, there is no conflict of this sort.
However, after implimenting a default behaviour (ignore padding for back to back shows) we could add options to add a priority flag to more than just favourite recorings and let one show's padding respect or ignore the other's padding. Maybe you don't mind starting the next show late if you would rather make sure your current recording is complete. This could also go hand in hand with adding a function to extend the recording time of a running recording.
(I guess the scheduling eventually needs some work to get it running with more than one capture card.)
Most certainly. This would be a good time to also incorporate real schedule conflict code.
We should also (if not already available) add a method to each recording plugin to query its state, if recording or idle, because this could be used to see if something is recording.
And if the plugin is recording, it should be possible to get a description/unique ID etc. of what it is recording.
Agreed. This should be no problem.
-Rob
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
