New Install - Stream Failed Transcoder Exited

[mvallevand]

To follow the install directions didn't you map your recording directories? The device line would be added the same way. The line you need again is

Code:

docker run -d \
    --volume /home/user/config:/config \                    
    --volume /home/user/videos:/recordings \
    --volume /home/user/videos:/buffer \
    --device /dev/dri:/dev/dri
    --publish 8866:8866 \
    nextpvr/nextpvr_amd64:latest

Martin

[fire fuze]

Nope, Didn't do anything of the sort, there was no prompt or anything obvious asking for any command line inputs - everything was done through the Docker GUI. Couple clicks and it was up and running as such - I had tested a recording and it did work so directories must be there to some extent?

There is a terminal within the container when it's running, I tried those commands there to see if they work, they didn't return an error but still I can't open any streams.

Might try run it on a Windows VM instead, don't think performance would be great though but seems I can't configure what needs to be configured on the NAS?

[sub]

In your logs, it looked like you have mapped a directory into the container as /buffer:

2020-03-27 23:48:07.324 [ERROR][14] Unexpected error creating TSWriter map: System.IO.DirectoryNotFoundException: Could not find a part of the path '/buffer/live-Three-1-1.ts.map'.

[mvallevand]

He didn't configure anything so that makes sense.

Martin

[sub]

Nope, Didn't do anything of the sort, there was no prompt or anything obvious asking for any command line inputs - everything was done through the Docker GUI. Couple clicks and it was up and running as such - I had tested a recording and it did work so directories must be there to some extent?

You have to map in the various folders. It can all be done in the Docker UI. Below is the page I used to set it up on my Synology device.

If you need to use hardware transcoding, which requires adding --device /dev/dri:/dev/dri, then you need to create the container from an ssh shell. After this, the container will appear in the Synology Docker app, and you can just stop/start your container from the UI like you normally would. (this is a little more advanced though, so I'd just focus on getting the folders mapped in first)

[sub]

He didn't configure anything so that makes sense.

Yep, I got that.

[fire fuze]

Nope, Didn't do anything of the sort, there was no prompt or anything obvious asking for any command line inputs - everything was done through the Docker GUI. Couple clicks and it was up and running as such - I had tested a recording and it did work so directories must be there to some extent?

You have to map in the various folders. It can all be done in the Docker UI. Below is the page I used to set it up on my Synology device.

If you need to use hardware transcoding, which requires adding --device /dev/dri:/dev/dri, then you need to create the container from an ssh shell. After this, the container will appear in the Synology Docker app, and you can just stop/start your container from the UI like you normally would. (this is a little more advanced though, so I'd just focus on getting the folders mapped in first)

And just like that I now have working TV! That screenshot was exactly what I needed. Thanks

Will see how I go without HW transcode for now

[caledoniangold]

I'm trying to do the same thing here but am also entirely clueless. Any help would be appreciated. I have got nextpvr installed on the NAS (220+) but am stuck at that point. Thanks in advance!

[mvallevand]

Did you find adding --device /dev/dri:/dev/dri to the other things you need to configure that difficult? Not all devices will have /dev/dri

Martin

[groenator]

Hi Martin,

I can confirm I have the same problem. I configured the Docker container as it was described in the documentation. I mapped the /dev/dri devices and enable privileges mode. 

I have some logs where you can have a look. I tried different types of HW transcoding but none of them worked well. In my case, I think the issue is happening with AAC audio codec that cannot be converted. 

Logs from docker container:

Code:

nextpvr    | [67] [FFMPEG]: [h264 @ 0x558ce0796980] no frame!
nextpvr    | [67] [FFMPEG]: [h264 @ 0x558ce0796980] SPS unavailable in decode_picture_timing
nextpvr    | [30] [FFMPEG]: [h264 @ 0x558ce0796980] non-existing PPS 0 referenced
nextpvr    | [33] [FFMPEG]: [h264 @ 0x558ce0796980] SPS unavailable in decode_picture_timing
nextpvr    | [33] [FFMPEG]: [h264 @ 0x558ce0796980] non-existing PPS 0 referenced
nextpvr    | [33] [FFMPEG]: [h264 @ 0x558ce0796980] decode_slice_header error
nextpvr    | [33] [FFMPEG]: [h264 @ 0x558ce0796980] no frame!
nextpvr    | [67] [FFMPEG]: [h264 @ 0x558ce0796980] SPS unavailable in decode_picture_timing
nextpvr    | [67] [FFMPEG]: [h264 @ 0x558ce0796980] non-existing PPS 0 referenced
nextpvr    | [67] [FFMPEG]: [mpegts @ 0x558ce0787ae0] decoding for stream 0 failed
nextpvr    | [67] [FFMPEG]: [mpegts @ 0x558ce0787ae0] Could not find codec parameters for stream 0 (Video: h264 ([27][0][0][0] / 0x001B), none): unspecified size
nextpvr    | [67] [FFMPEG]: Consider increasing the value for the 'analyzeduration' and 'probesize' options
nextpvr    | [67] [FFMPEG]: Input #0, mpegts, from 'http://127.0.0.1:8866/live?channeloid=7534&transcoder=94e83896-8d64-48f0-875a-91857bf8a85b&client=7c7d8eeb-15ce-47c0-87a4-d8762a8a1528':
nextpvr    | [67] [FFMPEG]:   Duration: N/A, start: 34770.005167, bitrate: N/A
nextpvr    | [67] [FFMPEG]:   Program 1
nextpvr    | [67] [FFMPEG]:     Metadata:
nextpvr    | [67] [FFMPEG]:       service_name    : Service01
nextpvr    | [67] [FFMPEG]:       service_provider: FFmpeg
nextpvr    | [67] [FFMPEG]:     Stream #0:0[0x100]: Video: h264 ([27][0][0][0] / 0x001B), none, 25 fps, 25 tbr, 90k tbn, 180k tbc
nextpvr    | [67] [FFMPEG]:     Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 194 kb/s
nextpvr    | [67] [FFMPEG]: [hls @ 0x558ce078ac60] dimensions not set
nextpvr    | [67] [FFMPEG]: Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument
nextpvr    | [67] [FFMPEG]: Stream mapping:
nextpvr    | [67] [FFMPEG]:   Stream #0:0 -> #0:0 (copy)
nextpvr    | [67] [FFMPEG]:   Stream #0:1 -> #0:1 (copy)
nextpvr    | [67] [FFMPEG]:     Last message repeated 1 times
nextpvr    | [82] Client has disconnected
nextpvr    | [95] Deleting web temp files

What I did found interesting is that I can play this channel when I use Kodi or Emby clients, but, I cannot play this channel when I use the web interface of nextPvr. 

Another issue that I have with is recordings, I recorded a show and the .ts file is broken. When I open the recorded file with VLC it doesn't work, I get a black screen. 

I tried multiple types of recording profile, like not keeping the original content, using 720/1080 pi. Same issue. I changed from CPU to VAAPI device but without any luck.
However, if I open the file with Emby or Kodi it stops a bit but eventually plays well.