RTP streams / Kodi gets incorrect docker IP

[DiligentScrubber]

Hello everyone, 

I was playing around with IPTV, trying out NextPVR and stumbled upon two issues. 

First basic information or scenario:

• NextPVR -> docker(-compose): stable -> Version: 7.0.1.241229 (please provide proper version tags )
  

• Country: Germany/DE
  
• ISP/Provider: Telekom (MagentaTV)
  
• Client: Kodi
  

Issue 1 - RTP streams

I'm in Germany and I'm receiving 'MagentaTV' via my ISP. Here's a collection of the multicast addresses I can use to tune in to the channel streams: https://db.iptv.blog/multicastadressliste

Code:

#EXTM3U
#EXTINF:-1 tvg-id="id1", Das Erste
rtp://87.141.215.251@232.0.20.35:10000
...

As you can see the `.m3u` file contains `rtp://` URLs. While I can watch them just fine with VLC and also with Kodi's `IPTV Simple Client`, when I try to import this .m3u in NextPVR it doesn't find any channels.
Now I found an older post on this forum by @sub mentioning rtp (or atleast rtps) is not supported. What's the status now?

The same site also provides a ffmpeg list which contains `udp://` URLs.

Code:

#EXTM3U
#EXTINF:-1,Das Erste
udp://@232.0.20.35:10000?sources=87.141.215.251
...

Importing that .m3u will result in the correct channels being found but I can't watch them. At least not in the webinterface. The log indicates that the transcoder fails.
It will attempt several times before exiting. I can provide logs if needed but I'm not sure if it's actually helpful. VLC can't play those ffmpeg version links.

So I tried to play these in Kodi which brings me to..

Issue 2 - docker IP in Kodi client settings

When I configure the Kodi NextPVR client add-on I enter the IP of the host running the docker container as `NextPVR hostname` which ofc is a local IP (192.168.178.10).
However when I try to enable the add-on it seems to communicate with the NextPVR server and sets a different IP (172.18.0.2) on its own. That is the docker virtual gateway IP which is the gateway between host and container.
Resulting in the add-on failling to be enabled.

This is my docker-compose file

Code:

services:
  nextpvr:
    image: nextpvr/nextpvr_amd64:stable
    container_name: nextpvr
    environment:
      - PUID=1000
      - PGID=100
      - TZ=Europe/Berlin
    ports:
      - 8866:8866
      - 16891:16891/udp
    volumes:
      - /opt/nextpvr/docker_appdata:/config
      - /mnt/nextpvr_recordings:/recordings
      - /mnt/nextpvr_buffer:/buffer
    restart: 'unless-stopped'

---

Lastly just to make sure I'm working on the correct assumptions here..

With NextPVR I can receive IPTV streams from my provider (or other devices which is not applicable in my scenario).
Clients can either receive a transcoded version of the streams or play them natively (are the streams redirected or do the clients just play them directly?).
Clients can also schedule recordings which will be performed by the server.
Recordings can be played by all clients.
Clients can use timeshift and play from the server's buffer.

Is this an accurate understanding of what NextPVR offers?


Thanks for taking your time reading this. Looking forward to any replies.

[mvallevand]

Right now rtp is only via an extra but I thought udp was supported.

For Docker sounds like you didn't set up the HOST environment variable explained in the install instructions. That is easier than a manual override.

Martin

[DiligentScrubber]

Thanks Martin!

I dismissed the part about setting the host ip env since it was mentioning some legacy HomerunHD setup (I was looking at the wiki on github).

What is this extra you're referring to? Idk about the udp streams. Never used them before. They don't work in VLC. Haven't tried with IPTV Simple client in Kodi yet.

[mvallevand]

Yes the Docker install needs a bit of updating to deal with Discovery too.

Here is an Extra example for rtsp https://forums.nextpvr.com/showthread.ph...#pid596647 You need to come up with the command line, it doesn' have to be in Docker and then place the extra xml file in /config

Martin

[mvallevand]

Regarding the udp:// URL's since you are running Docker I expect you would need to use host mode to get a real IP

Martin

[DiligentScrubber]

Hmm, so I played around with this for quite some time. Apparently with my multicast address one should use ffmpeg like this

Code:

ffmpeg.exe -v panic -i "rtp://@232.0.20.35:10000?sources=87.141.215.251" -codec copy -f mpegts out.ts

I confirmed that this works outside of NextPVR.
Note the absence of `-re`. That completely wrecked the file with tons of corrupted frames, fps stalling down to single digits.

So this is my test extras file:

Code:

<extras>
  <channel name="Das Erste">
    <command>ffmpeg</command>
    <args>-v panic -i "rtp://@232.0.20.35:10000?sources=87.141.215.251" -codec copy -f mpegts -</args>
  </channel>
  <channel name="ZDF">
    <command>ffmpeg</command>
    <args>-v panic -i "rtp://@232.0.20.234:10000?sources=87.141.215.251" -codec copy -f mpegts -</args>
  </channel>
  <channel name="RTL">
    <command>ffmpeg</command>
    <args>-v panic -i "rtp://@232.0.10.135:10000?sources=87.141.215.251" -codec copy -f mpegts -</args>
  </channel>
</extras>

The device generates, the channels populate but trying to play the channel nothing happens.

The main logs seems fine to me. The live one shows nothing after ffmpeg initialized.

This is the `/buffer`-volume

Code:

total 8.0K
drwxr-xr-x 2 root root 4.0K Mar 20 01:03  .
drwxr-xr-x 7 root root 4.0K Mar 19 17:55  ..
-rw-r--r-- 1 root root    0 Mar 20 01:03 'live-Das Erste-1-1.ts'
-rw-r--r-- 1 root root    0 Mar 20 00:42  live-ZDF-0.ts
-rw-r--r-- 1 root root    0 Mar 20 00:43  live-ZDF-1-4.ts

While the default ffmpeg process stops after closing the player, the 'extras'-one (my command) seems to hang and does not exit unless I kill it or restart the container. This seems to also prevent the device list from loading in the frontend.

edit: there are some other ffmpeg flags in the attached files I was messing around with to no avail.

[DiligentScrubber]

Regarding the udp:// URL's since you are running Docker I expect you would need to use host mode to get a real IP

Martin

I think I already tried that but I can try again later.

On some German forums I found, people are saying the source simply doesn't support it.

[mvallevand]

Did you try host mode for that Extra, it is the same issue as UDP.

Also are you testing the command line from a bash shell within Docker?

Martin

[DiligentScrubber]

That was it! I guess a networking issue then.

Switched docker container to host networking mode and everything works as expected. Thank you!

Now I just need to figure out how to add EPG info and channel icons to the extra channels. There's a tool called easyepg (or new-easyepg). I think I should be using that.