You may have noticed that a few days ago we switched to a new Stream player using HTML5, allowing phones and tablets to finally play videos directly on the site. For most people it seems like the switch was totally painless, but a few seem to have issues so I've just added the ability to switch back to the old Flash based player, at least while it's still supported by our partner Minoto. Please let us know in the comments if the HTML5 player works fine for you, or if you are switching back!
Update: Firefox users will be happy to know that the latest version (23) of the browser now supports hardware acceleration (DXVA) of of H.264 HTML5 videos. The results on my PC at least with our 60 fps videos are quite spectacular :)
All comments (58)
I'll update my GPU drivers to see if this fixes the problem.
Still we are thinking about it.
Good stuff!
windows 8, firefox 22.0
Here are some suggestions for some changes to the encoding system then (regarding the streaming videos):
Please always use the latest x264 revision. At the moment you are not using the latest revision.
Please use x264 presets. Please use at least "Preset Slow". At the moment you are not using presets.
For the streaming videos and their associated bandwidth constraints it also might be better not to use x264 tunes (i.e. use the default tune).
Also, please use VBV with x264. At the moment you are not using VBV at all, although VBV is very important for streaming purposes.
You can read about VBV and streaming over there (especially see "Example 3"):
http://mewiki.project357.com/wiki/X264_Encoding_Su...
Also, please use CRF (Constant Rate Factor) encoding. At the moment you are using ABR (Average Bit Rate), which is suboptimal. CRF combined with VBV is better and can save bandwith. For streaming purposes, CRF values somewhere between 21 and 16 should probably be reasonable. But try for yourself and see at what CRF value the quality becomes good enough for you.
Furthermore, please use the MP4 "Fast Start" feature when muxing to MP4 container (known as "Web Optimized" option in HandBrake GUI / --optimize option in HandBrake CLI for example).
And, as already mentioned earlier, please increase the video resolution. 960x540 is too low. Please use at least 1280x720p or even 1920x1080p.
PS: Not sure what AAC encoder you are currently using for the streaming videos, as this is unapparent from the corresponding MediaInfo output. But please make sure to use a good AAC-LC encoder, which is important at a bitrate of just 96 Kbps (which is what you are currently using).
PPS: Some time earlier you said that your streaming videos are automatically generated / (re-)encoded by your server, correct? And the source videos the server gets fed with are the full-bitrate H.264+AAC MP4 videos you are currently encoding with MeGUI, correct?
If yes, then you should be able to let your server auto-encode / auto-generate the streaming videos via HandBrake.
HandBrake currently does not support AviSynth as input. But in that case it doesn't need to because you would be feeding it with the full-bitrate MP4 videos you created via MeGUI in the first place ;).
And HandBrake is not just a x264 GUI, but a whole library which should have all the capabilites you need for that task (including things like altering the resolution of videos (if needed) and so on).
And HandBrake is also available as a CLI version.
GUI:
http://handbrake.fr/downloads.php
CLI:
http://handbrake.fr/downloads2.php
Nightly builds:
http://handbrake.fr/nightly.php
CLI Guide:
https://trac.handbrake.fr/wiki/CLIGuide
Oh, and for the sake of device compatibility (decoding performance), please don't forget to restrict the H.264 Level appropriately.