12/05/2007 01:37:44 1 GetConflictingSchedules: Schedule = Star Trek on 2 12/05/2007 02:00:00 - 12/05/2007 02:50:00
12/05/2007 01:37:44 1 GetConflictingSchedules: Cards.Count = 1
12/05/2007 01:37:44 1 AssignSchedulesToCard: schedule = Star Trek on 2 12/05/2007 02:00:00 - 12/05/2007 02:50:00
12/05/2007 01:37:44 1 AssignSchedulesToCard: free on card 0, ID = 1
12/05/2007 01:37:44 1 GetConflictingSchedules: newEpisode = Star Trek on 2 12/05/2007 02:00:00 - 12/05/2007 02:50:00
12/05/2007 01:37:44 1 AssignSchedulesToCard: schedule = Star Trek on 2 12/05/2007 02:50:00 - 12/05/2007 03:40:00
12/05/2007 01:37:44 1 AssignSchedulesToCard: card 0, ID = 1 has schedule = Star Trek on 2 12/05/2007 02:00:00 - 12/05/2007 02:50:00
12/05/2007 01:37:44 1 AssignSchedulesToCard: free on card 0, ID = 1
12/05/2007 01:37:44 1 GetConflictingSchedules: newEpisode = Star Trek on 2 12/05/2007 02:50:00 - 12/05/2007 03:40:00
It should be imposible for GetConflictingSchedules to work the above logic in the TVSERVER enviroment .
Multiple simultaneous recordings within a transponder/mux is allowed and yet the above logic is stopping a schedule from starting until another has finsihed (both on same channel )
Can this be fixed as it is the root of the 'same name' overlapped schedule failure/start delay.
12/05/2007 01:37:44 1 GetConflictingSchedules: Cards.Count = 1
12/05/2007 01:37:44 1 AssignSchedulesToCard: schedule = Star Trek on 2 12/05/2007 02:00:00 - 12/05/2007 02:50:00
12/05/2007 01:37:44 1 AssignSchedulesToCard: free on card 0, ID = 1
12/05/2007 01:37:44 1 GetConflictingSchedules: newEpisode = Star Trek on 2 12/05/2007 02:00:00 - 12/05/2007 02:50:00
12/05/2007 01:37:44 1 AssignSchedulesToCard: schedule = Star Trek on 2 12/05/2007 02:50:00 - 12/05/2007 03:40:00
12/05/2007 01:37:44 1 AssignSchedulesToCard: card 0, ID = 1 has schedule = Star Trek on 2 12/05/2007 02:00:00 - 12/05/2007 02:50:00
12/05/2007 01:37:44 1 AssignSchedulesToCard: free on card 0, ID = 1
12/05/2007 01:37:44 1 GetConflictingSchedules: newEpisode = Star Trek on 2 12/05/2007 02:50:00 - 12/05/2007 03:40:00
It should be imposible for GetConflictingSchedules to work the above logic in the TVSERVER enviroment .
Multiple simultaneous recordings within a transponder/mux is allowed and yet the above logic is stopping a schedule from starting until another has finsihed (both on same channel )
Can this be fixed as it is the root of the 'same name' overlapped schedule failure/start delay.