search

DDVTECH / mistserver

The official mistserver source repository - www.mistserver.com
The Unlicense
383 stars 133 forks source link

HLS (.m3u8) working fine in 3.2.2, but not in 3.3 #184

Open jorbig opened 11 months ago

jorbig commented 11 months ago

Just a heads up that the new 'stable' 3.3 release broke my HLS stream. The index.m3u8 somehow loads too slow to be played... Reverting to 3.2.2 'fixed' it for me. I don't have time to troubleshoot, but maybe this already helps.

Rokamun commented 11 months ago

Hey there,

Thanks for the report, I'll run some checks on it when I can.

What kind of input was the stream? I assume you meant the HLS output being slow.

With kind regards,

Balder Viëtor Head of Testing

MistServer

On Fri, Dec 22, 2023 at 3:44 PM jorbig @.***> wrote:

Just a heads up that the new 'stable' 3.2 release broke my HLS stream. The index.m3u8 somehow loads too slow to be played... Reverting to 3.2.2 'fixed' it for me. I don't have time to troubleshoot, but maybe this already helps.

— Reply to this email directly, view it on GitHub https://github.com/DDVTECH/mistserver/issues/184, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN2RJDFKZGNUQ7F75UZI5DYKWMDTAVCNFSM6AAAAABA75KQAWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2TIMBSGIZTGMY . You are receiving this because you are subscribed to this thread.Message ID: @.***>

jorbig commented 11 months ago

Yes, the output file: hls/livestream/index.m3u8 downloads eventually, but after something like 10 seconds. Which makes it unplayable. The input is an AAC audio only stream of 32 kbps,

jorbig commented 3 months ago

Same issue after updating to 3.4. Rolled back to 3.2.2 once again.

irg1008 commented 1 month ago

For me I am not being able to stream WHIP from OBS, it gets hung up on "receiving data"

Rokamun commented 1 month ago

I'll double-check the audio only streams. We did change quite a bit to the HLS code in this version. So chances are we fixed and then broke it. Sorry about that!

For WHIP I would recommend setting the WebRTC protocol to bind to 0.0.0.0 to force it to IPv4. Chances are it's trying to bind an IPv6 port and I'm actually not sure if we accept WHIP over IPv6 in the current builds. A tutorial on that subject is described here as well.