NextPVR Forums

Full Version: Stream not played: "Starting Device. Please Wait" until time-out
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
Hi,

My setup of NextPVR 5 under Debian 10 worked quite fine: I could successfully create a device, scan the channels from the SAT>IP source (4 DVB-C tuner implemented in a FRITZ!Box 6490 Cable Router) and could even retrieve the EPG data from the DVB-C stream. But when I try to playback a stream (tried with transcoder streaming profiles default and 720p), I only see the status "Starting Device. Please Wait..." and nothing appears.

This does not to be an issue of the Cable Router, as I can perfectly access the rtsp streams in VLC by downloading an m3u file from the Cable Router and having a direct connection to the Cable Router, without using NextPVR. So when I access the rtsp stream directly, the stream plays back, and when I open the same stream via NextPVR, I can only retrieve EPG data, but no stream for playback.

Therefore, I consulted the log file. After some initial tasks, NextPVR repeats the following steps many, many times before finally giving up. The following log information shows the portion that is repeated all the time while I see "Starting Device. Please Wait..." on the screen:

Code:
2021-06-03 20:26:55.327    [DEBUG][58]    {"status": "Starting Device. Please Wait...","final": false,"speed": 0,"duration": 0,"percentage": 0}
2021-06-03 20:26:55.829    [DEBUG][57]    Got request [192.168.4.52]: /services/service (channel.transcode.status)
2021-06-03 20:26:55.829    [DEBUG][57]    method=channel.transcode.status
2021-06-03 20:26:55.829    [DEBUG][57]    parameters:
2021-06-03 20:26:55.829    [DEBUG][57]       method: channel.transcode.status
2021-06-03 20:26:55.829    [DEBUG][57]       format: json
2021-06-03 20:26:55.829    [DEBUG][57]       sid: 3140d4b6-757c-4abd-bf6f-349a527481fc
2021-06-03 20:26:55.830    [DEBUG][57]       client_ip: 192.168.4.52
2021-06-03 20:26:55.830    [DEBUG][57]       user_agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:89.0) Gecko/20100101 Firefox/89.0
2021-06-03 20:26:55.830    [DEBUG][57]       host_callback: 192.168.4.173:8866
2021-06-03 20:26:55.830    [DEBUG][57]    GetStatus() got transcoder
2021-06-03 20:26:55.830    [DEBUG][57]    GetStatus()@2
2021-06-03 20:26:55.830    [DEBUG][57]    GetStatus()@3
2021-06-03 20:26:55.830    [DEBUG][57]    GetStatus()@exit

Unfortunately, my knowledge about NextPVR is not sufficient to identify any failure from the above log information. Similarly, I can also not identify an issue from the log information that preceeds the above repeated information once I click on a particular channel for playback and which is attached to this post in the file nrecord.log.

So I wonder what I could do to identify the source of the problem. I also tried to avoid a transcoding at all, but I do not know as how to enforce/achieve this.

I left the default settings in the transcoding sections at first, with the default streaming profile (which gives the same result) and then (as shown above in the log information) with the 720p streaming profile.  According to the default settings in the transcoding settings, transcoding is to be avoided.

Best regards,
Peter
You can't add txt files. Please upload the full zip you get from the browser.

Martin
Post updated with attached log file in zip
That's not what I asked for. For this problem I suggest enabling verbose logging (on the Setup page hold control) then try to play and then send the complete set of logs as zipped by NextPVR.

Note transcoding is typically only required when you use the web app, browsers don't know must broadcast standards.

Martin
I am sorry for the inconvenience caused by providing a portion of the log file. The log file is now updated in the original post and is retrieved from my NextPVR website. Unfortunately, I failed to identify an option to enable verbose logging. I have the Debian version of NextPVR 5 and also searched the forum and wiki as how to enable verbose logging, but I did not find an option.
Did you hold the control key when you were on the Settings Page in NextPVR? That should give you a new button Enable Verbose.

I did see one thing right away, please upgrade to 5.1.2 there are several SAT>IP changes

It does seem to be a source issue or firewall issue.

Code:
2021-06-03 13:33:12.224    [DEBUG][19]    Have received 0 bytes from rtsp source
2021-06-03 13:33:22.253    [DEBUG][19]    Have received 5786452 bytes from rtsp source (3 dropped packets)
2021-06-03 13:33:32.259    [DEBUG][19]    Have received 11079404 bytes from rtsp source (3 dropped packets)
2021-06-03 13:33:42.260    [DEBUG][19]    Have received 17823904 bytes from rtsp source (3 dropped packets)
2021-06-03 13:33:52.274    [DEBUG][19]    Have received 24528924 bytes from rtsp source (3 dropped packets)
2021-06-03 13:34:02.274    [DEBUG][19]    Have received 31582684 bytes from rtsp source (3 dropped packets)
2021-06-03 13:34:12.307    [DEBUG][19]    Have received 37873164 bytes from rtsp source (3 dropped packets)
2021-06-03 13:34:22.317    [DEBUG][19]    Have received 43874124 bytes from rtsp source (3 dropped packets)
2021-06-03 13:34:31.342    [ERROR][19]    System.Net.Sockets.SocketException (110): Connection timed out

Martin
Thanks for the hint to press the control key. Now I could enable verbosity. The updated log files are added after having performed a new test at 2021-06-03 21:23:00.

I am not sure whether the discussed log file excerpt from 2021-06-03 around 13:34 is relevent. Would you say that the dropping of a few packets causes NextPVR not toshow anything? My test for comparison was simple:

I have both NextPVR and my PC the in local network. I retrieve the rtsp stream either via NextPVR by opening a webbrowser on my PC or via VLC accessing the same rtsp stream via an m3u file. In the first case, the browser remains dark, in the second case, I see the stream in VLC.

The log file contains many different tests. Relevant should only be the last hour, i.e. everything after 2021-06-03 20:00:00, but not before.
You didn't update to 5.1.2 so we could be wasting time.

I suggest going to Setting->Access and disable Unauthenticated Access, make sure verbose is enabled and then see what happens with

ffplay http://192.168.4.173/live?channeloid=7348

assuming you aren't running headless. This will have cleaner logs and no transcoding

Martin
Updated to the most current version 5.1.2.210603. Disabled Unauthenticated Access. Enabled Verbosity agin. Run test again, video playback also not shown. Error message changes to "Failed to start requested stream". Log file attached with test at 2021-06-03 22:00.

Unfortunately, my server is headless. What could I do instead?
You would use

ffmpeg -i http://192.168.4.173:8866/live?channeloid=7308 -codec copy -f mpegts -y /dev/null

But the channel you are trying to play in the browser doesn't seem to exist so try 7308

2021-06-03 22:00:48.761 [DEBUG][43] does not have channel
2021-06-03 22:00:48.761 [DEBUG][43] StartStream(7348:3sat, LIVE&/mnt/multimedia/TV/.recordings/live-3sat-4327-5.ts) allocated handle: 0
2021-06-03 22:00:48.761 [DEBUG][43] Handle: 0
2021-06-03 22:00:48.761 [DEBUG][43] Failed to start stream. Handle 0.
2021-06-03 22:00:48.762 [DEBUG][20] [FFMPEG]: [http @ 0x55ede78ddd40] HTTP error 404 Not Found

Martin
Pages: 1 2 3