HI all
so I'm exporting a new project ( 4k 10bit 422 from a Sony FX3 ) using Phantom LUTs in 32 bit.
Working in 8 bit full range looks good - 32 bit as a workflow is too slow, which is why I only change to 32bit for the render.
The thing is, in my exports, the blacks are crushed, but applying the levels plugin set to computer RGB to sdtudio RGB results in washed out images. No neither looks correct, and exporting in 8 bit produces too much banding.
What am I missing here?
Thanks!
8-bit full is visually the same as 32-bit full with view transform off. The levels plugin wouldn't be needed in that case. I assume you're working in VP 22. Make sure VEGAS is properly reading the levels metadata (right-click on media and look in properties. If it says undefined it doesn't know what to do with it so set it manually to full).
I think your other screenshot showed 32-bit video levels mode which requires manual levels changes.
Thanks, I'm in V21 still as 22 won't let me render without crashing.
Properties read full range as intended.I tried adjusting the levels plugin but couldn't fine tune it to pulling the blacks back up without affecting highs and mids. I'll then probably have to adjust the main out with either colorfast2 or the CG panel.
Something is wrong here, I'm not seeing issues with similar Sony footage (though I work in 21.208 and not newer builds).
Could you share screenshots of the project with waveform scopes and the same point in the rendered file brought back into VEGAS also with scopes?
Is this what you meant?
project in 8bit full .......................project in 32bit
reimported render in 8bit full ........reimported render in 32 bit
EDIT: I think you found the issue. I rechecked the properties and it actually does read "undefined". I now batch changed all the media to "full", but the issue persists. hings look fine in Vegas but there are crushed blacks in the render. I might have gotten things wrong on this issue for ages...I used to work and render in 8 bit full when not using LOG and LUTs, and there wysiwyg.
Could it be that Vegas gets confused with LOG footage, and that the LUT filter can't seem to define the color range?
Thanks for doing the test, we're getting somewhere. The undefined metadata is a known issue with 21.300+ (fixed in 22).
In scopes studio RGB is unchecked?
The first two clips look good- 8-bit full and 32-bit full (view transform off) are matching nicely. 32-bit full render looks similar. The 8-bit render has crushed blacks. Just to check you have compositing gamma set to 2.2 for 32-bit full to match 8 bit full?
Here's what happens with a LUT Fx if the gamma is set differently:
Thanks! As I work in 32bit video levels, gamma is greyed out and set to 2.2 by default.Yes studio RGB is unchecked.
I ended up using the color curves plugin to limit the black levels to slightly above zero, and that finally worked.
You can't work in both 32-bit video and 8-bit full and expect they'd look the same. You'd work in 32-bit full with view transform off.
Edit: alternatively you can work in 8-bit video and do the levels changes to full and back manually.
I guess I worded that wrong. I "work", meaning edit in 8 bit for preview speed, then switch to 32 video levels just for the export. In 8 bit, what I render looks like what I work with. In 32 video levels, I need to apply the levels limiter. I'm a bit slow sometimes, but I think I'm starting to get it...
I understand what you mean but not why you are continuing to choose mismatched project settings.
Try 8-bit video/32-bit video if you want to handle levels conversions by hand (full range footage and photos are WYSIWYG but anything in video levels needs to be converted to full to match the other footage).
Otherwise if you want VEGAS to do levels conversions, 8-bit full/32-bit full (with view transform off) will also match.
Yes, I get it now. My brain didn't quite compute for some reason.