Custom EDIDs for LED processors and media servers
Short answer: a media server or graphics card can only output resolutions the connected device's EDID offers. For an LED canvas such as 3000 × 400, build an EDID with that exact timing, load it where the source will read it, and the server outputs the canvas pixel for pixel, with no scaling.
Build a 3000 × 400 EDID →
Step by step
- Size: enter the canvas size in pixels. CVT and RB v1 round the width down to a multiple of 8 (6100 becomes 6096); RB v2 keeps any width.
- Refresh: match your sync source: 59.94 or 50 Hz when the system is locked to broadcast or house sync, 60 otherwise. Leave the pixel clock on Exact refresh so the rate lands on target.
- Blanking: start with RB v1. Switch to RB v2 only if the link is tight and the processor accepts it. Which blanking to use.
- Bit depth and color: 8-bit RGB 4:4:4 suits most LED processors. Use 10-bit only if the processor and every device in the chain support it.
- Connector: check the Connectors panel shows the signal fits HDMI or DisplayPort on the actual ports you're using.
- Audio: leave it Off for LED processors unless something downstream needs it.
- Export the EDID as .bin (raw bytes, what most tools load), .txt (hex) or .edid, and load it.
Where to load it
- On the LED processor input: most processors let you upload a custom EDID per input, so the source reads it straight from the processor.
- In an EDID emulator or matrix between the media server and the processor, which presents the EDID to the source.
- On the graphics card: NVIDIA workstation GPUs can load an EDID file per output (NVIDIA Control Panel → View system topology → Manage EDID → Load). Your media server's documentation covers its own EDID tools.
Example: 3000 × 400 at 59.94 Hz
| Blanking | Active | Total | Pixel clock | Refresh |
|---|---|---|---|---|
| RB v1 | 3000 × 400 | 3160 × 419 | 79.36 MHz | 59.938 Hz |
| RB v2 | 3000 × 400 | 3080 × 415 | 76.61 MHz | 59.936 Hz |
Even at 8-bit RGB this uses only 23% of HDMI 1.4, so any connector will carry it.
RB v1 timing
| Active | Front porch | Sync pulse width | Back porch | Total | Polarity | |
|---|---|---|---|---|---|---|
| Horizontal | 3000 | 48 | 32 | 80 | 3160 | Positive |
| Vertical | 400 | 3 | 10 | 6 | 419 | Negative |
Watch out for
- Very wide or very fast canvases. A standard EDID timing tops out at 4095 pixels wide and 655.35 MHz. 6096 × 2160 at 60 Hz needs 834.04 MHz, so PixelTach writes it in a DisplayID block with a 1080p60 fallback, the same layout as the Analog Way EDID editor. Some sources ignore DisplayID, so test before the show.
- Canvases too big for one output: split them across several outputs, each with its own EDID (PixelTach's multi-output canvases, in the Supporter Toolbox).
- Reduced blanking v2 on HDMI with embedded audio: the 80-pixel gap may not leave room for audio on some sources.