Posts

Showing posts from January, 2013

Identified: Windows Media Player "An audio device was disconnected or reconfigured" during playback

In my case, this is a conflict between BeyondTV and Windows Media Player. WMP is playing a video file.  DivX, WMV, it doesn't seem to matter. BeyondTV begins to "Showsqueeze" a file to DivX format. WMP throws "An audio device was disconnected or reconfigured" error. Once identified, the error is perfectly reproducible.  Simply set BeyondTV to auto-squeeze without any time limits, start recording any show, then stop it anytime.  Manual or automatic recording, doesn't matter.  A few seconds after stopping, Beyond will queue up the Showsqueeze and start the DivX conversion, at which exact moment WMP will stop doing what it is doing and puke the above error. I am guessing that BeyondTV and WMP both "want" the DivX codec at the same time.  But I don't know for sure.  All I know is it seems to be unique to me. The error does NOT happen if Beyond compresses shows to WMV format.  Just DivX seems to set it off.  (Of course, nobody wants a ...

Windows Media Player "An audio device was disconnected or reconfigured" during playback

Credit to "Geoff" for this post - read it for a summary of the error.  Seems I'm not the only one who runs into strange errors. Naturally, this error is a real bitch.  Windows fails to tell you WHICH audio device changed, making it a trial-and-error approach to debugging.  I hate that, as they could have easily mentioned which device was causing the offense. Plus it takes about an hour to re-create the error, making troubleshooting very slow. For my part, here is what did NOT fix the error: 1.  Disabling Windows driver signing enforcement.  My Hauppage WinTV-PVR-150 cards were listed as "Sound" devices in Device Manager, making them (possibly) "audio" devices to Windows.  They had yellow exclamation points in Device Manager only because the drivers are not signed for Windows 7.  So they worked, but they could have run into some kind of driver checking BS that caused the error sporiadically. However, turning off the driver checking using the ...