jwplayer Filename bug?

Our streaming works perfectly, but recently we noticed that our mobile viewers were not working properly.
Our site is still under development, so I’m not certain if it was an s2Member update that caused the problem. Our older test site seems to work okay in Mobile, so I believe it must have been some sort of update.

Our RTMP files were working perfectly in our browsers (flash), but when we forced it to MP4 mode to check on why our mobile was not working we found some weirdness.

Our test file worked perfectly:

$s2_jw_config["mp4_video_file_name"] ="/demo/video_no_space.mp4";
...
 sources:
                               [
                                   {type: "mp4", file: ""}
                               ]

As soon as we introduced spaces, the streaming worked fine, but the MP4 got borked.

ie:

$s2_jw_config["mp4_video_file_name"] ="video with spaces.mp4";
...
 sources:
                               [
                                   {type: "mp4", file: ""}
                               ]

We get the dreaded “Error loading media: File could not be played”.

After a bit of digging, and our hatred of spaces in file names, I tried urlencoding it.

$s2_jw_config["mp4_video_file_name"] = urlencode("1 pushup knees on ball.mp4");
 ...
  sources:
                                [
                                    {type: "mp4", file: ""}
                                ]

BINGO! Now I’m not sure if this should be in s2Member or on the end user? Would be kinda nice to have it auto urlencode.

Hi Seth – I am no expert on this area but when reading your post I wondered if you are using JWPlayer 6? If so, that player has an automatic delivery to mobile devices. JWPlayer 5 had no such capacity and from what you have written it sounds like you had some other way to translate the files to be seen via mobile. What I am wondering is if you have switched to JWPlayer 6 could it be that the player is trying to convert for mobile and your previous method is also trying to do the same thus creating a problem?

Echomango,

We are indeed using jwPlayer6. Its just weird though the mobile doesn’t work without specifying that MP4 code for some reason. I’m not sure why it works with the streaming portion though.

Regards

Thank-you for reporting this important issue.

I’m sending these details to Jason to look at.

Thanks for the heads up on this thread :-)

Investigating this. Thanks for your patience.

I believe the underlying issue here is with a difference in the CloudFront API, with respect to streaming vs. download distros. The resource identifiers and endpoint URLs should be encoded differently, depending on whether we’re talking with a streaming distribution or a downloads distribution. We’ve found a way to correct this behavior and standardize things within s2Member®.

I’m attaching a PATCH file if you’d like to experiment. Please unzip and upload the attached file, allowing it to override your existing copy of /s2member/includes/classes/files-in.inc.php

Please specify the file name without encoding, like this:

$s2_jw_config["mp4_video_file_name"] ="video with spaces.mp4";

s2Member® will take care of the internal specifics for you.

PATCH: http://d1v41qemfjie0l.cloudfront.net/s2member/uploads/files-in.inc_.php_.zip