Another thread that I didn't want to hijack mentioned that VideoReDo detects/cuts commercials. Does it use comskip or does it use its own processor? How does it compare to comskip?
i'm having a bit of trouble with the npvr addon on my odroid c2 running libreelec 9 (kodi 18) when ever i try to play a tv channel as it starts to play it lock's kodi up and i have to ssh in and restart kodi as it stops responding to the remote. on my nuc running librelec 9 and my win laptop running kodi 18 it all works as it should. kodi logs included
On the client I was using the Recordings What's new menu to delete recordings with the Delete Key.
I unintentionally hit delete on a ongoing recording, probably because the screen refreshed after deleting others recordings, and that the prompt Are you sure you want to delete this recording? doesn't display the recording name.
This cancel the ongoing recording, delete it then the NPVR Service hang.
I Stop NPVR service, then start it.
I just discovered NextPVR and successfully installed it with my network and my tuner hardware on a Win7 32-bit laptop computer. I was able to install, configure tuners, scan for channels, get EPG and record a show.
I then seemingly installed NextPVR 4.23 on my Win2012R2 server, my tuner hardware showed up (two instances of two tuner hardware AVM Fritz!box 6490 cable, AVM Fritz!W-LAN repeater DVB-C). But I wasn't able to scan for channels.
When trying, I got an error "Unable to start device".
I also was not able to stop the PVR Recording service. When I tried, the error message was:
Code:
Unable to stop service: System.InvalidOperationException: Der Dienst NPVR Recording Service auf dem Computer . kann nicht beendet werden ---> System.ComponentModel.Win32Exception: Der Dienst kann zurzeit keine Steuerungsmeldungen annehmen
--- Ende der internen Ausnahmestapelüberwachung ---
bei System.ServiceProcess.ServiceController.Stop()
bei NCtrl.Program.Mai(String[] args)
I have my firewalls permanently disabled, I was able to reach the https localhost release notes URL mentioned in another thread. I restarted the server.
The part of the logs which looks relevant is:
Code:
2019-02-05 16:35:12.218 [DEBUG][1] Detected SAT>IP server desc:
<?xml version="1.0"?>
<root xmlns="urn:schemas-upnp-org:device-1-0" configId="0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<device>
<deviceType>urn:ses-com:device:SatIPServer:1</deviceType>
<friendlyName>FRITZ!Box 6490 Cable (kdg)</friendlyName>
<manufacturer>AVM Berlin</manufacturer>
<manufacturerURL>http://www.avm.de</manufacturerURL>
<modelDescription>FRITZ!Box 6490 Cable (kdg)</modelDescription>
<modelName>FRITZ!Box 6490 Cable (kdg)</modelName>
<modelNumber>kdg</modelNumber>
<modelURL>http://www.avm.de</modelURL>
<serialNumber></serialNumber>
<UDN>uuid:663d5d6c-f9f8-4bb4-84d4-C80E1466A4A8</UDN>
<iconList>
</iconList>
<serviceList>
<service>
<serviceType>urn:ses-com:service:satip:1</serviceType>
<serviceId>urn:ses-com:serviceId:satip</serviceId>
<controlURL>/upnp/control/satip</controlURL>
<eventSubURL>/upnp/control/satip</eventSubURL>
<SCPDURL>/satipSCPD.xml</SCPDURL>
</service>
</serviceList>
<presentationURL>http://192.168.94.254</presentationURL>
<satip:X_SATIPCAP xmlns:satip="urn:ses-com:satip">DVBC-2</satip:X_SATIPCAP>
</device>
</root>
2019-02-05 16:35:12.265 [DEBUG][1] X_SATIPCAP: DVBC-2
2019-02-05 16:35:12.265 [DEBUG][1] this is a new device
2019-02-05 16:35:12.265 [DEBUG][1] host: 192.168.94.254:1
2019-02-05 16:35:12.265 [DEBUG][1] CaptureSource.LoadAll()
2019-02-05 16:35:12.265 [DEBUG][1] Found existing SAT>IP device with host: 'FRITZ!WLAN Repeater DVB-C (663d5d6c-f9f8-4bb4-84d4-7CFF4DF63CDF)'
2019-02-05 16:35:12.265 [DEBUG][1] Found existing SAT>IP device with host: 'FRITZ!WLAN Repeater DVB-C (663d5d6c-f9f8-4bb4-84d4-7CFF4DF63CDF)'
2019-02-05 16:35:12.265 [DEBUG][1] Found existing SAT>IP device with host: 'FRITZ!Box 6490 Cable (kdg) (663d5d6c-f9f8-4bb4-84d4-C80E1466A4A8)'
2019-02-05 16:35:12.265 [DEBUG][1] Found existing SAT>IP device with host: 'FRITZ!Box 6490 Cable (kdg) (663d5d6c-f9f8-4bb4-84d4-C80E1466A4A8)'
2019-02-05 16:35:12.468 [DEBUG][1] host: 192.168.94.254:2
2019-02-05 16:35:12.468 [DEBUG][1] CaptureSource.LoadAll()
2019-02-05 16:35:12.484 [DEBUG][1] Found existing SAT>IP device with host: 'FRITZ!WLAN Repeater DVB-C (663d5d6c-f9f8-4bb4-84d4-7CFF4DF63CDF)'
2019-02-05 16:35:12.484 [DEBUG][1] Found existing SAT>IP device with host: 'FRITZ!WLAN Repeater DVB-C (663d5d6c-f9f8-4bb4-84d4-7CFF4DF63CDF)'
2019-02-05 16:35:12.484 [DEBUG][1] Found existing SAT>IP device with host: 'FRITZ!Box 6490 Cable (kdg) (663d5d6c-f9f8-4bb4-84d4-C80E1466A4A8)'
2019-02-05 16:35:12.656 [DEBUG][1] Detected SAT>IP server desc:
<?xml version="1.0"?>
<root xmlns="urn:schemas-upnp-org:device-1-0" configId="0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<device>
<deviceType>urn:ses-com:device:SatIPServer:1</deviceType>
<friendlyName>FRITZ!WLAN Repeater DVB-C</friendlyName>
<manufacturer>AVM Berlin</manufacturer>
<manufacturerURL>http://www.avm.de</manufacturerURL>
<modelDescription>FRITZ!WLAN Repeater DVB-C</modelDescription>
<modelName>FRITZ!WLAN Repeater DVB-C</modelName>
<modelNumber>avm</modelNumber>
<modelURL>http://www.avm.de</modelURL>
<serialNumber></serialNumber>
<UDN>uuid:663d5d6c-f9f8-4bb4-84d4-7CFF4DF63CDF</UDN>
<iconList>
</iconList>
<serviceList>
<service>
<serviceType>urn:ses-com:service:satip:1</serviceType>
<serviceId>urn:ses-com:serviceId:satip</serviceId>
<controlURL>/upnp/control/satip</controlURL>
<eventSubURL>/upnp/control/satip</eventSubURL>
<SCPDURL>/satipSCPD.xml</SCPDURL>
</service>
</serviceList>
<presentationURL>http://192.168.94.48</presentationURL>
<satip:X_SATIPCAP xmlns:satip="urn:ses-com:satip">DVBC-2</satip:X_SATIPCAP>
</device>
</root>
2019-02-05 16:35:12.656 [DEBUG][1] X_SATIPCAP: DVBC-2
2019-02-05 16:35:12.656 [DEBUG][1] this is a new device
2019-02-05 16:35:12.656 [DEBUG][1] host: 192.168.94.48:1
2019-02-05 16:35:12.656 [DEBUG][1] CaptureSource.LoadAll()
2019-02-05 16:35:12.672 [DEBUG][1] Found existing SAT>IP device with host: 'FRITZ!WLAN Repeater DVB-C (663d5d6c-f9f8-4bb4-84d4-7CFF4DF63CDF)'
2019-02-05 16:35:12.672 [DEBUG][1] Found existing SAT>IP device with host: 'FRITZ!WLAN Repeater DVB-C (663d5d6c-f9f8-4bb4-84d4-7CFF4DF63CDF)'
2019-02-05 16:35:12.875 [DEBUG][1] host: 192.168.94.48:2
2019-02-05 16:35:12.875 [DEBUG][1] CaptureSource.LoadAll()
2019-02-05 16:35:12.875 [DEBUG][1] Found existing SAT>IP device with host: 'FRITZ!WLAN Repeater DVB-C (663d5d6c-f9f8-4bb4-84d4-7CFF4DF63CDF)'
2019-02-05 16:37:31.787 [DEBUG][1] CaptureSource.LoadAll()
2019-02-05 16:37:31.927 [DEBUG][1] CaptureSource.LoadAll()
2019-02-05 16:37:52.350 [DEBUG][1] CaptureSource.LoadAll()
2019-02-05 16:38:06.570 [DEBUG][1] loading new bitmap data for: Background
2019-02-05 16:38:06.585 [DEBUG][1] loading new bitmap data for: DateTime
2019-02-05 16:38:15.429 [DEBUG][1] CaptureSource.LoadAll()
2019-02-05 16:38:15.492 [DEBUG][1] CaptureSource.LoadAll()
2019-02-05 16:38:28.352 [DEBUG][1] ScanDropTime: 1000
2019-02-05 16:38:28.414 [INFO][7] DigitalRecorder.StartStream(c:\nowhere\scan.ts)
2019-02-05 16:38:28.414 [DEBUG][7] CaptureSource.LoadAll()
2019-02-05 16:38:28.430 [DEBUG][7] SAT>IP uri: freq=114&sr=6900&mtype=256qam&msys=dvbc&pids=0,16,17,18
2019-02-05 16:38:29.946 [INFO][7] Creating BDA graph.
2019-02-05 16:38:30.024 [INFO][5] SAT>IP locked=False, level=44, quality=0
2019-02-05 16:38:30.024 [DEBUG][7] FindFilterByName failed to locate filter: MPEG-2 Demultiplexer
2019-02-05 16:38:30.039 [ERROR][7] Unexpected error building digital graph: System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei DShowHelper.ConnectPins(IGraphBuilder* pGB, IBaseFilter* pSourceFilter, Char* pinNameSource, IBaseFilter* pDestFilter)
bei Native.DigitalRecorderBase.BuildGraph(String deviceFilter, Int32 deviceInstance, Int32 commonInterface, Int32 commonInterfaceInstances, String& message)
bei NShared.DigitalRecorder.StartStream(ChannelMapping channelMapping, String target, String& reason)
2019-02-05 16:38:35.118 [INFO][5] SAT>IP locked=False, level=37, quality=86
2019-02-05 16:38:35.399 [INFO][1] DigitalRecorder.StopAllStreams()
2019-02-05 16:38:35.415 [ERROR][5] Unexpected error in RTSPKeepAlive (terminating thread): System.Threading.ThreadAbortException: Der Thread wurde abgebrochen.
bei System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout)
bei System.Threading.Thread.Sleep(Int32 millisecondsTimeout)
bei NShared.DigitalRecorder.RTSPKeepAlive()
2019-02-05 16:38:36.571 [DEBUG][1] CaptureSource.LoadAll()
2019-02-05 16:42:08.783 [DEBUG][1] /Settings/General/ShowNewInGuide is set to False
2019-02-05 16:42:08.783 [DEBUG][1] loading new bitmap data for: DateTime
2019-02-05 16:42:10.955 [DEBUG][1] storing Position (1):156,156
2019-02-05 16:42:10.955 [DEBUG][1] storing Size (1):789,473
2019-02-05 16:42:10.986 [INFO][1] Exiting...
2019-02-05 16:42:10.986 [INFO][1] Done.
Can you please help me finding a way to support my setup?
I just discovered NextPVR (being frustrated using the Plex DVR solution).
I tried installing it on my Win7 laptop and everything worked well (just for testing purposes).
I could scan for channels and get EPG, record shows from different tuner hardware.
Then, I went for installation on Win2012 Server (64-bit) and while it installed without error, trying to scan channels for any SAT-IP tuner I own (AVM Fritz!box 6490 cable, AVM Fritz!W-LAN repeater DVB-C ).
After installation, going to Settings - Devices shows noth my tuner hardware devices (each with two instances). Clicking on any of them (on W2k12) then configure for Kabel Deutschland and scan for channels.thtows an error "Unable to start device".
I simply cannot access any of the devices.
I have all firewalls disabled, I can access the https localhost release note URL mentioned in another thread.
And I cannot stop or re-start the PVR recording service.
The following error shows:
Unable to stop service: System.InvalidOperationException: Der Dienst NPVR Recording Service auf dem Computer . kann nicht beendet werden ---> System.ComponentModel.Win32Exception: Der Dienst kann zurzeit keine Steuerungsmeldungen annehmen
--- Ende der internen Ausnahmestapelüberwachung ---
bei System.ServiceProcess.ServiceController.Stop()
bei NCtrl.Program.Mai(String[] args)
This is the part of the logs that look interesting to me...
As many of you know, the Colossus IR Blaster is very weak. It worked just fine with my Dishnetwork equipment but when I converted over to Xfinity, I had many problems getting the IR blaster to consistently change the channels. I tried many different options and here is what worked for me:
2. I unscrewed the bottom of the Pace PX022ANM and exposed the IR receiver. Once the bottom was removed you can get direct access to the IR receiver and then I pointed the Colossus IR blaster directly at the receiver. To do this, I had to put a piece of aluminum foil underneath it to angle it downward at the receiver then I used aluminum foil tape to hold it in place. You may be asking why I used aluminum. This was to make sure the IR signal reflected at is maximum potential. I had to tape the Pace bottom back on because once the IR blaster was attached there was too much physical interference for the bottom to fit back on nicely.
3. Minimize heat sources. Do not put any devices underneath the Cable Box that will create heat. In addition, I had to elevate the box using spacers to maximize venting. In addition to heat sources, keep away from Plasma TVs and fluorescent lights. All of these interfere with the IR signals and can drive inconsistency.
With these three things in place, I now have reliable channel changing. The third item was very important to get reliability. When I moved the box away from my heat sources and elevated it, I went from 60-70% reliability to 100% reliability.
Here are some things I tried to get a stronger IR signal with no success:
1. Use an IR repeater. Did not work and just was not able to boost the signal using an IR repeater.
2. Bought a USBUIRT and used IRSS to learn the signal. My Harmony Ultimate (did not have a Xfinity IR remote) worked fine with the box and had plenty of strength. I tried learning the signal with the USBUIRT and IRSS using the Harmony signal with no success. I was able to get the USBUIRT to learn with Sage TV but I really did not want to switch to Sage TV. Something was not working in the learning process and these programs (IRSS and Sage TV) have not been updated in years.
3. Bought the single IR blaster from Hauppauge that does not have the IR receiver. There was no change in the IR blaster strength. Even tried a different IR blaster that does have the IR receiver but still did not change the IR strength.
So there you have it. What worked and what did not work for me. I hope this helps someone with the same problems!
Considering subscribing to Schedules Direct and curious where the XLMTV file will reside? Is it in the scripts folder? I'm assumming I have the option of getting the xlmtv file vs the json method.
Thanks.
I have two hdhomeruns and when I go to the channel setup I notice that at least one channel that appears in hdhomeruns channel list does not appear in nextpvr's channel list. I'm using schedulesdirect as my EPG provider if that helps.
I clicked on devices in the setup dialog, followed by Scan but the channel does not appear in the scanned channels. Any idea what could be going on? I've attached the nextpvr log.