Sun Feb 11, 2018 6:03 pm by atc98092
I'm not following what you mean by a Serviio native XML sob file.
Serviio has to be able to recognize what the actual video is, to determine if it can be played without transcoding. Your URL does not contain the complete path to the video. It has to end with the file name, with the container, such as video_stream.flv (or .mp4 or similar). The only way I've seen an online source work without a specific video path is with a plug-in that decodes the page at the URL and provides links to one or more videos available at that URL.
In Serviio a M3U playlist file has to provide that full path. Perhaps some other software package can take that playlist file and work properly with it, but I don't know if Serviio can. My comment about the proxy was simply to state that your M3U file is only pointing at the proxy, not the actual public URL.
I hope Zip can provide any further information, as I believe I've reached the limit of my knowledge here.
Dan
LG NANO85 4K TV, Samsung JU7100 4K TV, Sony BDP-S3500, Sharp 4K Roku TV, Insignia Roku TV, Roku Ultra, Premiere and Stick, Nvidia Shield, Yamaha RX-V583 AVR.
Primary server: Intel i5-6400, 16 gig ram, Windows 10 Pro, 22 TB hard drive space | Test server Windows 10 Pro, AMD Phenom II X4 965, 8 gig ram
HOWTO: Enable debug logging HOWTO: Identify media file contents