Generate WebM videos for each movie request
Bug #692574 reported by
Keith Hughitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Helioviewer.org |
Fix Released
|
Medium
|
Keith Hughitt |
Bug Description
Currently Helioviewer.org offers H.264 video in several different container formats (mp4, mov, and flv). While this covers of the main operating systems and also enables in browser support (using either mp4 or flv), a better solution would be to offer formats that are optimised for each browser:
Firefox - ogv
Chrome - webm
Safari - mp4/mov
IE - mp4
First, however, performance should be measured to ensure that encoding time is reasonable. A good solution might be to initially generate only the format needed immediately (based on the user's browser). Other formats can then be added to a lower priority queue and can be handled when no other movie requests are being processed.
Changed in helioviewer.org: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Update:
As of 2011/01/03, the time it takes to generate a WebM movie of comparable quality to currently generated ones takes about 10-20x longer.
For example, for a specific test (~1080p, 100 frame AIA 171 image) the recording times were:
H.264 ultrafast 1.6s
WebM qmax 1 26.4s
Until the encoding time for WebM goes down it looks like the above queuing method will be the best way to handle movie requests
while supporting both H.264 and WebM.
As for Ogg support, since the quality is not as good and the encoding times are also slow, it is probably best just to use Flash/H.264 for Firefox 3.5 and lower. As of version 4 Firefox uses WebM/VP8 instead of ogv.