Reply to thread

Message: <blockquote data-quote="mm1352000" data-source="post: 1113349" data-attributes="member: 82144">Ahhhh, interesting. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />Logs show that TV Server definitely tried to record the 9:45 and 10:30 recordings.2014-12-04 09:44:02.312500 [scheduler thread(9)]: Scheduler: Time to record KOLDHD 9:44 AM-10:15 AM Manual (KOLDHD)However your tuner didn't want to play ball:2014-12-04 09:46:33.828125 [scheduler thread(9)]: dvb:  RunGraph returns: 0x8007001FNot 15 minutes earlier the tuner was working fine:2014-12-04 09:34:14.234375 [scheduler thread(9)]: Scheduler: Time to record KOLDHD 9:34 AM-10:00 AM Flip My Food With Chef Jeff...2014-12-04 09:34:14.859375 [scheduler thread(9)]: atsc:Tune:ATSC:tv:unknown KOLDHD Freq:193250 ONID:0 TSID:0 SID:3 PMT:0x20 FTA:True LCN:10000 phys:11 maj:13 min:1 mod:Mod256Qam ...2014-12-04 09:34:20.609375 [scheduler thread(9)]: subch:0-0 tswriter StartRecording...So, what could have caused this?My answer would be: the suspend + resume cycle at 9:36:44 - 9:39:44. Not all hardware and/or drivers can handle suspend/resume reliably.In my experience, once a driver decides it isn't happy, all subsequent tune requests - both for live TV and recordings - won't work correctly. This pattern continues until the TV service or PC are restarted.Sometimes timing can also be important. By timing, I mean the delay for "card" detection in the general section of TV Server configuration. Any attempt to interact with the tuner driver before it is ready can trigger the problem.If I were you, at this point I would confirm that live TV is not working. I say live TV, because it would be affected in just the same way as recordings... and is probably easier to test.After that I'd try to restart the TV service and see if live TV starts working again.If it does, I'd do some focussed standby/resume testing to confirm that the tuner stops working after standby/resume relatively consistently. It may not be 100% consistent due to our inability to measure/predict when Windows will load the tuner driver. You'll know the problem is triggered by standby/resume as long as it breaks live TV at least a few times.After confirming the problem, I'd try to increase the previously mentioned "card" (tuner) detection delay. It's a bit tricky to know what value to use, but I'd probably start at 30 seconds and increase in 10 second blocks until the problem is no longer reproducible. Values of less than 10 seconds probably won't make any difference; values of 60 seconds or more may be necessary for slow systems, or systems with a lot of peripheral hardware.Regards,mm</blockquote>

Verification