ACES/32-full & sLOG3

ALO wrote on 6/22/2025, 10:53 AM

Am I crazy or is Vegas applying all clip/track/bus-level fx before the transform from sLog3 to REC709 inc CG Panel? There's no way to grade footage with this behavior!

sLOG3 footage on 32FR timeline

clip-->properties-->color space sLog3/sGamut3

ACES-->default

view transform-->REC709

VP22/248

Last changed by Steve_Rhoden on 6/26/2025, 7:21 PM, changed a total of 1 times.

Reason: Start heading back down the road he was previously blocked for (nonstop shots at the development team)

Dell XPS 15 9520 (main)

i9-12900HK 2.5GHz 32GB RAM

NVIDIA GeForce RTX 3050 Ti

current Windows/Vegas builds (non-beta/non-preview)

Comments

RogerS wrote on 6/22/2025, 11:15 AM

How did you conclude that?

ALO wrote on 6/22/2025, 7:23 PM

because even a simple levels fx is operating in the log space, not in REC 709

RogerS wrote on 6/23/2025, 7:47 AM

I wonder if that's the wrong way to look at it- that in ACES you're in the ACES color space, not Rec709.

https://www.vegascreativesoftware.info/us/forum/aces-and-acescc-intro-and-tutorial-for-vegas-pro--100416/

Howard-Vigorita wrote on 6/23/2025, 11:40 AM

@ALO I think you're right that cgp is not operating in Rec709 color space when it is selected as a view transform. Which functions only for viewing the display. If you really want to edit in Rec709 space, you need to apply the log to the footage via a transcode before edit. In which case it would be easier to have just set your camera to shoot in Rec709. But then you're losing any advantages log shooting might have.

ALO wrote on 6/25/2025, 9:52 PM

I mean, I guess you could nest a Vegas ACES project in a new project. I'm not saying there aren't times when you want to make tweaks before the log transform, but it seems flat-out crazy to me that Vegas doesn't give you an easy way to control the order of operations if you choose to go the ACES route.

Note that there are obvious advantages to editing in a wide-gamut space (Resolve makes this easy and most pros like to edit this way), but I'm not talking about that. You need to decode your log footage to REC709 (or a normalized gamma) before you can grade it. As far as I can tell, if I put an sLog3 clip on the timeline and flag its colorspace for proper decoding, everything I do from an fx point of view happens *before* that transform.

It's just so discouraging to me that Vegas' developers don't seem to understand even the minimum basics of a modern 10-bit color-managed workflow, and leave it to users to just flounder around with half-implemented features :(

RogerS wrote on 6/25/2025, 11:07 PM

With ACES you are defining the input and then working in a wide gamut space with a SDR or HDR preview so you can see what you are doing, no?

It works with media in any supported color spaces and transforms them into one unified space like ACEScc for correction and grading. From there you output to any desired colour space.

Are you saying that the VEGAS implementation through OpenColor is defective in some way?

If you want to work in Rec 709 apply a Lut at the media level and do grading after that with ACES off.

Last changed by RogerS on 6/25/2025, 11:11 PM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with latest studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.250

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

ALO wrote on 6/26/2025, 9:59 AM

Well, I tried nesting a 32FR/ACES project inside a new Vegas project. That breaks just about everything. All of the Vegas 32-bit bugs bite with a vengeance, so that's not an option.

This is how things should work:

(sLog3 clip) --> (transform to REC709) --> (fx applied here to grade)

This is how ACES mode seems to be working:

(sLog3 event) --> (fx applied here!) --> (transform to REC709) --> (no way to apply anything here)

I suppose I could reinstall Sony VP 9 to prove a point here, but really...the venn diagram of things you can do in the current Vegas that don't cause fatal problems keeps getting smaller and smaller. I'm building my entire Vegas workflow around expertise in what to avoid

Adis-a wrote on 6/26/2025, 3:12 PM

This is how things should work:

(sLog3 clip) --> (transform to REC709) --> (fx applied here to grade)

That somehow defeats the purpose of recording to LOG, you could then record in Rec.709.

ALO wrote on 6/26/2025, 4:05 PM

I'm not going to try to explain how a log workflow works here.

I will note that in ACES mode, an sRGB event shows this same strange behavior. Put an sRGB image on the timeline, flag it (clip properties-->colorspace) as sRGB. Switch project properties-->pixel formal to 32 full range. Put a levels fx on the clip. In this configuration, it should not matter whether or not view transform is active. You should get the same result. Drag the levels around and compare between view transform on and off.

If Vegas was working correctly, you'd expect the same result, right?

Anyhow, I'm done with this subject. It's yet another critical broken feature in the 32-bit modes.

Seriously: maybe deprecate the 32-bit modes until you can get them working? This is ridiculous. How much reputational harm has been done to Vegas because the developers insist on pretending all is well?