Color Profile LUTS for Vegas ~ NEW ~

Musicvid wrote on 3/23/2021, 2:16 PM

I have compiled the most common ICC color space profiles, as well as some camera and grading LUTS, and converted them to LUTS for use in Vegas. A list of the profiles includes:

  • Image Profile LUTS (AdobeRGB, Prophoto, et al)
  • Video Profile LUTS (2020, 709, et al)
  • Canon EOS Camera LUTS
  • Panasonic Color Grading LUTS
  • 185 LUTS in All

DOWNLOAD: https://drive.google.com/open?id=1AKe_ts4pSQ5fJVVGN_vN8Z8GyCUWkhnR&authuser=musicvid%40gmail.com&usp=drive_fs

  • USAGE: The most common example of needing a still image profile conversion in Vegas is Adobe RGB. Still photos created and profiled in this space are not color managed in Vegas, yielding uncharacteristically flat video output colors; the solution is to convert and save the still first to sRGB in Photoshop, or to color manage in Vegas using a LUT.
  • As an alternative to ACES, all of the Canon EOS LUTS are included, as well as spiffy Panasonic Color Grading LUTS.
  • Please let me know which LUTS you use the most, and which ones are needed, and I will include them in the next compilation.
  • They are free of charge -- Enjoy!

Comments

BobMoyer wrote on 3/23/2021, 2:41 PM

Thank you, they will come in handy.

Ecquillii wrote on 3/23/2021, 2:49 PM

Hey, thanks for all your hard work and all the ways you enrich this community!

Desktop:ASUS M32CD

Version of Vegas: VEGAS Pro Version 20.0 (Build 370)
Windows Version: Windows 10 Home (x64) Version 21H2 (build 19044.2846)
Cameras: Canon T2i (MOV), Sony HDR-CX405 (MP4), Lumia 950XL, Samsung A8, Panasonic HC-V785 (MP4)
Delivery Destination: YouTube, USB Drive, DVD/BD

Processor: 3.40 gigahertz Intel Core i7-6700
RAM: 16 Gigabytes
Graphics Card 1: AMD Radeon R9 370; Driver Version: 15.200.1065.0
Graphics Card 2: Intel HD Graphics 530; Driver Version: 31.0.101.2111
GPU acceleration of video processing: Optimal - AMD Radeon R9 370
Enable Hardware Decoding for supported formats: 'Enable legacy AVC' is off; 'Enable legacy HEVC' is on
Hardware Decoder to Use: Auto (Off)

RogerS wrote on 3/23/2021, 9:58 PM

Just a clarifying question- these are all intended to take photos in the listed color spaces and convert them to sRGB for use in Vegas? So for ProPhoto you'd take a photo that was saved in ProPhoto, then apply the LUT and it would appear normal on the timeline next to a regular sRGB photo?

I just ask because some of these color spaces are unusual for photos, so would videopal be the same concept but to use on a PAL video to bring it into Rec 709?

Musicvid wrote on 3/24/2021, 10:42 AM

Have you tried Prophoto? I need some feedback. I've only tested Adobe.

The legacy spaces are there because they were available and easy to convert. If I was to predict their use, I would say Adobe 99%, ProPhoto 1%, and the rest 0%. I found them here. But fun to play with.

RogerS wrote on 3/25/2021, 2:19 AM

I think ProPhoto is okay, too. There are slight luminance and color differences between the three profiles, and I don't know if that's rounding errors or inherent to conversions between color spaces of quite different sizes. I think it's acceptable.





Testing it on an actual photo (16-bit ProPhoto PSD) it matches Photoshop well.

Huge before and after difference, too (split screen- left side is pre-LUT)


 

fr0sty wrote on 3/25/2021, 4:12 AM

Are these LUTs for converting these formats to a Rec709 display? What about Rec2020 targeted output?

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

RogerS wrote on 3/25/2021, 6:36 AM

These LUTs appear to be converting for use on a Rec 709 timeline.

Musicvid wrote on 3/25/2021, 8:37 AM

I don't have a full 2020 monitor to test with.

Glad Prophoto is working for you. The P3 cinema LUTS are a hoot! (D60, D65, DCI)

RogerS wrote on 3/25/2021, 9:08 AM

I can't say I understand what the LUT is doing, but the sRGB file and ProPhoto with LUT applied look different in HDR (HDR 10) mode.

