This project is read-only.

Impacts on hardware decoding

Topics: Windows 8 Xaml
Sep 19, 2013 at 6:09 AM
Edited Sep 19, 2013 at 6:09 AM

I have the understanding that windows 8 is putting hardware to good use to assist with video playback / decoding.

Is there any material one can review to get a good understand of what things one should and shouldn't do with customising Player Framework that would disrupt hardware decoding?

Sep 20, 2013 at 7:10 PM
This will all be handled automatically by the player framework as long as you:
  1. Don't add any visible UIElements on top of the MediaPlayer control. Even a 1 pixel element with opacity = 0 will mess up the hardware rendering.
  2. Make sure the MediaPlayer control consumes the entire window. This means no margins or borders.
  3. Make sure AutoHide = true (note: it is true by default).
After you've followed the steps above, hardware decoding and rendering of video will be automatic. It will switch out of hardware mode when the user is interacting with the control but autohide will cause it to go back into hardware accelerated mode when the user is done interacting and auto hide kicks in.
Sep 20, 2013 at 10:57 PM
Great info, tks Tim :)

I'll be adding some controls (not traditional player controls) so it would seem I'm going to want to integrate them into the autohide mechanism.