Stream not played: "Starting Device. Please Wait" until time-out
|
2021-06-03, 08:49 PM
I needed to enable unauthenticated access in order to submit the ffmpeg command without error 401. However, the result was then HTTP error 404 not found for both 7348 and 7308. My channel list looks fine, but probably the mapping from RTSP URLs for SAT>IP and the NextPVR channel IDs is somehow broken?
2021-06-03, 08:54 PM
Yest I thought I mentioned disabling security. I agree try a rescan and if that fails upload verbose logs for sub.
Martin
2021-06-03, 11:57 PM
I reported this issue after having already rescanned multiple times. So I am afraid to tell you that this did not alter anything. The previously submitted log file logs-20210603-2200.zip was already in verbose mode, after a full rescan (done yesterday) and covers the failed playback at 2021-06-03 22:00. Is there anything further I could provide?
2021-06-04, 12:19 AM
Do you have the verbose logs from the ffmpeg test?
Martin
2021-06-04, 06:46 AM
The previous execution of ffmpeg resulted in an output of HTTP error 404. I thought ffmpeg will output to the screen and there was nothing more than this error message. However, I rescanned the channels right again and started at 2021-06-04 08:40 to update the EPG which now does not really work as the NextPVR output simply showed 0 updates without going through the streams. After this rescan, not even the playback is broken, but also EPG.
2021-06-04, 10:03 AM
Installation history: When I installed nextpvr-helper-5.1.1.210329.deb for the first time, stream playback worked right out of the box. No JellyRoll installed, therefore no EPG in Emby. All following steps were refining the NextPVR / Emby setup without touching my network or DVB-C source.
I installed JellyRoll and upgraded to nextpvr-helper-5.1.2.210603.deb. The playback of streams did not longer work. I uninstalled nextpvr-helper-5.1.2.210603.deb and went back to nextpvr-helper-5.1.1.210329.deb including JellyRoll. EPG updates worked fine, but playback of streams did not work. I contacted you the first time and provided log files. According to your instructions, I upgraded to nextpvr-helper-5.1.2.210603.deb which caused that also EPG updates broke. At present nothing works, neither EPG updates nor playback of streams. I can only successfully scan for channels and store them.
2021-06-04, 12:06 PM
There is a very weird error in the log as it seems to skip the good channel, but only sub can help.
Code: 2021-06-04 08:40:56.400 [DEBUG][42] StreamNative@8 (/mnt/multimedia/TV/.recordings/live-3sat-8002-2.ts)Since my suggestion earlier to rescan didn't help, I would consider removing all the channels from the device by clicking the trashcan icon on the right and then scanning fresh. Martin
2021-06-04, 12:11 PM
Sorry to say, but when I told you that I have already rescanned multiple times, I ALWAYS deleted the existing channels so that the channel list was empty and started with a fresh scan again. This is what I also did last evening. So the latest log files are already based on a fresh scan. Is there no way to increase verbosity? A weird error is occurring and we cannot see any information.
What do you mean by "but only sub can help"?
2021-06-04, 12:25 PM
(This post was last modified: 2021-06-04, 01:14 PM by mvallevand.)
Sub is the author of NextPVR and it is closed-source. Only he can explain that odd sequence but I don't think it requires any more log details, it looks to me like the data is bad.
Another option is to stop the service rename npvr.db3 and restart the server to start completely fresh. It is also not clear why there is no indication that you have SAT>IP at startup in the logs. On Settings->General is "Scan devices at startup" checked? It appears that logging disappeared after your upgraded to 5.1.2 Do you restart the service or restart the server when you make changes? It is possible that you haven't scripted startup to have NextPVR wait for the network to be available. Martin
I always restart nextpvr upon applying changes, just to make sure:
Code: sudo service nextpvr-server restartWorth to note is that the SAT>IP device (DVB-C tuner) is at 192.168.0.1 and NextPVR at 192.168.4.X, i.e. they do not reside within the same LAN. Therefore, scanning a device (applicable only for the same LAN) would not return any result as there is no SAT>IP device in 192.168.4.X. Instead, I populated /etc/nextpvr-server.conf with SATIP_DEVICES=http://192.168.0.1:49000/satipdesc.xml to gain access. The network connections between 192.168.0 and 192.168.4 are up and running. As mentioned, I do not encounter any difficulties to playback an RTSP data stream via VLC in 192.168.4.X that is retrieved from 192.168.0.X. So I wonder why NextPVR has difficulties when VLC can cope with this network setup. However, it turned out that the upgrade to the latest version killed the line SATIP_DEVICES=http://192.168.0.1:49000/satipdesc.xml in etc/nextpvr-server.conf. So I added it again and restarted nextpvr. With this change, it appears that I am now again at a similar state as prior the update to the latest version. By doing so, nextpvr is capable of performing the EPG update again and the rtsp streams are parsed. Thanks a lot for your considerations so that I could identify this issue. Unfortunately, I am still away from sucessfully streaming the video, but at least the situation did not get worse when applying an update... So I added new log files and hope that this makes a difference! I tried streaming at 2021-06-04 17:12 |
|
|
