Comments

mark-y wrote on 5/29/2024, 10:55 AM

You need to set the correct Colorspace in Media Properties, because Vegas may not register them correctly.

fr0sty wrote on 5/29/2024, 12:46 PM

2 approaches...

1. (My preferred)

Do all of your editing first in 8 bit mode. When done and ready to render, switch it to 32 bit full range mode.

Right click on your media and go to properties, and under color space set it to S log, there's various S log varieties in there so be sure to set it to the correct one.

You will notice the cloud effect goes away then, but you can still use the color grading panel to further color it to your liking.

2. Leave it in 8 bit mode, and use a conversion lut in the color grading panel. You can either download one made by Sony, or use one of the ones that are built into Vegas on the input tab of the color grading panel.

Rony-Alfandary wrote on 5/29/2024, 1:56 PM

Thank you both @fr0sty and @mark-y for your advice

RogerS wrote on 5/29/2024, 6:05 PM

VP 21 may not correctly read the color range metadata of full range files so manually change it from undefined to full as needed.

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, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208

Try the
VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

mark-y wrote on 5/29/2024, 9:36 PM

ALO wrote on 5/31/2024, 8:50 AM

For people who are not highly experienced with color grading & ACES, I would strongly recommend the LUT approach. Work in 8-bit (project properties) mode with a good conversion LUT applied; switch to 32-bit video levels (not FR) for your render out, making sure you're sending correct levels to the encoder.

Joel's Phantom LUTs are excellent for converting sLog3/sGamut3.Cine to REC709. Sony's free conversion LUT via their LUT library is also a solid option.

 

RogerS wrote on 5/31/2024, 9:37 AM

If you uses the LUTs with 32-bit full (helpful to match 8-bit full), just set view transform to off to avoid double-correcting with ACES. I do this with the Leeming LUT.

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, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208

Try the
VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

mark-y wrote on 5/31/2024, 11:38 AM

If you have the correct Camera Profile in Vegas, LUTS aren't really necessary.

But since it was brought up, you can download the Sony Camera LUTS, also Canon, Panasonic Grading LUTS, and a number of others including some custom LUTS for Vegas, free of charge.

https://drive.google.com/open?id=12q-Ehteq7q7rYHiX7Kwtp2C2GpQwrXZ5&usp=drive_fs

Rony-Alfandary wrote on 5/31/2024, 12:03 PM

If you have the correct ACES Profile in Vegas, LUTS aren't really necessary.

But since it was brought up, you can download the Sony Camera LUTS, also Canon, Panasonic Grading LUTS, and a number of others including some custom LUTS for Vegas, free of charge.

https://drive.google.com/open?id=12q-Ehteq7q7rYHiX7Kwtp2C2GpQwrXZ5&usp=drive_fs

Great. What do I do with them? do they need placing in a particular directory? Install them? This is unfamiliar territory for me.... Thank you

ALO wrote on 5/31/2024, 6:33 PM

Let me just add, I personally think sLOG3 is a very challenging format. For now it's the closest we get to in-cam RAW from a Sony sensor, which is awesome, but the learning curve is steep on both ends and in many cases you can just shoot a standard Sony picture profile and get great results. If you want to dive into this rabbit hole go for it...but it is a long way down :)

john_dennis wrote on 6/1/2024, 4:48 PM

The case against S-Log3...

  • From My Camera
  • On My Machine
  • For My Subject Matter

I shot some S-Log3 as a thought experiment this morning.

As a rule, I use Picture Profile 6, Cine 2 which produces good control over highlights and is much more efficient to process.

mark-y wrote on 6/1/2024, 8:45 PM

Let me just add, I personally think sLOG3 is a very challenging format. For now it's the closest we get to in-cam RAW from a Sony sensor, which is awesome, but the learning curve is steep on both ends and in many cases you can just shoot a standard Sony picture profile and get great results. If you want to dive into this rabbit hole go for it...but it is a long way down :)

Oh, I kind of enjoyed the challenge. Actually it's pretty easy with the right profile, and being a retired film grader doesn't hurt.

Sony SLog3.SGamut3.Cine

 

Howard-Vigorita wrote on 6/2/2024, 9:01 AM

@Rony-Alfandary I use what fr0sty lists as approach #2 but don't leave it in 8-bit full-mode for final render. I switch to 32-bit full mode and only correct the compositing gamma and view transforms in project properties:

I don't have a Sony camera but I get 64- or 65-point luts from Canon and Zcam which yield better results than the few supplied with Vegas in its CGP. For convenience, I throw them into this folder so they show up in the vp21 CGP drop-down:

C:\Program Files\VEGAS\VEGAS Pro 21.0\OFX Video Plug-Ins\Vfx1.ofx.bundle\Contents\Resources\AutoLooks