ACEScc - Preview doesnt match with final output

alifftudm95 wrote on 3/20/2021, 6:35 AM

Doing some experiment in ACES color spaces.

My project settings:

1080p

Pixel format 32 bit Full Range

Compositing Gamma 2.222 Video

ACES Version 1.2

ACES color spaces ACEScc

View Transform REC709

My monitor is BenQ PD2700U, set it to REC709 mode. By right, the monitor color mode shall sync with VEGAS view transform.

I exported the quick graded clip (The footage was assigned with Slog2 Sgamut IDT) with REC709 color spaces & color range to limited.

The final output have more contrast then what I see in VEGAS Preview window.

But, If I import the exported clip into VEGAS & assigned it with REC709 IDT, it match perfectly fine with original footages.

Back to post

Comments

RogerS wrote on 3/21/2021, 8:39 AM

@Yelandkeil I see, that is helpful. Looking at this thread while the footage was shot in S-log I believe the intended output is Rec 709, so the view transform should be just Rec 709, right?

Absolute wrong!

View Transform IN VEGASPRO concerns only one thing: getting the correct editing picture view with proper equipment.

To transcode the wanted output, that's the job of the render machine. ACES has many many render machines.

As you leave the ACESpace, you have only one machine: Rec709.

What is wrong? Of course you want to get the proper "editing picture" or you can't visually see what you are doing or edit the footage.

So output Rec 709, view transform to sRGB (or Rec 709?) and input tranform (Rec 709) to match the footage, I assume.

Yelandkeil wrote on 3/21/2021, 8:48 AM

Oh mano'man!

Please help me to set my view transform:

1, I want to output Rec2020

2, I want to output P3-DCI

3, I want to output RED-Linear-REDcolor4

......

alifftudm95 wrote on 3/21/2021, 8:57 AM

1, I don't recommend the ACESpace for Rec709 production. Reasons are simple: several FXplugins can't be used in this huge space due to their limitation and the space itself requires a real powerPC.

2, I do recommend the 32-bit floating full-mode for Rec709 production because it avoids every color banding artifact. People doubt that the final rendering just packs everything in 8-bit and where does the benefit come from. Well, algorithms for processing and packing are different. I'm not engineer.

3, materials like Log-file could be treated with LUT, but I don't have any experience and, in my opinion, the Color-Match plugin is way better. Vegaspro introduces LUT filter also very lately.

4, view transform is about hardware/equipment, not videosignal transcode.

I'm confused a bit when you recommend to use 32 bit full in VEGAS, because that mode is already ACES, or u saying using the default color space in 32 bit?

I'm a kinda novice in this whole color system, which I try to learn and understand.

RogerS wrote on 3/21/2021, 10:22 AM

1, I don't recommend the ACESpace for Rec709 production. Reasons are simple: several FXplugins can't be used in this huge space due to their limitation and the space itself requires a real powerPC.

2, I do recommend the 32-bit floating full-mode for Rec709 production because it avoids every color banding artifact. People doubt that the final rendering just packs everything in 8-bit and where does the benefit come from. Well, algorithms for processing and packing are different. I'm not engineer.

3, materials like Log-file could be treated with LUT, but I don't have any experience and, in my opinion, the Color-Match plugin is way better. Vegaspro introduces LUT filter also very lately.

4, view transform is about hardware/equipment, not videosignal transcode.

I'm confused a bit when you recommend to use 32 bit full in VEGAS, because that mode is already ACES, or u saying using the default color space in 32 bit?

I'm a kinda novice in this whole color system, which I try to learn and understand.

I'm pretty confused by these statements. 32-bit full is ACES now...

The Vegas LUT loader works fine, at least in 8-bit and 32-bit video modes.