2013-10-14, 12:19 PM
Hi, first I want to say how great of a program this is. Love it!!!
Here's the issue i have with the new update. Every morning since I updated from 2.6.2 to 3.1.1 I wake up and notice the little "N" in the tray is red, meaning one of my HDHomerun tuners is being used. When I click the N icon, one of the tuners says: Recording c:\devxxxxxx\null.ts When it shows that, only one tuner can be used, so I have to restart the NPVR service to clear it and be able to use both tuners.
I don't have anything recordings scheduled in the morning so i took a look at the NRecord.log and it seemed to be related to my EPG update set for 3am. Unfortunately, I saved the wrong log file so I need to pull one out after tomorrows update. I did save the correct ndigitalhost20.log which shows that null.ts issue also, so i'll post that.
I tried searching for this issue and found a few people with similar issues, but none seemed to be resolved (or from what I read). I'm running windows 8 and my computer is always on (never sleeps).
The one thing I noticed on the NRecord.log (which again, i saved the wrong one so lost it) is that when 2 of my stations which do not pull EPG info from schedules direct (via mc2xml) try to update their epg info through the channel , the (c:\devxxxxxx\null.ts) shows up.
I was running 2.6.2 for months and never experienced this issue. Can anyone chime in?
Thanks
Here's the issue i have with the new update. Every morning since I updated from 2.6.2 to 3.1.1 I wake up and notice the little "N" in the tray is red, meaning one of my HDHomerun tuners is being used. When I click the N icon, one of the tuners says: Recording c:\devxxxxxx\null.ts When it shows that, only one tuner can be used, so I have to restart the NPVR service to clear it and be able to use both tuners.
I don't have anything recordings scheduled in the morning so i took a look at the NRecord.log and it seemed to be related to my EPG update set for 3am. Unfortunately, I saved the wrong log file so I need to pull one out after tomorrows update. I did save the correct ndigitalhost20.log which shows that null.ts issue also, so i'll post that.
I tried searching for this issue and found a few people with similar issues, but none seemed to be resolved (or from what I read). I'm running windows 8 and my computer is always on (never sleeps).
The one thing I noticed on the NRecord.log (which again, i saved the wrong one so lost it) is that when 2 of my stations which do not pull EPG info from schedules direct (via mc2xml) try to update their epg info through the channel , the (c:\devxxxxxx\null.ts) shows up.
I was running 2.6.2 for months and never experienced this issue. Can anyone chime in?
Thanks