2020-05-26, 05:05 AM
Sure - no problem. I've been snowed under with day-job the last the couple of days, but hopefully should be able to get back to it tomorrow.
NextPVR Forums
Public
NextPVR Support
Linux
v5.0.5 not recording: failed to start stream
v5.0.5 not recording: failed to start stream
|
2020-05-27, 02:33 AM
Give this updated NShared.dll a go. I'm pretty confident this will resolve the issue.
I'd probably advise going to the Settings->Devices, holding the Ctrl key, deleting the Legacy device, then restarting NextPVR. After this you should be able to scan and setup the device again. I can't remember if you had another non-legacy HDHR device. If you do, and it offers to copy the configuration from your existing HDHR, I'd probably decline it, since these two types of HDHR require different tuning settings. (you can always use the AutoMerge feature to make them appear as one set of channels)
2020-05-28, 01:02 PM
Hi All,
I have 3 of the HDHomerun legacy devices (they are quite old) and I tried this updated file and it does not work for me. HDHomeRun DUAL Model: HDHR3-DT Device ID: 11105569 Firmware: 20200225 2020-05-28 21:58:54.591 [INFO][1] Version 5.0.5.200518 2020-05-28 21:58:54.734 [DEBUG][1] CaptureSource.LoadAll() 2020-05-28 21:58:54.750 [DEBUG][1] Added new device 'IPTV Device' 2020-05-28 21:58:55.473 [DEBUG][1] [ { "DeviceID": "11101593", "LocalIP": "192.168.106.144", "Legacy": 1, "BaseURL": "http://192.168.106.144", "DiscoverURL": "http://192.168.106.144/discover.json" }, { "DeviceID": "11101922", "LocalIP": "192.168.106.145", "Legacy": 1, "BaseURL": "http://192.168.106.145", "DiscoverURL": "http://192.168.106.145/discover.json" }, { "DeviceID": "11105569", "LocalIP": "192.168.106.146", "Legacy": 1, "BaseURL": "http://192.168.106.146", "DiscoverURL": "http://192.168.106.146/discover.json" } ] The channel scan works and returns the available channels. Couple of things dont work.. the EPG and Recording Looking at the log file, I see NextPVR trying to connect to the HDHR to get the EPG. What is puzzling is the IP address is it trying to connect to is itself, not the HDHR. The HDHR is at 192.168.106.146 but the tuning request is to 192.168.106.226 which is the IP address of the server. 2020-05-28 22:00:10.381 [DEBUG][22] Processing locator for '7 Adelaide' 2020-05-28 22:00:10.381 [DEBUG][22] CaptureSource.LoadAll() 2020-05-28 22:00:10.385 [DEBUG][22] HDHomeRunRecorder.StartStream() 2020-05-28 22:00:10.385 [DEBUG][22] ipaddress is 192.168.106.146 2020-05-28 22:00:10.385 [DEBUG][22] building graph 2020-05-28 22:00:10.385 [DEBUG][22] About to load channel from tuning 2020-05-28 22:00:10.385 [DEBUG][22] 11105569 is at 192.168.106.146 2020-05-28 22:00:10.385 [DEBUG][22] legacy tuning requesting auto:177500000 2020-05-28 22:00:10.405 [DEBUG][22] legacy tuning requesting program 1360 2020-05-28 22:00:10.423 [DEBUG][22] legacy tuning requesting target rtp://192.168.106.226:8020 2020-05-28 22:00:10.441 [DEBUG][22] Requesting: rtp://192.168.106.226:8020 2020-05-28 22:00:10.441 [DEBUG][22] RTP input source starting 2020-05-28 22:00:10.444 [DEBUG][22] StartStream [sink] allocated handle: 4 2020-05-28 22:00:10.444 [DEBUG][22] StartStream() returned handle=4 2020-05-28 22:00:10.444 [DEBUG][22] Allocated Handle: 4 2020-05-28 22:00:10.828 [DEBUG][24] Have received 1316 bytes from rtp source Is this right ?
2020-05-28, 01:13 PM
With the recording issue, I see the same log entries as others have posted before with the request for http:// instead of rtp://
Is there a configuration setting somewhere that can force it to use the rtp:// protocol ? 2020-05-28 22:01:42.678 [DEBUG][9] [ONE] at 05/28/2020 22:02 2020-05-28 22:01:42.678 [DEBUG][9] Requesting wake up for 'RecordingOID850' [ONE] at 05/28/2020 22:00 2020-05-28 22:01:42.678 [DEBUG][9] PowerManagement ScheduleWakeup (needs implementation) 2020-05-28 22:01:42.685 [DEBUG][9] DefaultDirectoryChoice: spread 2020-05-28 22:01:42.686 [DEBUG][9] allocating recording target filename: /home/recordings/Manual Recordings/ONE_20200528_22022204.ts 2020-05-28 22:01:42.687 [DEBUG][9] About to start recording (850 on 26): /home/recordings/Manual Recordings/ONE_20200528_22022204.ts... 2020-05-28 22:01:42.687 [DEBUG][9] (Recording is due to be stopped at 05/28/2020 22:04) 2020-05-28 22:01:42.687 [DEBUG][9] HDHomeRunRecorder.StartStream() 2020-05-28 22:01:42.687 [DEBUG][9] ipaddress is 192.168.106.146 2020-05-28 22:01:42.687 [DEBUG][9] building graph 2020-05-28 22:01:42.687 [DEBUG][9] About to load channel from tuning 2020-05-28 22:01:42.687 [DEBUG][9] source@1 2020-05-28 22:01:42.687 [DEBUG][9] Requesting: http://192.168.106.146:5004/tuner1/v1 2020-05-28 22:01:42.720 [ERROR][9] Failed to start stream: System.NullReferenceException: Object reference not set to an instance of an object. at NShared.Shim.InputSourceHTTP.StartStream(String target) at NShared.Shim.GenericCapture.StartStream(String target, String& reason) 2020-05-28 22:01:42.720 [DEBUG][9] Failed to start recording on allocated device (850:/home/recordings/Manual Recordings/ONE_20200528_22022204.ts): 'Connection refused Connection refused' 2020-05-28 22:01:42.720 [DEBUG][9] Looking for second chance device to perform recording... 2020-05-28 22:01:42.721 [DEBUG][9] Will try again after pre-padding period I copied in the NShared.dll from the post above..
2020-05-28, 01:39 PM
Also not working here, and same as the others. Trying to use http.
This is the MD5 of the .dll, just to make sure I used the correct one. e1f19977a5c32df3937f4cc8ad0b3574 NShared.dll Also restarted the machine, Just In Case.
2020-05-28, 01:49 PM
You must delete the tuner and restart NextPVR to readd the channel using the new dll. That is the md5sum of the dll that fixed it for me (in Docker). I really suggest full logs though.
This is the correct log message you want to see I made the same mistake at first but that is NextPVR telling the HDHR the target IP and port. 2020-05-28 22:00:10.423 [DEBUG][22] legacy tuning requesting target rtp://192.168.106.226:8020 Martin
I have deleted the two legacy tuners using CTRL, then restarted. When I login, the legacy devices are auto-added? Is that supposed to happen as part of initialization? In addition, when I then go to run the scan, it tells me that there is a channel configuration already in the database, and do I want to use it?[attachment=1632][attachment=1632]
2020-05-28, 03:22 PM
All tuners are added to the database at startup but nothing happens until you add channels.
You don't want to copy from you non legacy tuners. Martin
2020-05-28, 05:36 PM
(2020-05-28, 01:02 PM)djm2305 Wrote: Looking at the log file, I see NextPVR trying to connect to the HDHR to get the EPG. What is puzzling is the IP address is it trying to connect to is itself, not the HDHR. The HDHR is at 192.168.106.146 but the tuning request is to 192.168.106.226 which is the IP address of the server.Yes, that's normal. "rtp://192.168.106.226:8020" is where it's asking the HDHR to send the RTP data to. ie, "send the channel stream to NextPVR". (and in the case, it's also saying "nextpvr will be listening on port 8020")
2020-05-28, 05:47 PM
(2020-05-28, 03:16 PM)rkulagow Wrote: I have deleted the two legacy tuners using CTRL, then restarted. When I login, the legacy devices are auto-added? Is that supposed to happen as part of initialization? In addition, when I then go to run the scan, it tells me that there is a channel configuration already in the database, and do I want to use it?It discovers the device again when the backend application is restarted, or when you click 'rescan for devices'. In this case you've got two different types of HDHR, and they require different types of tuning information, so decline it's offer to copy the tuning information from the existing HDHR (I'll look into adding some logic to auto detect this, and not offer the option). |
|
|
