What Is Demu and Why Internal Resolution Matters
Demu is commonly invoked when displays, capture cards, and streaming gear report unexpected resolution or timing behavior. Internal resolution refers to the fixed timing domain used by the chip to process pixels before any output scaling or conversion. When Demu cannot change internal resolution, it usually indicates timing, firmware, or driver constraints rather than a simple setting toggle.
This article explains the common causes, compatibility scenarios, and safe workarounds for situations where resolution changes are blocked. The guidance targets capture devices, HDMI/DP peripherals, and integration with encoders, streamers, and production tools.
Core Constraints That Prevent Resolution Changes
Firmware and Bootloader Limitations
Some Demu-based devices ship with firmware compiled for a single native mode. If the firmware lacks parameter tables for other resolutions, the driver cannot load alternative timing models. This is common in budget capture dongles and legacy boards that only expose EDID templates tied to one fixed mode.
Physical Interface and Protocol Limits
HDMI and DisplayPort impose bandwidth ceilings. For example, HDMI 1.4 at deep color and high refresh can exhaust the available bandwidth, forcing the device to reject nonstandard timings. Similarly, DisplayPort 1.1 with limited lanes may restrict the pixel clock, making certain resolutions unsupported unless the firmware explicitly reconfigures the link.
Driver and Operating System Constraints
The host GPU driver, USB or PCIe transport layer, and OS-level mode-setting must all agree on a valid mode. If any component lacks a connector or timing entry, the system falls back to a safe default. Demu firmware that does not advertise a mode through EDID or standard enumerations will be ignored, making changes impossible until the chain is updated.
Identifying Why Demu Can't Change Internal Resolution
Diagnosis starts with gathering data from the device itself and the host system. Examine EDID, timing reports, and system logs to locate the bottleneck.
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Device EDID revision | EDID lists only one native mode | Read EDID via OS tools |
| Pixel clock limit | Device maxes out at interface spec (e.g., HDMI 1.4 340 MHz) | Device datasheet or measured with test pattern |
| Firmware version | Version lacks alternate timing tables | Vendor release notes or device info command |
| Driver-reported modes | Mode list in OS display settings excludes desired resolution | Operating system diagnostics or API query |
| Link bandwidth usage | Active video stream consumes most of available bandwidth | Protocol analyzer or GPU control panel |
Practical Workarounds and Safe Adjustments
If Demu cannot change internal resolution, focus on upstream or downstream scaling to match your target output while avoiding timing-related disconnects or frame drops.
- Use a capture card or scaler upstream that converts to a mode the device accepts, then rescale in software or hardware to your final delivery resolution.
- Update firmware and drivers; vendors sometimes add tables for common studio formats such as 1080p60, 1440p60, or 4K30.
- Force a modeset at the GPU level, then ensure the capture path treats the input as a fixed feed matching that mode.
- Reduce color depth or chroma subsampling to lower bandwidth, enabling otherwise unsupported resolutions within link limits.
- Replace or patch firmware if open-source tools support the device and risk is acceptable.
When to Expect a Real Resolution Change
Resolution changes become possible only when one or more constraints are removed:
- The internal timing generator is reprogrammed via updated firmware.
- The transport interface supports a higher bandwidth mode.
- The host driver advertises a custom mode and the device accepts it.
Until then, treat the current resolution as a fixed property of the Demu path and plan capture, encoding, and output around it.
Compatibility Matrix and Common Scenarios
| Scenario | Internal Resolution Status | Recommended Action |
|---|---|---|
| Single-mode firmware, HDMI 1.3 input | Cannot change | Add upstream scaler or replace device |
| Firmware updated, DP 1.4 available | Can change if bandwidth allows | Set custom mode in OS and verify timing |
| GPU passthrough in virtual machines | Limited to VM-exposed modes | Adjust VRAM and monitor group settings |
Validation, Safety, and Long-Term Reliability
When applying workarounds, validate timing safety with measured reports. Prefer hardware scalers over firmware hacks for critical production paths. Document the exact mode, color format, and link settings so future changes are deliberate rather than accidental.
For environments demanding frequent resolution shifts, plan for devices with reprogrammable timing engines and verified firmware updates from the vendor. Treat unsupported modes as edge cases, not standard configurations.