HLG mode was much more similar though red and green hue is a bit off.

It looked worse (dull, washed out) when the color space was set to Rec 709 or sRGB.

Musicvid wrote on 3/25/2021, 9:35 AM

I don't understand HDR mode very well.

RogerS wrote on 3/25/2021, 9:54 AM

I think we need a LUT that goes from sRGB, ProPhoto, etc. to Rec2020.

For remapping white point to get above 100 nits, can selecting the Rec 2020 input display transform/"color space" do this if the colors were mapped to Rec 2020 by the LUT? Not sure of order of operations here and it may matter.

As an alternative,I converted from ProPhoto to Rec2020 using ICCs in Photoshop, and then assigned the Rec 2020 color space in Vegas.

In HDR 10 mode it looks dull with white around 650 the Rec 2020 spaces with 1000, 2000, 4000 nits, etc. all clip whites.

In HLG mode whites get up to about 6600/10,000 with regular Rec 2020. If set to Rec 2020 / HLG 1000 it doesn't look bad and fills up the RGB parade:


I don't have an HDR monitor to actually view this with, though.

Musicvid wrote on 3/25/2021, 5:47 PM

I think we need a LUT that goes from sRGB, ProPhoto, etc. to Rec2020.

I think my LUT pack does that, but probably inversely to your workflow.

Instead of going <from> ProPhoto <to> sRGB, my LUTS go <from> Unmanaged (sRGB) <to> ProPhoto (or whatever).

So it adds the profile information starting from square one, wherever that may be in the timeline color space.

I believe my LUTS are working correctly in 2020 space, but as the output, not as the input.

To "prove" this, I took a 4K HDR10 transport stream, flagged P3 color space, and opened it in a 32 bit linear project with no view transform; IOW perfectly flat.

I applied the P3DCI LUT, raised the whites a bit, and this is what I got.

If I apply the 2020 LUT, the results are pretty pleasing, too.

So, these LUTS can be looked at as a substitute for ACES and other color space profile tools, and it is expected they will start in an appropriate, non-managed space. And they give the impression of being quite accurate.

As far as going a second hop (ProPhoto->?->2020), it may not be necessary; transform just to one or the other. Let me stew on that for a while...

RogerS wrote on 3/25/2021, 9:25 PM

How are you in a Rec 2020 image space if there is no view transform? (I think you're still in an unmanaged sRGB-like space).

No view transform also takes you out of HDR mode, so I don't get what usage scenario this is for. Is it for avoiding ACES with SDR, or for color spaces where there aren't ACES IDTs?

In 32-bit full 1.0 without a view transform, colors look off (oversaturated and some shifted hues) when the LUT is applied to a ProPhoto still (either the chart or real picture). I rendered it as HDR 10 and it looks the same in the media player.

It looks good in 32-bit video mode:


I don't have any HDR 10 footage to test with.

Getting wide gamut photos accurately displayed in a wide gamut video color space (Rec 2020) was one scenario I was thinking of.

Musicvid wrote on 3/25/2021, 9:37 PM

Give me one of your true ProPhoto camera images and I'll try to show you. I'm looking through the other end of the telescope, again, and it seems to be working so far.

The LUT replaces the transform. The LUT is agnostic to the output space, I still believe.

 

 

RogerS wrote on 3/25/2021, 9:48 PM

Yes, I used the LUT in place of the transform.

Here's data for X-Rite colorcheckers ("From X-Rite L*a*b* D50 (formulations AFTER Nov. 2014)") to start with- it's good for troubleshooting. The 8-bit TIFFs should work or 16-bit if converted to PSDs.
https://www.babelcolor.com/colorchecker-2.htm#CCP2_images

If you also want a camera image here is one exported as a ProPhoto file, also excitingly of a chart : )
https://www.dropbox.com/s/nhyi2b32spm280h/Colorchecker-1.psd?dl=0

It's a 16-bit PSD. I can convert to another format if you prefer.

Last changed by RogerS on 3/25/2021, 10:03 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.239

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

Musicvid wrote on 3/26/2021, 11:19 AM

I guess I was insensitive by asking for one of your production images, and yet I certainly understand.

So now you are asking if the transforms made to a reverse engineered, 1080x768 8 bit Macbeth chart work the same with a ProPhoto LUT in Vegas as with a ProPhoto ICC in Photoshop?

