• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Scopes look different in 2023 than 2023 Beta - beta is correct

Engaged ,
Oct 19, 2022 Oct 19, 2022

Copy link to clipboard

Copied

I have a single file sequence in .exr that I am bringing into AE (both regular release and beta). I am using the ACES color space. 

 

The Beta Vectorscope shows the colors accurately and match Premiere's scopes. But the scopes in the regular AE 2023 release are way out of whack. Every setting is identical in each program. Shots are attached.

 

Could this because because of the new OCIO implementation in AE Beta? If so, I wish they'd fix the scopes in the regular releaase to read properly.

 

 

 

 

TOPICS
Bug

Views

241

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Expert , Nov 06, 2022 Nov 06, 2022

There are a bunch of variables at play here. First, the vectorscope reads your data as Rec.709 by default. If your working space/current image is something different, the way it presents the data is false no matter what. Secondly you probably want to make sure you set your scopes to float not 8bit clamp. Lastly if you work with OCIO the display transform isn't taken into account when reading your scopes because it analyses the working space and not the viewer result. This is typically what you w

...

Votes

Translate

Translate
Community Expert ,
Nov 06, 2022 Nov 06, 2022

Copy link to clipboard

Copied

There are a bunch of variables at play here. First, the vectorscope reads your data as Rec.709 by default. If your working space/current image is something different, the way it presents the data is false no matter what. Secondly you probably want to make sure you set your scopes to float not 8bit clamp. Lastly if you work with OCIO the display transform isn't taken into account when reading your scopes because it analyses the working space and not the viewer result. This is typically what you want because you want to see if you have values above 1.0 for example on your waveform. But sometimes you may want to evaluate display referred. We need an option for this. In my OCIO feedback thread I mention this. See point 4.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Nov 07, 2022 Nov 07, 2022

Copy link to clipboard

Copied

LATEST

Thank you, Shebbe. This post answers my questions perfectly. I'll take a look at your other thread. Yes, the option to see the display's output would be nice on the AE scopes, since that is what I want to send to Premiere.

 

I did discover that if I just add a lumetri color effect on an adjustment layer with saturation set at 99.9 in my AE project, it puts all the colors in the proper Rec709 color space in Premiere when it is exported from AE. If I don't do that they are way out of range. Why it works? Got me.

 

So for now I just ignore the scopes in AE. Thank you again.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources