Invalid source url: malformed M3U provided

I am getting the following error when I try to add the M3U file from my Sat>IP box

" invalid source url: malformed M3U provided"

I am not editing the M3U it is the one provided from my SAT>IP tuner which is a GSS.box DSI 400.

I have provided some same lines from the M3U below

#EXTM3U
#EXTINF:-1,BBC One HD
http://192.168.0.3/?freq=10847&src=aa&pol=v&msys=dvbs2&fec=auto&rolloff=auto&pilots=auto&sr=23000&mtype=auto&sid=6961&pmt=257&pids=0,5400,5402,257
#EXTINF:-1,BBC Two HD
http://192.168.0.3/?freq=10847&src=aa&pol=v&msys=dvbs2&fec=auto&rolloff=auto&pilots=auto&sr=23000&mtype=auto&sid=6940&pmt=258&pids=0,5500,5502,258

Read through the documentation on Custom Channels. Your m3u is missing quite a few tags.

What url did you put into custom channels?

The url provided by my Sat>IP box
http://192.168.0.3:8080/maintvlist.m3u
This opens in my browser so is a valid link

Maybe you have a space before or at the end when you entered it?

Please submit diagnostics from the DVR

1 Like

2023/02/16 19:19:31.748608 [ERR] Failed to parse m3u for Test: malformed M3U provided

Please go to Support -> Troubleshooting -> Submit Diagnostic Logs from the web interface of the DVR and let us know when it's been submitted so we can have a better idea of what was going on.

No matter what tags I add, Channels doesn't seem to be able read the M3U link generated by my Sat>IP box (GSS.Box DSI 400).

The Url provided is in the following format
http://192.168.0.3/?freq=10936&src=aa&pol=v&msys=dvbs&fec=auto&sr=22000&mtype=auto&sid=8340&pmt=268&pids=0,2359,2361,268
This link opens superfast in VLC so I know it works with other apps.

Update
The URL works with rtsp but seems slow to load compared to on VLC
rtsp://192.168.0.3/?freq=10936&src=aa&pol=v&msys=dvbs&fec=auto&sr=22000&mtype=auto&sid=8340&pmt=268&pids=0,2359,2361,268

Further Update
rtsp links work in the android app on my phone but not on my Nvidia Shield. The channel loads but freezes on the first frame

Anyone ever see the following errors in their log file?

2023/02/18 21:34:00.251066 [HLS] ffmpeg: rtsp-SATIP-38: av_interleaved_write_frame(): Invalid argument
2023/02/18 21:34:00.256024 [HLS] ffmpeg: rtsp-SATIP-38: Error writing trailer of pipe:: Invalid argument

Change rtsp to satip

I changed to satip in the m3u as suggested and the channels load in my browser. It takes about 12 seconds for a channel to load but they do load and play ok.

However when I try to watch on my Nvidia Shield the channel freezes on the first frame for a minute or two before starting to play with no sound.
My log file shows the following entries

2023/02/20 20:54:30.178125 [TNR] Opened connection to M3U-SATIP for ch10906 BBC One NI HD
2023/02/20 20:54:48.468363 [SNR] Buffer statistics for 192.168.0.59 (Kitchen TV) for ch10906 BBC One NI HD: buf=0% drop=0%
2023/02/20 20:54:48.468908 [ERR] Error during stream M3U-SATIP ch10906 BBC One NI HD: read |0: file already closed
2023/02/20 20:54:48.468908 [TNR] Closed connection to M3U-SATIP for ch10906 BBC One NI HD
2023/02/20 20:54:48.472651 [HLS] ffmpeg: rtsp-SATIP-0: av_interleaved_write_frame(): Invalid argument
2023/02/20 20:54:48.472651 [HLS] ffmpeg: rtsp-SATIP-0: Error writing trailer of pipe:: Invalid argument

Please change back to http and submit diagnostics after any errors

Logs have been submitted as 7bc50fce-2921-4679-b4bb-784d52644515

Channels dont play at all after switching back to http:

Log file entries below

2023/02/21 16:24:15.378256 [TNR] Opened connection to M3U-SATIP for ch10930 Channel 5 HD
2023/02/21 16:24:15.383751 [TNR] Closed connection to M3U-SATIP for ch10930 Channel 5 HD
2023/02/21 16:24:15.391341 [HLS] Starting live stream for channel 10930 from 192.168.0.60
2023/02/21 16:24:15.430188 [HLS] ffmpeg: ch10930-dANY-ip192.168.0.60-remux: Output file #0 does not contain any stream
2023/02/21 16:24:15.482883 [HLS] Couldn't generate stream playlist for ch10930-dANY-ip192.168.0.60: Stream stopped
2023/02/21 16:24:15.482883 [HLS] Stopping transcoder session ch10930-dANY-ip192.168.0.60
2023/02/21 16:24:15.484457 [ERR] Probe failed for live stream after 92.5914ms and 0 bytes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.