Open r-vdp opened 1 year ago
Yeah, it's not intentionally excluded. Happy to accept contributions if you can add that.
Trying to figure out where that extra timing is: looks like just a detailed timing descriptor block inside the CTA extension block? That should be supported, there must be a bug or something, because I'm pretty sure I remember seeing something in an equivalent place when I was making the JSON schema for this.
Oh nvm the 3840 resolutions are in:
So yeah, missing features. Contributions welcome.
The short video descriptors look like they're parsed correctly for the most part. According to this wikipedia page, those are one byte each, pointing into a lookup table of resolutions.
The three before the last one, the ones with VICs 93, 94, and 95, are the 3840x2160 modes for 24, 25, and 30 fps, it just needs a way to map VICs to resolutions; the very last one might be a bug though.
It looks like the vendor specific blocks are parsed correctly, just not interpreted.
After a lot of searching for a tool to edit EDID data and save the result to a new binary file, I came across this repo.
However, it seems that not all data is included if I run
edid2json
on my monitor's EDID file. Notable, the actual higher resolution modelines are missing, there is no mention of 3840x2160 in the output ofedid2json
.Do you have any idea why this is? Is it simply not implemented? It would be great if we could extend this tool to cover all this data too. I might be able to help out in doing that.
E.g.,
edid-decode
gives me this:Whereas
edid2json
on the same EDID file gives me this: