M1/ARM version doesn't gamma encode output of linearised project if color spaces match ?!?!
This is a bit nuts so if anyone has a second to either confirm it's a bug or point out my idiocy it'd be much appreciated; there's a minimal project file attached.
I tend to work with a linearised sRGB working space, and when rendering to an sRGB output file, AE correctly applies gamma correction to de-linearise the image. Except it's not doing it on my M1 machine; it outputs a linear space file. The same project opened on Intel vs ARM64 machines show the problem:
To reproduce:
- open the attached project. It contains an empty comp and a single render item.
- look at the File > Project Settings... > Color dialog. It should show the project is using a linearised sRGB working space:
- go to the Render Queue, click on the Output Module (ProRes), and go to the Color Management tab.
On my Intel Mac Pro, I see this:
Note the middle paragraph - though I'm outputting to the same colour space as the project, AE knows it has to apply gamma.
On my M1 MacBook Pro, I see this:
... which is patently wrong. Even if I manually select sRGB in the Output profile list, AE still doesn't recognise that the Working Space is linearised while the output space shouldn't be. The only way I can get a correctly gamma-encoded output is to choose something other than sRGB as an output profile (say, Rec.709) - which seems to nudge AE into recognising it has to gamma encode the output.
Same project, same version of AE Beta, on both machines. Vanilla installs on both, plus the same set of plugins.
Is this something I've done? I'm at a loss; never come across this before, and it's driving me crazy.
AdChoices