Community Forums

1. 

   Mason
   Member
   Posted 1 year ago

   I've run into a problem with mp3 playback on Safari (Mac) and mobile Safari (iPad/iPhone). With files hosted in MediaCore, Safari will display the media player, but not play any media if it is under the MediaCore directory. On the iDevices, a dialog will say that the "Media cannot be played". I tested the media in Firefox, Opera, Chrome and they work fine. It seems to only be Safari.

   To investigate the issue, I created a test page. The page simply loads media from another server and from my mediacore server via the < audio > tag. The media from the other server loads and plays, while the media on my MediaCore server doesn't load or play. If you go to http://roltemp.awardspace.com/sandbox/html5.html in any flavor of Safari you will see what I am talking about. It doesn't appear to be an HTML5 issue as Chrome loads both media files just fine.

   Being that we are seeing an increase in iDevice traffic, I'd like to know if there is something that we can do to fix this problem. I also was wondering if anyone else is experiencing this behavior as well.

   Thank you for any help in resolving this issue.
2. 

   Nathan Wright
   Maintainer
   Posted 1 year ago

   Hi Mason,

   v0.8.1 adds a foolproof way of serving files: mod_xsendfile. With that installed, Apache takes over and serves the file itself, so it should be no different than the 'non-mediacore hosted' example you give. This offers better performance too, so it's definitely going to be the recommended approach.

   We've also greatly improved the default file serving code (used when mod_xsendfile isn't available) so this issue may have been fixed already; I wasn't able to reproduce this issue with Safari. However, I did run into troubles with seeking ahead in media on Chrome with the Paste server. For 0.8.2 I hope to have all these kinks ironed out. It's mostly a matter of supporting the right headers (Range, etc) and response types I believe. In the mean time there's mod_xsendfile.

   Hope that helps, and please let us know if v0.8.1 fixes the issue. The plan is to release v0.8.1 final on Sunday or Monday.
3. 

   schmiddy
   Member
   Posted 1 year ago

   Mason,

   I'm having the same issue. Are you by any chance deployed using mod_wsgi?

   Here's the forum topic i have this posted in. http://getmediacore.com/community/topic/question-on-mime-types

   I installed 0.8.1 as well as enabled mod_xsendfile in my apache config, but that didn't seem to do the trick.
4. 

   schmiddy
   Member
   Posted 1 year ago

   Doh! I'm an idiot. I didn't realize there's a setting in the deployment.ini file where you need to set it to use apache_modxsendfile.

   Seems to have fixed my issue. Thanks for the tip Nathan
5. 

   Mason
   Member
   Posted 1 year ago

   Is there a git-update script to do a quick update to the installation, or a document with the upgrade process? I don't want to break our installation, but I'd really like to resolve our problems and get mod_xsendfile working for us.
6. 

   schmiddy
   Member
   Posted 1 year ago

   In all honesty, I think the safest way is to set up a separate instance of mediacore with a separate virtualenv and checkout the latest code from the git repository.
   That way you have no inter dependencies between your current production environment and can test your new configuration without worrying about bringing your current site down.

   From my experience it's always best practice to have some type of workflow and have multiple environments configured to ensure you're working out all the issues before sending anything live. (Dev, Stage, Prod at the least) . My dev environment is typically the latest and greatest changes from github. From there i'll push any changes I want to send live to my stage environment to confirm everything is working as expected, and once confirmed I'll finally send it off to prod.

   If you are worried about any modifications, customizations, etc that you've made to your current mediacore setup, you can simply create a fork of the simplestation mediacore repository and push/merge your changes to your fork. From there you can checkout the code and test to make sure everything is working correctly.

   Hope this helps!

RSS feed for this topic

Reply

You must log in to post.