- Posts: 22
- Joined: Fri Mar 01, 2013 11:12 pm
I could not find a better place to post this so here goes. For all 3 platforms, even with the newest 10.0 SDK, the _BMDDisplayMode enum is missing the 3 2K DCI modes (2d23, 2d24, 2d25) from the header, so it is not possible to set this mode without constructing an int with the proper bytes set by hand (and then casting it to a BMDDisplayMode). The DeviceList program on my 4K extreme card shows that 2K DCI is supported for both input and output, yet it is completely missing from the SDK (also the headers say that 4K DCI is output-only, but DeviceList disagrees). I modified DeviceList to print out the raw display mode values and it confirms the 2d23 2d24 etc. naming does exist:
2d23 2K DCI 23.98 2048 x 1080 23.976 FPS 8-bit YUV 10-bit YUV 8-bit ARGB 8-bit BGRA 10-bit RGB
2d24 2K DCI 24 2048 x 1080 24 FPS 8-bit YUV 10-bit YUV 8-bit ARGB 8-bit BGRA 10-bit RGB
2d25 2K DCI 25 2048 x 1080 25 FPS 8-bit YUV 10-bit YUV 8-bit ARGB 8-bit BGRA 10-bit RGB
Can someone from Blackmagic confirm this is a bug? Manually setting the display mode to 2d25 etc. still works, but it should be part of the BMDDisplayMode enum in the header with the rest of the modes.
2d23 2K DCI 23.98 2048 x 1080 23.976 FPS 8-bit YUV 10-bit YUV 8-bit ARGB 8-bit BGRA 10-bit RGB
2d24 2K DCI 24 2048 x 1080 24 FPS 8-bit YUV 10-bit YUV 8-bit ARGB 8-bit BGRA 10-bit RGB
2d25 2K DCI 25 2048 x 1080 25 FPS 8-bit YUV 10-bit YUV 8-bit ARGB 8-bit BGRA 10-bit RGB
Can someone from Blackmagic confirm this is a bug? Manually setting the display mode to 2d25 etc. still works, but it should be part of the BMDDisplayMode enum in the header with the rest of the modes.