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

Same video plays in Firefox (pc) when trying to play different media ids

We run a video streaming site with about 50 different videos on it.

I'm not able to reproduce this, but my client is saying that when he launches a video, the correct poster frame loads, but clicking to play the video results in the wrong video playing. It always seems to play the same video no matter which one he tries to load. This ONLY happens for him on Firefox on Windows.

Note on our setup...
We're currently using the JW platform and using their m3u8 playlists. Videos are launched in modal windows from the same page so we're using the JavaScript API to initialize everything.

This setup has worked very reliably in the past, and I'm not even sure where to begin troubleshooting this. If we're initializing the player with a mediaid and it loads the correct poster image, it's super bizarre that the wrong video would subsequently play.

Each playlist file that loads is a unique file so some sort of caching issue doesn't seem immediately relevant. Just curious if anyone else has experienced anything like this.

Thanks for any help!

2 Community Answers


JW Player Support Agent  
0 rated :

Hi, Ryan.

We have already been contacted by Doug from Physique57 regarding this issue and have replied to him, essentially saying that we weren’t able to reproduce the issue in Firefox on Mac or Windows 7 and to try clearing the browser cache if the issue is still occurring.

Thank you.

doug McQuery

0 rated :

Thanks Alex!

For anyone else, we were eventually able to fix this. It turned out to be our own bug initializing the player. When initializing a video, we were passing an m3u8 manifest and an mp4 path. I thought the mp4 was only used on mobile, but it turns out it's used when flash is disabled on desktop as well. I was initially confused because I was debugging the manifest file which appeared to be correct/unique for each video, but the problem was really with the mp4 file. We had a bug in our backend where the mp4 path was always returning the same stream.

This question has received the maximum number of answers.