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

JWPlayer cached on Chrome. Looping video pulls a video URL from a database. On most browsers it works as expected. The first video plays, on completion, the server is queried and the next video autoplays. This should go on forever. On Chrome and Firefox it loops the same first video over and over. I've tried cache busting server side. Any suggestions on how to correct this?

A secondary issue is that when we use "autostart: true", the logo (watermark) does not display.

<!DOCTYPE html>
<meta charset='UTF-8'>
<script type='text/javascript' src='jwplayer.js'></script>
<script type='text/javascript'>jwplayer.key='XXXXXXXXXXXXXXX';</script>
<div id='myElement'>Loading the player...</div>
<script type='text/javascript'>
var cachebuster = Math.round(new Date().getTime() / 1000);
logo: {
file: ''
file: '',
type: "mp4",
image: '',
margin: 8,
width: 640,
height: 360,
position: "top-left",
repeat: true,

4 Community Answers


0 rated :

In IE11, I get a different video every time, but when I seek forward, I'm getting the dreaded "Error loading media / File could not be played" error message.

I'd start by doing a little code cleanup. The "margin" and "position" attributes apply to the logo, so they need to be <em>within</em> the logo block. Also remove the trailing comma from the last attribute (repeat) - that can upset IE, in particular.


0 rated :

Hmm.... The new forum software doesn't seem to support HTML tags. Ethan, can you give us a hint about what tags ARE supported? HTML tags? bbcode?

Ethan Feldman

JW Player Support Agent  
0 rated : is just one file it seems. This is not an actual playlist.

For posting code in the new forum, use Gist –


0 rated :

It's not an actual playlist. A playlist would be finite at some point. We want the video to be selected from the database and played one after the other forever if need be. It does this in IE8 and safari, but in Chrome and Firefox it plays the same video over and over.

I assume this is some sort of javascript caching on Chrome's part. I've tried all of the cache busting techniques that I can think of....

Anyone with any idea?

This question has received the maximum number of answers.