That's not a great workaround. Changing to YCbCr as input requires conversion of the colorspace from RGB, which the application would have to do. So it may be faster to write, but the conversion would add overhead. Presumably it would be better to let the API do the colorspace in and out of YCbCr rather than implementing it manually, and if the coprocessor of the Max/Pro/Ultra chips can do this, there's no way I can do it faster on the CPU.

Sadly, it isn't fixed.

That does work, but it's an annoying workaround. It involves the application doing the color space conversion from RGB to YCbCr, which eliminates any performance gains (it is better to have the API do this symmetrically on read and write than to implement it in the application). And if the ProRes hardware encoding of the M1 Pro/Max/Ultra can do the color space conversion, it's very unfortunate to have to offload this to the CPU.

Thanks! That's interesting. Does anyone know a way to query the supported kCVPixelFormats at runtime? I thought I ran across that in the docs once, but it's lost to my searches now. Probably just dreamed it.

I tested this on macOS 12.1 Beta 3, and it's still broken. Wondering if there's been any update.

Thanks! I have done so. The feedback number is FB9757381. Thanks very much again!