Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

Big problem with HSL/Cloudfront streaming and live position

Hi,

we have a big problem with our new JWPlayer Premium and HLS/Cloudfront streaming:

As long as the stream is online the player starts at the live position as it should be. But if we interrupt the stream (f.e. during a speakers pause) and restart it the JWPlayer starts not at the new live posotion, but at the START postion of the previous stream. DVR isn't enabled in our Wowza server so this shouldn't be an issue.

We followed exactly the Cloudfront/Wowoza/JWPlayer tutorial - but that case isn't covered in the tutorial. How do we solve that?

Thanks for your help!

4 Community Answers

Ethan Feldman

Best Answer  JW Player Support Agent  

Ah, glad you got it. Thanks for letting me know :)

View in conversation
Up Down

info

User  
0 rated :

Another strange thing:

If I start a new stream it happens that suddenly during the new stream the player switches to the old stream and plays that instead.

I think it must have something to do with the cloudfront edge servers that cache the stream segments wrong. But I can't figure out what it is.

Up Down

Ethan Feldman

JW Player Support Agent  
0 rated :

Can I see a link to where this is running?

Up Down

info

User  
0 rated :

I found the answer to that problem:

The problem is that Wowza server creates similar filenames for the chunks by default if you restart the stream. The cloud distribution caches the old files AND the new files so there are some file conflicts (same name) and the player doesn't know whick chunk to play, so the streams mix up.

You can simply avoid this behaviour if you add this code to the application.conf file of Wowza Streaming Engine:

> In Application.xml, add the property to the
> <LiveStreamPacketizer>/<Properties> container:
>
> <Property>
> <Name>httpRandomizeMediaName</Name>
> <Value>true</Value>
> <Type>Boolean</Type>
> </Property>

With that property Wowza gives random and different filenames to each incoming stream and so the problem is solved.

Thanks to the awesome Wowza support I solved this issue and now it works like a charm. Thanks Ethan anyway.

Cheers

Up Down

Ethan Feldman

Best Answer  JW Player Support Agent  
0 rated :

Ah, glad you got it. Thanks for letting me know :)

This question has received the maximum number of answers.