Digard While that would serve the purpose quite well, I think that a simple pop-up to raise the awareness at DVR recording registration would be preferable. No need to visibly checking charts.
It was just an idea for a quick fix that could be implemented at the WebUI level.
Detecting a potential conflict is not that simple when you take into account how many steps there are between a scheduled recording and a physical tuner.
A recording is scheduled on a channel, a channel can be provided by multiple services. Each service is supplied from a mux, a mux can be associated with a single network and a network can originate from multiple tuners. All along this chain, there are multiple priorities and other settings to take into account. As well as that, every timer needs to be expanded and compared to the scheduled recordings.
In summary, at any time, how many unique muxes are required to service the scheduled recordings plus expanded timers vs how many free tuners are available will determine if a conflict will occur. As @davep has already pointed out, this is non-deterministic, consequently, the best the user can be present with a list of potential conflicts to be resolved manually.
@davep and I have produced various versions of this, so it is possible. How to incorporate this into TVH to be able to provide live feedback to a user when any object changes that impacts potential conflicts without placing undue load on the server is the question. Simply adding/modifying/removing/disabling/enabling a tuner or a network or a mux or a service or a channel or scheduled recording could have an impact on conflicts and the whole thing will need to be recalculated.
