Hello Mr. Sub.
I have a newly installed machine x64 Win 10 and a Hauppauge HD-PVR 2. Everything is working like a champ except when I watch live tv. No audio comes through while in the live tv mode. However, recording and playback are working fine. Can you look at the attached log and give me a clue? I have sniffed the forums here, but have not found the solution yet.
I appreciate your hard all of your hard work.
I am not having any luck using comskip--either with parallel or post processing. FIles get created in my directory, but they don't register the breaks when watching the show through NPVR.
Here's the log:
Quote:2015-11-16 08:07:23.125 [DEBUG][9] About to start recording (9207 on 22): E:\Recordings\Leave It to Beaver\Leave.It.to.Beaver.S06E19.Beavers.Good.Deed.ts...
2015-11-16 08:07:23.125 [DEBUG][9] Free space 47319896064 (E:\)
2015-11-16 08:07:23.125 [DEBUG][9] Asking NDigitalHost to start: E:\Recordings\Leave It to Beaver\Leave.It.to.Beaver.S06E19.Beavers.Good.Deed.ts
2015-11-16 08:07:23.346 [DEBUG][9] Temp at 11/16/2015 8:07:33 AM
2015-11-16 08:07:23.346 [DEBUG][9] Started recording (9207:3:E:\Recordings\Leave It to Beaver\Leave.It.to.Beaver.S06E19.Beavers.Good.Deed.ts)
2015-11-16 08:07:23.426 [DEBUG][9] Starting: C:\Users\Public\NPVR\Scripts\ParallelProcessing.bat "E:\Recordings\Leave It to Beaver\Leave.It.to.Beaver.S06E19.Beavers.Good.Deed.ts" 5 9207 22 "Leave It to Beaver"
2015-11-16 08:07:24.264 [DEBUG][25] Using URL: https://json.schedulesdirect.org/20141201
2015-11-16 08:07:24.363 [DEBUG][25]
{"account":{"expires":"2016-09-27T07:14:30Z","messages":[],"maxLineups":4},"lineups":[{"lineup":"USA-OTA-91325","modified":"2015-11-16T12:16:30Z","uri":"\/20141201\/lineups\/USA-OTA-91325"}],"lastDataUpdate":"2015-11-16T13:31:09Z","notifications":[],"systemStatus":[{"date":"2015-09-08T00:00:00Z","status":"Online","message":"No known issues."}],"serverID":"20141201.web.1","code":0}
2015-11-16 08:34:00.044 [DEBUG][9] Stopping recording (9207 on 22). Past end time of recording. 3
2015-11-16 08:34:00.144 [DEBUG][9] StopStream(3)
So it shows activated... ParallelProcessing.bat has:
I have been using a USBUIRT with GBPVR/NextPVR since 2004 and a recent Windows 10 update has given my first crash with that device. Rather, lots of crashes on windows startup, with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED errors all over.
Analysis using "WhoCrashed" of 7 minidumps all look like below.
The only ftdibus.sys-based device on my PC is the USBUIRT.
This thread viewtopic.php?f=1&t=5606 describes how to roll your own driver, but initially I was too scared to try it.
But I did try and it seems to have worked. I am pretty pleased with myself
Code:
[url=http://usbuirt.com/phpBB3/viewtopic.php?f=2&t=8855&p=13894#]SELECT ALL[/url]On Mon 11/16/2015 12:37:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111615-13828-01.dmp
This was probably caused by the following module: ftdibus.sys (ftdibus+0x9363)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801CB054C90, 0xFFFFD0013DD9AF08, 0xFFFFD0013DD9A720)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ftdibus.sys
product: FTDIChip CDM Drivers
company: FTDI Ltd.
description: FTDIBUS USB Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ftdibus.sys (FTDIBUS USB Driver, FTDI Ltd.).
Google query: FTDI Ltd. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
If you use this, you may need to follow his point 17 and sign it. I actually temporarily disabled unsigned drivers while it loaded but then used that.
Code:
17) at this point, the driver files will have been copied into their correct locations, but the driver will not load because it is unsigned. To deal with the unsigned driver, you need to take some extra measures:
a) download Driver Signature Enforcement Overrider 1.3b at [URL]http://www.ngohq.com/home.php?page=dseo[/URL]
b) right-click the downloaded file dseo13b.exe, and select "Run as administrator"
c) consider reading the instructions to understand what you will be doing
d) select "Enable Test Mode"
e) select "Sign a System File"
f) enter "c:\windows\system32\drivers\ftdibus.sys"
18) now the driver is signed. Reboot, and you should be set.
I am not sure if I am allowed to post it (sub or mods please remove if not) but it is attached for now.
Just wondering does anyone use the N3700 or similar as a NextPVR Server, or have any thoughts on it? Seems a great deal, so I might take the plunge and order one. The energy savings should make it pay for itself in about 18 months.
Got asked to post this here instead of Emby site -
Some help would be appreciated to find my missing TV tuner. On Win 10 pro 64bit I have a Hauppauge DVB-S card installed in main PC, which has disappeared from Emby (see attached screenshot) and hence no TV guide. The card works fine using the Hauppauge app, including TV guide and NPVR also works fine, including TV guide. Think this is since the latest NPVR Emby plug-in update.
When I browse to the localhost:8866 I get this 'unable to write' thingy........
Attachments are logs (hopefully), images of no tuner appearing in Emby, error on navigating to '8866', and NPVR showing TV Guide working fine.
I was not able to watch Live TV with NextPVR, but it had been working fine previously. It turns out that the NextPvr Service had been stopped. Enabling it allowed TV to work again. But, what caused the service to be stopped in the first place?
I have just installed and configured NextPVR on my HTPC. I am using Kodi as the front end. I have to say that your software works great! I have tried three different PVR backends with my system and yours is the only one that works. Great job! Now to my question.
I have configured my system so that the computer wakes up to make scheduled recordings. This part is working great. However I have found that after the recording, the backend does not shut down the computer. Is there some setting for this, or is that functionality not programmed in?