Yes they do. With a calculated SSIM of .9965 (ffmpeg). The pre-emptive condition being, of course, that the Vegas testing will be undertaken in the correct project and pixel formats (previously discussed to death...).

Adobe works. ProPhoto works. P3 cinema appears to work. Confidence is high. Feel free to share other use cases in Vegas.

Fun stuff!

RogerS wrote on 3/26/2021, 10:26 PM

I'm not trying to be ungrateful but can you expand upon when it works and under what test conditions? What exactly did you do? This is not 32-bit full mode, I take it?

For correct project and pixel formats I have found LUTs only work accurately with 8-bit full, video or 32-bit video. If it's user error, please describe the conditions upon which it will work.

I gave a link to ProPhoto synthetic/engineered files as they very much demonstrate what happens when you put a non-color managed ProPhoto file into Vegas. You don't need extended color gamut image data to see the difference (and don't have the variable of colormetric intents for converting out of gamut colors). The nice thing about charts is you can clearly see when things go awry.

I also supplied a file directly from the a camera I use for photography with a chart. It originated as a 14-bit raw and then white balanced and exported as a 16-bit ProPhoto PSD. If the LUT/Vegas can pass this test it can pass a test with any other image.

The problem with starting with a real-world image is that if you don't know what it is supposed to look like it may appear acceptable upon casual viewing. (Based on the chart in 32-bit full blue and red/magenta are the biggest problem areas so I'd have to make sure the image has such tones. Happy to supply that next.)

Musicvid wrote on 3/27/2021, 8:21 AM

What exactly did you do?

Sure. I am a beginner at this, so I don't understand the rest of your question.

  • Take an image with embedded profile information (Adobe RGB or ProPhoto). Open it in Vegas, taking special care to match all project settings and pixel formats exactly to the source. Turn View Transform off if active. Note that it looks different in Vegas than in Photoshop. If they look the same, get a different file.
  • Now, add the LUT conversion in Vegas fx or Grading panel. Choose the corresponding profile (Adobe RGB or ProPhoto). After a short lag, the preview should change and the previews should now match. ≥ 99.5%

Errata:

Did you know that changing the project pixel format from the source often changes the gamma internally and adds shadow frequency noise, making any test results useless?

 

 

 

Musicvid wrote on 4/7/2021, 11:50 PM

Updated to include Canon EOS and Panasonic Color Grading LUTS.

Rich Parry wrote on 4/14/2021, 6:51 PM

Musicvid,

I think I am missing how to properly use your LUTs. For 15+ years I have shot raw still images, post processed in Adobe ACR (LR), and saved in AdobeRGB1998 as JPEGs. I import the stills into VP18 to create a slideshow and have been happy with the results.

After reading your post, I thought I might benefit by adding your AdobeRGB1998 LUT to the JPEGs to enhance the image, but when I did, in most cases all it did was over saturate the image, the images looked worse.

QUESTION: Am I using the LUT incorrectly?

Thanks in advance,

Rich

CPU Intel i9-13900K Raptor Lake

Heat Sink Noctua  NH-D15 chromas, Black

MB ASUS ProArt Z790 Creator WiFi

OS Drive Samsung 990 PRO  NVME M.2 SSD 1TB

Data Drive Samsung 870 EVO SATA 4TB

Backup Drive Samsung 870 EVO SATA 4TB

RAM Corsair Vengeance DDR5 64GB

GPU ASUS NVDIA GeForce GTX 1080 Ti

Case Fractal Torrent Black E-ATX

PSU Corsair HX1000i 80 Plus Platinum

OS MicroSoft Windows 11 Pro

Rich in San Diego, CA

Musicvid wrote on 4/14/2021, 9:35 PM

Hey, Rich.

Can you send me a couple of AdobeRGB JPGs to play with?

Sent you a PM with my email.

john_dennis wrote on 4/14/2021, 11:39 PM

I sent you a pair. RAW and JPG Adobe RGB. Check your messages for the link.

RogerS wrote on 4/15/2021, 8:20 PM

@john_dennis ACES with the view transform to sRGB looks strange. How is it with view transform set to off?

Musicvid wrote on 4/15/2021, 9:21 PM

@john_dennis What camera and model did you shoot the RAW .arw with?

The AdobeRGB LUT is working just fine.