Reply to thread

Message: <blockquote data-quote="mm1352000" data-source="post: 1177099" data-attributes="member: 82144">Hello and welcome to the forum! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />...and may I also commend you on an excellent first post. You've provided all the information anybody would need to help you. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up    (y)" loading="lazy" data-shortname="(y)" />The reason the recording is not performed is as indicated in the TV service log file:[2016-02-29 19:59:04,827] [Log  ] [scheduler thread] [DEBUG] - Scheduler: Check recordings for schedule The Bachelor...[2016-02-29 19:59:04,847] [Log  ] [scheduler thread] [DEBUG] - Scheduler.CancelSchedule: The Bachelor 2/29/2016 8:00:00 PM[2016-02-29 19:59:04,996] [Log  ] [scheduler thread] [INFO ] - diskmanagement: recording The Bachelor ended. type:Once max episodes:2147483647[2016-02-29 19:59:05,067] [Log  ] [scheduler thread] [INFO ] - Scheduler: Schedule 2/29/2016 8:00:00 PM-The Bachelor (-) has already been recorded (2/22/2016 7:59:16 PM) - aborting...What this is saying is that based on your scheduler settings:<a href="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/07_Recording#Scheduler" target="_blank">http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/07_Recording#Scheduler</a>...TV Server thinks it does not need to record the episode. It thinks this because it has already recorded an episode with the given episode name/number, and you've told it not to record duplicate episodes.Now, from the log file we can see that the episode name/number of this particular episode is "-". That's obviously completely bogus. TV Server could perhaps do better to recognise that it is bogus and skip the is-previously-recorded check. However if possible, a better solution would be to fix this problem at the source: your EPG data.I can see that your EPG data comes from SchedulesDirect via the SchedulesDirect plugin. I can also see that you have TVDB lookups enabled. So, either the episode name/number as provided by SchedulesDirect is bogus... or the plugin and/or TVDB lookup process it performs is adding the bogus detail.Based on what I see in the SchedulesDirect plugin code, I think it may be responsible for this problem. You may not understand this, but here it is anyway:[code]const string EMPTY = "-";...string zEpisode  = string.IsNullOrEmpty(tvProgram.Subtitle) ? EMPTY : tvProgram.Subtitle;...string zSeriesNum  = string.IsNullOrEmpty(tvProgram.Series) ? EMPTY : tvProgram.Series;string zEpisodeNum  = string.IsNullOrEmpty(tvProgram.SyndicatedEpisodeNumber) ? EMPTY : tvProgram.SyndicatedEpisodeNumber;[/code]In other words, when the episode details are not available, it looks like the SD plugin is assigning "-". That's... not the best thing to do.So, to reiterate: this problem appears to be caused by the combination of your TV Server scheduler settings (prevent duplicate recordings), the SD plugin adding bogus episode details, and TV Server not recognising that the episode details are bogus.The solution could be one or more of the following:<ul> <li data-xf-list-type="ul">you change your TV Server settings to not prevent duplicate recordings</li> <li data-xf-list-type="ul">you report the problem to the SD plugin developer(s)/maintainer(s) and they fix it by not adding bogus episode details anymore </li> <li data-xf-list-type="ul">you report the problem to Team MediaPortal and we try to fix it by recognising and ignoring bogus episode details</li> <li data-xf-list-type="ul">you switch to a different EPG data source which doesn't provide bogus episode details</li> </ul></blockquote>

Verification