Updates:
Summary: Very large and very small playback rates on audio crash the tab
Comment #7 on issue 18362 by [email protected]: Very large and very small
playback rates on audio crash the tab
http://code.google.com/p/chromium/issues/detail?id=18362
Ok, after more research, HTMLMediaElement does cache the rate, but only for
a limited
time and does ask its player for how fast it's actually playing. So!
Ignoring
requests to change to ridiculous values should not be a problem if we put
the logic
in WebMediaPlayerImpl.
The question becomes, what should our thresholds be, and how should we
treat them?
- Vista64 crashes due to audio issues if we try to play at <0.1x or >10x.
Muting
would be an option, but our volume logic only sets the volume to the output
stream.
If the volume is set to 0, it still does all its calculations and will
fail. So if we
want to mute, we need to change that logic.
- Vista also has a video rendering issue for speeds greater than about 4x.
The first
paragraph of
http://blogs.msdn.com/directx/archive/2009/05/12/2d-drawing-apis-in-
windows.aspx may explain that. No direct access to hardware for 2d
rendering?
So, it may be best to
1. Modify muting so audio renderers know not to do anything if the volume
is 0, then
mute if below 0.1x or above 10x.
2. Figure out what to do about vista's video rendering? It feels like this
is again 2 separate issues. Splitting.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
