Forum Replies Created
-
-
12 years ago in reply to: Issues with Chrome 27
Hi Martin
Thanks for your reply. I mentioned in my initial post what versions of everything I was using. Chrome v. 27.0.1453.94 m.
However, I didn’t mention my op. system, which is Windows 7 on a Toshiba 64-bit laptop. The hosting provider of the website uses Redhat Entreprise Linux el5.
Unfortunately when I clicked the links to your server, neither of them ran in Chrome. i got the same Video not properly encoded message on BOTH the original and the Fixed Meta Data versions. (But as before, it did run in the latest versions of FF and IE – see my first post for details.)
I know Chrome is a real swine for throwing odd “features”, like not displaying form data sometimes, or crashing online forms so that you post rubbish to your db over and over again. Good luck with the continued searches!
12 years ago in reply to: Issues with Chrome 27Hello again
Here is the very long dump from Chrome after installing 2.1.12!
Analysis of http://www.servethecitygeneva.ch/videos/STCG_ph.mp4 (local):
Bad mime type: Video served with a bad mime type text/html; charset=iso-8859-1! Some web browsers may experience playback issues in HTML5 mode (Internet Explorer 9 – 10). Currently you are using the “Default (mixed)” Preferred Flowplayer engine setting, so IE will always use Flash and will play fine. (show fix)
Error: Can’t check the video (HTTP 406)!
Error: Meta Data (moov) not found at the start of the file (found at 17,223,610 byte)! Please move the meta data to the start of video, otherwise it might have a slow start up time.
Format: mp4
Seek points: 4422 (stts sample count)
Audio: 1 stream, mp4 (ISO/IEC 14496-3 AAC) 48000Hz, 2 channels, 16bit, stereo
Video: avc1 (H.264 Encoder) codec, mp42 (MS-MPEG4 v2 Decoder) file type(show more info)
(Note: read about remote file analysis in FAQ)
12 years ago in reply to: Issues with Chrome 27Thank you! In the meantime, I tried adding:
AddType video/ogg .ogv
AddType video/mp4 .mp4
AddType video/webm .webmto my .htaccess, and this solved the problem for IE 10. In Chrome, the error message changed to:
html5: Video not properly encoded
Haven’t tried the new version yet.