Hi all,
I probably lack some understanding here, but ever since Vegas implemented the 8bit video level setting, there was no more need to use the levels computer RGB to studio RGB filter before exporting.
But recently, when working with 10 footage in the 8bit video levels, and doing the final export at 32bit video level, not using the conversion results in fullrange exports, which in turn leads to excessive levels on the viewing screens.
Is this "normal"?
Thanks!
Sounds normal to me- 8-bit video and 32-bit video levels both need to be manually limited to studio range.
Is this "normal"?
I've never seen anything unexpected since the 8 bit full range option was offered, but we would need all of your source, project, and render data to answer this question.
Sounds normal to me- 8-bit video and 32-bit video levels both need to be manually limited to studio range.
I don't think that is so, that was one of the changes when 8bit video levels was introduced.I tested it thoroughly and remember asking that specific question to Marco here on the forum..That is why I was surprised the 32bit setting actually required level conversion.
Is this "normal"?
I've never seen anything unexpected since the 8 bit full range option was offered, but we would need all of your source, project, and render data to answer this question.
why? I specifically said that the problem only occurs within the same project, same footage and "render data", only the bit depth in the project changes before rendering. It has nothing to do with the footage, which is 10bit 422 full range.
from this thread:
https://www.vegascreativesoftware.info/us/forum/vp18-notes-on-the-8-bit-full-level-option--122749/?page=1
If you render a project with the project's pixel format set to 8 bit full level, by default Vegas Pro will apply a computer level to studio level transformation for the output file and automatically set the output file's color range meta data to "limited".
I used to edit in video range so I could easily switch between 8-bit and 32 and used SeMW so that renders in a viewer matched the Vegas preview. Problem was that uploads to YouTube changed. Apparently YouTube remaps uploads from video range to full range which alters brightness, contrast, and color.
So I've switched to editing in full range, which is now the Vegas default for its preview screen and projects. Now what I see on YouTube matches the Vegas preview. Only problem left is the render in a viewer. The Vegas render is video range by default and most viewers preserve the range. I tried rendering full range but that messed up YouTube... it apparently does the range conversion whether it needs it or not which wrecks a full range upload. My solution is to continue rendering in video range but to use mpc-hc (x64) with its Shaders, Active pre-resize shaders, set to use the 16-235 to 0-255 preset, which is effectively a video-to-full range view transform. So I can line up the Vegas preview, render viewed with mpc-hc, and YouTube theater-mode displays next to one another for a perfect match.
Keep in mind that Vegas is all messed up switching from 8-bit full to 32-bit full... Vegas turns on an sRGB view transform and changes the compositing gamma from 2.222 to 1.0. I find I need to restore those 2 things manually if I change modes after grading in 8-bit full.
why? I specifically said that the problem only occurs within the same project, same footage and "render data", only the bit depth in the project changes before rendering. It has nothing to do with the footage, which is 10bit 422 full range.
Because it can have everything to do with it, depending on your source, your 32 bit project properties settings, and the switch to 8 bit output. Thanks for sharing your source properties.
Sounds normal to me- 8-bit video and 32-bit video levels both need to be manually limited to studio range.
I don't think that is so, that was one of the changes when 8bit video levels was introduced.I tested it thoroughly and remember asking that specific question to Marco here on the forum..That is why I was surprised the 32bit setting actually required level conversion.
Is this "normal"?
I've never seen anything unexpected since the 8 bit full range option was offered, but we would need all of your source, project, and render data to answer this question.
why? I specifically said that the problem only occurs within the same project, same footage and "render data", only the bit depth in the project changes before rendering. It has nothing to do with the footage, which is 10bit 422 full range.
32-bit video range requires such a change and is equivalent to 8-bit video (legacy). Marco and I had a similar discussion.
If you are doing a 32-bit full project and want to match 8-bit full, set view transform to off and compositing gamma to 2.2.
Or if you want to use ACES, just apply the levels filter to return it to studio RGB before export. It is behaving as expected. VEGAS' 8 bit mode by default uses Studio RGB now, but 32 bit mode uses full range (hence the 32 bit full name).