You try to play a video in Windows Media Player (WMP) and get slapped with error 0XC00D1BDF. It's annoying because the file plays fine in VLC or MPC-HC. Let's fix it.
The Direct Fix: Re-encode Audio to Constant Bitrate (CBR)
The error happens because WMP's streaming engine can't handle variable bitrate (VBR) audio—specifically when it tries to generate broadcast metadata. The cleanest fix is to re-encode the audio stream to constant bitrate using FFmpeg.
ffmpeg -i input.mp4 -c:v copy -c:a libmp3lame -b:a 192k -ac 2 output.mp4Step-by-step:
- Install FFmpeg from
ffmpeg.org(or via Chocolatey:choco install ffmpeg). - Open a terminal in the folder with your broken file.
- Run the command above, replacing
input.mp4andoutput.mp4with your filenames. - Open the output file in WMP. Should work now.
What this does: -c:v copy keeps your video stream untouched (no quality loss there). -c:a libmp3lame -b:a 192k re-encodes the audio to MP3 at a constant 192 kbps bitrate. -ac 2 forces stereo, which avoids any channel config weirdness WMP might choke on.
Why This Works
The root cause is WMP's audio pipeline. When WMP reads a file, it tries to generate broadcast information—stuff like stream duration, bitrate, and codec details—to populate its UI and support features like seeking. VBR audio doesn't have a fixed bitrate value; it fluctuates during playback. WMP's code for generating that broadcast info expects a constant bitrate, gets confused by VBR's variability, and throws NS_E_CANNOT_GENERATE_BROADCAST_INFO_FOR_QUALITYVBR.
The specific audio codecs that trigger this are usually AAC (especially in MP4 containers) or WMA with VBR encoding. By converting to CBR MP3, you're giving WMP exactly what its broadcast info generator expects: a steady, predictable bitrate.
Why not just change WMP settings? There's no registry key or checkbox to fix this. The bug is in wmpeffects.dll or the streaming filter—Microsoft never patched it because WMP is basically abandonware since Windows 8.
Less Common Variations
Error pops up when you try to stream the file to an Xbox or DLNA device
Same cause, different context. The media server component in WMP also fails on VBR audio. Use the same FFmpeg fix above. If you need to keep the original file intact, create a separate copy just for streaming.
Error occurs only on certain files, not all VBR audio files
WMP is picky about the audio format version. AAC-LC (Low Complexity) VBR often triggers it, while AAC-HE (High Efficiency) VBR might not. Also check if your file has multiple audio tracks—sometimes the second track is VBR while the first is CBR. Use FFmpeg's -map 0:1 to isolate the problematic track and re-encode it.
ffmpeg -i input.mp4 -map 0:v -map 0:1 -c:v copy -c:a libmp3lame -b:a 192k output.mp4File plays fine in WMP on Windows 7 but fails on Windows 10
WMP in Windows 10 uses a different DirectShow filter chain. The newer wmpeffects.dll has a stricter validation for broadcast info. You can't downgrade it. Stick with the re-encode approach.
Prevention
If you're encoding your own videos, avoid VBR audio if you plan to play them in WMP. When using HandBrake, set the audio tab to "Constant Bitrate" and pick a bitrate like 192 or 256 kbps. In FFmpeg, never use -q:a (which enables VBR) for files destined for WMP. Use -b:a instead.
If you're downloading videos from YouTube or other sources, check the audio codec before saving. YouTube's default audio stream is usually Opus or AAC VBR—both will trigger this error in WMP. Use yt-dlp with --audio-format mp3 or --recode mp4 to force CBR.
yt-dlp -f 'bestvideo[ext=mp4]+bestaudio[ext=m4a]' --audio-format mp3 URLOne last thing: if you see this error on a file that plays fine in WMP but crashes when you try to burn it to a CD or share it via email, re-encode the audio. WMP's burning engine reads the audio stream directly and chokes on VBR just the same.