In this episode of Defrag Tools, Chad Beeder and Jorge Novillo wrap up a series on Media eXperience Analyzer (MXA). We examine one more audio glitch scenario, and show how to use MXA to determine what caused the problem.

Media eXperience Analyzer (formerly WindowsXRay) is a tool used to visualize ETW traces, with a particular emphasis on media scenarios such as audio/video capture and playback.

For an introduction to MXA, and explanation of how to capture a trace, refer to Defrag Tools Episode #149.

Timeline:
[00:00] Introductions and overview
[01:20] Loading the trace into MXA
[01:50] Step 1: Start with the Audio Glitches dataset to see where we need to look in the trace
[02:52] Step 2: Look at the CPU Scheduler dataset to see what was going on at that time
[04:04] Filter on the audiodg.exe process to see the activity of the audio engine – notice a gap in the audio pump activity
[05:57] Look at the Call Stack when the thread started again after the delay. What was it waiting on? (Hard page fault)
[07:27] Ready Thread viewer tells you what was running when our thread was ready to run, but couldn’t.
[08:28] Hard Page Faults dataset lets us see what file we were paging in during this time: the DLL for the Audio Processing Object was paged out.
[12:47] Email us at [email protected]





Source link