- Posts: 18
- Joined: Wed Jun 24, 2015 2:40 am
I use ACEScc as timeline colour space in RCM and I use Rec.709 Gamma 2.4 as my output colour space.
When I try to make a clip monochromatic either by de-saturating the image all the way down to zero or by checking the monochrome checkbox in mixer, I always get a colour tint in the supposedly monochrome image, verifiable on the scopes. You can even see the shift when highlighting qualification or power windows - anywhere grey will have a colour tint to it - verifiable on the scopes.
I checked if the issue persisted when I bypass output transform, and the colour shift did went away. I also checked if it persisted when I use other output colour spaces (such as Rec.2020) and it did (verifiable on scopes). It seems that RCM is not handling the transform from ACES to other output colour spaces very well.
I believe you can easily recreate the problem if you set ACEScc as timeline colour space and anything other than bypass as output colour space.
Maybe I shouldn't use ACEScc with RCM? But I don't use the ACES workflow because ACES is noticeably slower than RCM on my laptop. And I like the feel of grading and how the controls respond in ACEScc so I resorted to using ACEScc with RCM. And Resolve still does not come with a Pocket 4K IDT yet (or does it?) so using RCM seemed to be the only option if I don't want to use a LUT workflow.
It's not that big of an issue for me, as I almost only export to Rec.709 and don't have to worry about RCM spitting out different results in different output colour spaces, so basically I just grade for Rec.709. But black & white image can be tricky to get.
Hopefully it can be fixed, but even it doesn't get fixed, please leave ACEScc in RCM as an option, I do enjoy this combination.
When I try to make a clip monochromatic either by de-saturating the image all the way down to zero or by checking the monochrome checkbox in mixer, I always get a colour tint in the supposedly monochrome image, verifiable on the scopes. You can even see the shift when highlighting qualification or power windows - anywhere grey will have a colour tint to it - verifiable on the scopes.
I checked if the issue persisted when I bypass output transform, and the colour shift did went away. I also checked if it persisted when I use other output colour spaces (such as Rec.2020) and it did (verifiable on scopes). It seems that RCM is not handling the transform from ACES to other output colour spaces very well.
I believe you can easily recreate the problem if you set ACEScc as timeline colour space and anything other than bypass as output colour space.
Maybe I shouldn't use ACEScc with RCM? But I don't use the ACES workflow because ACES is noticeably slower than RCM on my laptop. And I like the feel of grading and how the controls respond in ACEScc so I resorted to using ACEScc with RCM. And Resolve still does not come with a Pocket 4K IDT yet (or does it?) so using RCM seemed to be the only option if I don't want to use a LUT workflow.
It's not that big of an issue for me, as I almost only export to Rec.709 and don't have to worry about RCM spitting out different results in different output colour spaces, so basically I just grade for Rec.709. But black & white image can be tricky to get.
Hopefully it can be fixed, but even it doesn't get fixed, please leave ACEScc in RCM as an option, I do enjoy this combination.