How to Use Intel Video Pro Analyzer for AV Signal Debugging

Troubleshooting Common Issues in Intel Video Pro Analyzer

1. No Signal Detected

• Check connections: Verify all cables (SDI/HDMI/DisplayPort) are seated and undamaged.
• Confirm input settings: Ensure the analyzer input matches the source format (resolution, frame rate, color space).
• Test with known-good source: Connect a different, confirmed-working signal to isolate the problem.

2. Incorrect or Missing Audio

• Verify audio configuration: Confirm the analyzer is set to the correct audio channels and sample rate.
• Check embedding/embedding status: For embedded audio (e.g., HDMI/SDI), ensure the source is actually sending audio and that channels aren’t muted.
• Inspect cable/format compatibility: Some adapters or converters strip audio—test direct connections.

3. Frame Drops or Stuttering

• Check capture settings: Match capture buffer size and input format to the source; lower buffer may cause drops.
• Monitor system resources: High CPU, GPU, or disk I/O can cause stutter—close unnecessary apps and ensure fast storage.
• Update drivers and firmware: Outdated GPU or capture device drivers and analyzer firmware can introduce instability.

4. Color or Gamma Incorrect

• Confirm color space and bit depth: Mismatched RGB/YCbCr, limited/full range, or bit-depth settings cause shifts.
• Disable automatic color adjustments: Some capture chains apply automatic corrections—turn those off for accurate analysis.
• Use reference test patterns: Feed known patterns to isolate whether the issue is in source, capture, or analyzer.

5. Sync and Timing Errors (Dropped/Repeated Frames, Black Frames)

• Check genlock and reference signals: If using multiple devices, ensure proper reference (SDI tri-level/blackburst) and genlock.
• Inspect timestamping and timebase: Incorrect timebase or PTP/NTP drift can cause misalignment—verify clock sources.
• Replace long or problematic cables: Poor cable quality can introduce signal integrity issues.

6. Analyzer Crashes or Freezes

• Collect logs and reproduce steps: Note the exact actions leading to the crash and save analyzer logs for diagnosis.
• Update software/firmware: Install the latest analyzer software and firmware; patch known stability bugs.
• Run on supported hardware: Confirm system meets minimum requirements and uses supported OS/drivers.

7. Incorrect Metadata (EDID/HDCP/InfoFrames)

• Read EDID directly from source/display: Verify EDID content matches expected capabilities.
• Check HDCP handling: Some analyzers cannot decrypt HDCP-protected signals—use an unprotected test source.
• Validate InfoFrames and ancillary data: Capture and inspect VBI/ancillary packets to ensure correct transmission.

8. Low