Network stream of m3u file cuts off after 3 minutes and skips to next song

[DarkStarHarry]

Good day:

I opened a stream using the "open location from clipboard".
The location is an M3U file of 22-30 mp3 files.

What will happen is after 3 minutes (or so) of a song, the player will skip to the beginning of the next song in the m3u playlist.

Is there a way to correct this so that the player will play the entire song before going to the next entry in the playlist?
thanks,
DarkStarHarry

[DarkStarHarry]

Note: using VLC 2.1.5 ricewind on a Windows 10 computer.

[Lotesdelere]

You should try with a newer version of VLC.

[DarkStarHarry]

using version 2.2.4 weatherwax.
Same issue.

Please advise.
thanks,
DarkStarHarry

[kodela]

You opened a stream. The location is an M3U file. Is this M3U file on your computer?
Can you provide an example of such a stream?

[DarkStarHarry]

The M3U file is on my desktop.
I can provide the text of the file if you'd like (as to avoid having to Dropbox it, or similar file transfer)

[kodela]

You have written:

The location is an M3U file of 22-30 mp3 files.

Where are the 22-30 mp3 files?

[DarkStarHarry]

here's the address to the M3U file...

https://archive.org/download/gd79-01-10 ... nf_vbr.m3u

[kodela]

You wrote: "The M3U file is on my desktop."
"https://archive.org/download/gd79-01-10 ... nf_vbr.m3u" is a network address!

I have tested this MRL. There were 23 MP3 files with a total playing time of 2 hours, 56 minutes and 58 seconds.

All pieces were played without interruption until the end.

Reset all settings for preferences and cache as described here:
https://wiki.videolan.org/Reset_Setting ... s_from_VLC

[DarkStarHarry]

No luck.. still happening.
Is there a buffer setting (or something else) I can change that might fix this?

[Rémi Denis-Courmont]

This typically occurs when the server terminated the HTTP connection before the end of the file. There is (probably) a setting to fix this - but that would on the server side.

You can try VLC 3.0 nightlies which attempt to work around the problem by reconnecting.

[kodela]

This typically occurs when the server terminated the HTTP connection before the end of the file. There is (probably) a setting to fix this - but that would on the server side.

Yes, that's for sure.
It is peculiar, however, that there was not a single interruption in my case.