firefox - video.js Chrome and FF Quality problems -


i can't work out why video playing @ different qualities on different browsers. in chrome , ff quality terrible in safari , ie looks fine. know of reason/solution?

video: www.mediaeclipse.co.uk

html code:

<link href="http://vjs.zencdn.net/c/video-js.css" rel="stylesheet"> <script src="http://vjs.zencdn.net/c/video.js"></script> <video id="my_video_1" class="video-js vjs-default-skin" controls preload="auto" width="1000" height="536" poster="http://www.mediaeclipse.co.uk/media/previewimage1.png"  data-setup="{}"> <source type="video/ogg" src="http://www.mediaeclipse.co.uk/media/showreel.ogg"> <source type="video/mp4" src="http://www.mediaeclipse.co.uk/media/showreelsmall.mp4"> </video>

you have 2 videos of incredibly different quality. mp4 rendition looks fine, safari , ie playing, since chrome , ff can play ogg natively you're seeing horrendous ogg encoding.

you can either remove ogg rendition altogether , let video.js fallback flash player, or transcode mp4 ogg using handbrake or zencoder. suggest latter, either should trick.


Comments

Post a Comment

Popular posts from this blog

Java sticky instances of class com.mysql.jdbc.Field aggregating -

i noticed (via jmap+jhat) app leaking storing many instances com.mysql.jdbc.field  class - double checked code make sure closing preparedstatements, find few missing didn't change outcome. - preparedstatement created , closed right away - several others created @ start , reused many times - using org.apache.tomcat.jdbc.pool.datasource connection pool what can cause type of behavior? are closing of preparedstatements / result sets using: preparedstatement stmt (possible assignment here); try { // work prepared statement resultset rs; try { while (rs.next()) ... // process results } { rs.close(); } } { stmt.close(); } so guarantee result sets closed when finished (regardless of exceptions) , statements closed (regardless of exceptions)? there other ways write that, idea same. if you're doing of properly, unless have many references it's taking inordinate amount of memory, it's ok , nothing needs done it.
Read more