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

Problem loading flash

Hi,

according to your documentation for JWPlayer 7, the default location of the swf file is at the same location as the javascript player.
This seems to be not working, since the js player is at "http://127.0.0.1:3000/assets/plugins/video/jwplayer.js" and I can see in the logs it's trying to load the swf at "GET http://127.0.0.1:3000/jwplayer.flash.swf ".
It works fine if I manually give him the path, however I'm worried about the other javascripts files like provider.*.js, etc.

Any idea what's going on?

Thank you

9 Community Answers

Todd

Best Answer  JW Player Support Agent  

Our Configuration Options Reference at https://support.jwplayer.com/customer/portal/articles/1413113-configuration-options-reference has been updated to include the base: ‘’ parameter, where you can define the base path for skins and providers but does not change the path for the jwplayer.flash.swf, as you can already do this with flashplayer: ’’

The other files you mentioned (provider.cast.js, provider.shaka.js provider.youtube.js, etc) are the providers we load to play different media types. By default, we pull them from the CDN to make sure they’re all current/up to date. You really should not mix and match providers between versions, which is why we opt to use the CDN. If you update your JW Player and forget to update all of the providers on your own server, you are going to see errors.

As for polyfill.base64.js, polyfills are used on certain browsers that are missing base functionality that the player needs to work. The base64 polyfill exists for browsers that do not provide that functionality natively. Primarily, that would be IE9: http://caniuse.com/#feat=atob-btoa

View in conversation
Up Down

Todd

JW Player Support Agent  
0 rated :

That is strange, I just checked a self-hosted copy of 7.3.5 and the .swf loaded from the same path as the jwplayer.js. Can you send me a link to a public-facing URL where I can reproduce this? What version of JW7 are you using?

Up Down

Raphael

User  
0 rated :

Hey Todd,

we are using the 7.3.4.
You can check it over here: http://integration.tsu.co/
You can see that jwplayer.js is located at http://tsu-integration-assets.s3.amazonaws.com/assets/plugins/video/jwplayer-ab4a80e20c673971c29e2677ce23b3ce43fef3fb78c32d2016af8350ecfd9df5.js but it's trying to load the jwplayer.flash.swf at http://integration.tsu.co/jwplayer.flash.swf.
The flash file is accessible at: https://s3.amazonaws.com/tsu-integration-assets/assets/plugins/video/jwplayer.flash.swf.
Maybe the fingerprint in the js filename is causing the issue? Although that doesn't explain why it's trying to load the flash file at the other domain.

Thanks

Up Down

Todd

JW Player Support Agent  
0 rated :

Looks like the problem is that your jwplayer.js was renamed to jwplayer-73ba8b6028ce3983f5b53b5afe2c7e51dda1db9f62c47ba4aae1192d9743e112.js

I was able to verify that jwplayer.flash.swf tries to load from the root level when your jwplayer.js has these extra characters added to the filename, so I will escalate this as a bug.

A much faster fix, however, is to make sure the name of your file stays jwplayer.js

Up Down

Todd

JW Player Support Agent  
0 rated :

Another workaround would be to define the full jwplayer.flash.swf URL in the flashplayer: ’’ setup parameter:

<script> 
jwplayer("videoPlayer").setup({ 
	file: 'bunny.flv',
	primary: 'flash',
	flashplayer: 'http://full_path_to/jwplayer.flash.swf'
});												
</script>

Up Down

Raphael

User  
0 rated :

Hey Todd,

sure but the fingerprinting is actually very useful and a good practice for assets delivering using a CDN.
Yes it works fine with the flashplayer option, but I'm concerned about the other assets that are part of the JWPlayer package like provider.cast.js, provider.shaka.js provider.youtube.js polyfill.base64.js, etc. I guess jwplayer won't be able to access it as well.

What are these assets for? Is there any options like the flash one to specify the path of these assets? What happens if these assets aren't accessible?

Thanks

Up Down

Todd

JW Player Support Agent  
0 rated :

I will work with our product manager to make sure we provide better documentation for these items. Stay tuned and I will provide a new update when the new documentation is in place.

Up Down

Todd

Best Answer  JW Player Support Agent  
0 rated :

Our Configuration Options Reference at https://support.jwplayer.com/customer/portal/articles/1413113-configuration-options-reference has been updated to include the base: ‘’ parameter, where you can define the base path for skins and providers but does not change the path for the jwplayer.flash.swf, as you can already do this with flashplayer: ’’

The other files you mentioned (provider.cast.js, provider.shaka.js provider.youtube.js, etc) are the providers we load to play different media types. By default, we pull them from the CDN to make sure they’re all current/up to date. You really should not mix and match providers between versions, which is why we opt to use the CDN. If you update your JW Player and forget to update all of the providers on your own server, you are going to see errors.

As for polyfill.base64.js, polyfills are used on certain browsers that are missing base functionality that the player needs to work. The base64 polyfill exists for browsers that do not provide that functionality natively. Primarily, that would be IE9: http://caniuse.com/#feat=atob-btoa

Up Down

jlewin Lewin

User  
0 rated :

Thank you

Up Down

Todd

JW Player Support Agent  
0 rated :

You’re welcome. I will mark this support case as closed, but certainly contact us again if you have any other support questions or concerns.

This question has received the maximum number of answers.