本地网络ABR直播测试及MPD文件正确性的技术求助

Hey there! Let's dig into why your ABR isn't switching and how to fix this step by step.

First, Decode That Console Message #

The line [3945283] AbrController (video) stay on 1/1 (buffer: 24.141) tells us the core problem: the player only detects 1 video representation total. Without alternative bitrate/resolution options, ABR has nothing to switch to—so it stays stuck on the only available stream. This points to either an issue with your MPD file or how the player is interpreting it.

Critical MPD File Checks #

Since you mentioned the MPD has two Adaptation Sets, let's focus on the video-focused one (the AbrController is referencing video). Verify these key details:

• Multiple Representations in the Video Adaptation Set: The video <AdaptationSet> must contain multiple <Representation> nodes, each with unique bandwidth, width, and height attributes. For example:

  <AdaptationSet mimeType="video/mp4" codecs="avc1.4D401E">
    <Representation id="1" bandwidth="500000" width="640" height="360"/>
    <Representation id="2" bandwidth="1500000" width="1280" height="720"/>
  </AdaptationSet>
  

  If your video Adaptation Set only has one <Representation>, that's why ABR can't function.
• Accessible Segment Paths: Ensure the <BaseURL> or <SegmentTemplate> in each <Representation> points to valid segment files on your local network. Broken or unreadable paths will make the player ignore that representation entirely.
• Consistent Media Metadata: Double-check the video Adaptation Set's mimeType matches your segment format (e.g., video/mp4 for H.264 in MP4 containers). Mismatched metadata can lead the player to discard valid representations.
• Dynamic MPD Timing: Since your MPD is marked as type="dynamic", confirm availabilityStartTime and publishTime align with your local live stream's timeline. Timestamps that are too far off can prevent the player from loading all available representations.

Fixing Bandwidth Simulation in Chrome #

The Performance Panel's throttling often doesn't work reliably for DASH streams. Try these more consistent methods:

• Network Panel Throttling: Open Chrome DevTools → Network tab, use the "Throttling" dropdown (top-left) to select a low-bandwidth preset like "Slow 3G". Refresh the page after enabling throttling—it won't apply to already loaded content.
• Command-Line Throttling: Launch Chrome with explicit network restrictions to guarantee bandwidth limits. For Windows:

  chrome.exe --user-data-dir="C:\temp\abr_test_profile" --enable-network-emulation --emulate-network-conditions --netem-rate=500k
  

  For macOS/Linux:

  google-chrome --user-data-dir="/tmp/abr_test_profile" --enable-network-emulation --emulate-network-conditions --netem-rate=500k
  

  This caps bandwidth at 500kbps, which should trigger ABR switching if your MPD is correctly structured.

Next Step: Share the Full Video Adaptation Set #

To pinpoint the exact MPD issue, could you share the full content of your video <AdaptationSet> (and surrounding MPD code if possible)? Wrap it in a code block so it's easy to parse.

内容的提问来源于stack exchange，提问作者Massimo Vantaggio