"IPTV" recording is murdering my CPU

[Coxeroni]

New NextPVR user here, version 5.0.1.200103 through the official nextpvr amd64 docker image.

I am using an enigma2 set-top cable box as a tuner source. The channels are shared in the local network via m3u8 playlists and imported into NextPVR. The STB just passes on the unprocessed transport stream.

When I start a recording, the CPU usage of my Xeon E3-1225 v6 boosts to 100 %, the source being ffmpeg treating the "buffer" file (not the actual recorded file).

How do I get rid of this? Can/should I set buffer time to 0? Or is it related to the recording in general?

I read here about substituting a .dll file, something I probably cannot do in the docker container.

[sub]

First thing we need to do is determine if this is about input or output, which are the two different places ffmpeg can be used.

Where are you watching? If it's in the web app, ie in the browser, then it's having to convert the video to a format that can be displayed in the browser. If you watch from NextPVR using a player like VLC, opening the network url http://<ipaddress:8866>/live?channel=12 (pick a channel number), does it help the CPU? This is the output side of things.

The other place it can happen with IPTV devices is at input, getting the stream into NextPVR. I'd probably need to see the logs to tell you if it was happening there.

[sub]

Actually re-reading, because you said recording is causing this, it must be the input side of things. If you can post the logs, I'll check it out.

[Coxeroni]

I am not watching, I am recording. If you tell me which logs and where I can find them, I will happily share them.

[sub]

On the Settings->About page, there is a 'log files' button.

[mvallevand]

NextPVR transcodes everything it doesn't think is m3u8 or ts file. If the files are m3u8 but don't have the extension I find it helps somtimes to fake one by adding

&.m3u8

to the source url, assuming the server supports that (and most do)

Martin

[Coxeroni]

On the Settings->About page, there is a 'log files' button.

Thanks, attached them.

[Coxeroni]

NextPVR transcodes everything it doesn't think is m3u8 or ts file.  If the files are m3u8 but don't have the extension I find it helps somtimes to fake one  by adding

&.m3u8

to the source url, assuming the server supports that (and most do)

Martin

The actual streams in the m3u8 look like this:
http://192.168.178.40:8001/1:0:19:2B5C:4...014A:0:0:0
Might this be the issue? Dunno how I can manipulate them.
Edit: added &.m3u8 just as you said, the link still works. So this might be a quick fix. Will try it out as soon as I can (can't do it now).

[sub]

Do you know what mime type your enigma2 set-top box uses for it's streams? Basically it looks like it's returning a type that NextPVR doesn't normally equate with being a transport stream, so it falls back to using ffmpeg

[sub]

Edit: added &.m3u8 just as you said, the link still works. So this might be a quick fix. Will try it out as soon as I can (can't do it now).

Actually, if you can stick ".ts" on the end, it'd be better. With this, it wont need to look at the mime type.