JW Player 6 with Drupal 7

As far as I know this version was for JW 5.

The release notes on jw_player 7.x-2.x-dev say "Branch 2.x is for JW Player 6 support" https://drupal.org/node/1977398 - which presumably means branch 1.x does not support JW6.

We are also waiting for the Drupal module for JW Player 6 as JW PLayer 5 is full of bugs, and no longer being bug-fixed.

The release notes on jw_player 7.x-2.x-dev say "Branch 2.x is for JW Player 6 support" https://drupal.org/node/1977398 - which presumably means branch 1.x does not support JW6.

I believe that is correct.
JW Player 6 seems to play ok for me so far with JW Player 7.x-2.x-dev (2013-Apr-23) for example - here but I don't know about the development status of jw_player 7.x-2.x-dev - is anyone using this on production sites?

Hi all

I have purchased licensed version of the JW Player, it's jwplayer 5. I am currently on Drupal 6. I intend to upgrade to Drupal 7 so can I do that if I stay with 1.x branch?

@Rhino-new The alpha release is built for version 5. The 2.x dev code is for JW Player 6.

I use JW Player 7.x-2.x-dev with Video module 7.x-2.10+13-dev. Also, video preset module for convert to MP4, FLV and WebM.
In my video module I set JW Player as Player for the 3 formats mention above.
I use FFMPEG as Transcoder.

In my content-type "Video" I put a field video for use the conversion.
The conversion is OK. Then, I create a view-block that only display all node of my content-type video with formatter "video player" .

When I see my block, JW Player show me a error: "Error loading player: No playable sources found" (attach a image)
And I inspect the jw player container and I have this:

jwplayer('jwplayerjw-player').setup({
   "image":"http://my-domain.com/es/system/files/videos/thumbnails/525/thumbnail-525_0004.png",
   "file":"http://my-domain.com/",
   "width":640,
   "height":360,
   "stretching":"uniform", 
   "autostart":"true"
});

The error is in the Path of my file. No attach the video format (in this case, the 3 formats MP4, FLV and WebM). Only display the domain.

Do I need to do a extra configuration in any module? What's wrong here?

@Dvex, I think maybe you want to start a new support ticket for that.

I'm currently having trouble getting JWP6 to work, I have 7.x-2.x-dev installed and it's failing to recognise the player - it's looking for a "player.swf" file in the library, which apparently is no longer packaged with JWP?

The contents of the jwplayer folder I downloaded from jwplayer.com are:
jwplayer.flash.swf
jwplayer.html5.js
jwplayer.js
README.html

Is the module being brought up to speed with this or do I have to track down a legacy copy of the player?

@ kingandy have you tried renaming your jwplayer.flash.swf to player.swf?

I've just tried the latest version of jwplayer and the latest dev 2x version of the module dated 2013-Sep-30.

Renaming jwplayer.flash.swf to player.swf used to work (back in March last year) but now there's an error stating that if renaming in the latest version to player.swf the player isn't found. This is in the reports log.

http://multimedia.kingfisher.so/jwplayer shows this

@ kingfisher64 what does http://multimedia.kingfisher.so/jwplayer show? It looks like JW Player 6.7.4071 is working correctly.

@Juc1 - it appears we have a browser issue as from your comment I tested other browsers other than firefox - which doesn't work.

Google Chrome version 31.0.1650.63 & Opera version 12.15 works fine

Firefox 26 - just spins round

IE11 & Safari 5.17 - "Error loading player: No playable sources found"

I got JW Player 6 to work as a file formatter (with File entity) using the latest 7.x-.2x-dev branch (which hasn't changed since February 23, 2013). I had to write a few patches to add some features and fix a bug with File entity. But I think the 7.x-.2x-dev should works out of the box when used as a file field formatter.

So I believe the 7.x-.2x-dev branch is the fix to this issue but it needs review. I'm moving this issue to the 7.x-.2x-dev version and marking it to "Needs review". Maintainer, feel free to close this issue as fixed if no further review of the 7.x-.2x-dev is needed. In such case, consider creating a beta release of this version.

I release the 7.x-2.x branch as 7.x-2.0-beta1 with a couple of fixes (see release notes) I've been testing for the past month. Next step is to identify release blocker and create issue for them.