As you can see form these 2 clips, all identical settings in VP17 & VP18 (32bit float full range) same rendering method/settings, basically everything the same, except for the final output. Just a simple black background from media generator and simple text.
VP17 (Expected)
VP18 (Not Expected)
Gonna have to go back to VP 17 until this can be rectified.
Set your VP18 project properties to legacy 8 bit video levels.
Here`s a comparison if the files using MediaInfo program. Saved to text and compared with Beyond Compare. Not sure if its any help, but here it is anyway.
The only major difference is the colour range tag being added in VP18
Thing is it looks fine in the preview here, just the rendered result is not expected. I`m no expert and certainly not a pro, but something is not right somewhere.
Nothing's wrong, nothing's odd. Exactly the way expected. You may have missed this info about a new option of the Vegas Pro 18 project properties.
Well according to the new 8 bit Full Range setting Vegas Should “know” that media/text generation uses limited levels and thus should be “left alone”. It looks like in marks generation of text Vegas is automatically and incorrectly applying a “computer to studio levels fix” (if mark added a studio to computer levels fix the text would show identical to Vegas 17.
mark are using a Vegas 17 project file for vegas 18? that could be the source of the problem.
"From what he said he didn’t, so neither did I."
Can't repro. Everything's like it is meant to be. Mark's results are to be expected.
"It looks like in marks generation of text Vegas is automatically and incorrectly applying a “computer to studio levels fix”."
Everything's correct. Vegas Pro's internal generated media are based on computer levels and that 8 bit full level option is meant to conform all imported media to computer levels, too.
Now standard export option (which is switchable) for 8 bit full level projects is a "limited" color range meta data, thus output must be transformed from computer levels to video levels. This is correct processing.
mark are using a Vegas 17 project file for vegas 18? that could be the source of the problem.
Yes I made sure, v18 opened as is and had to open v17 with "open with vp17"
After so many years of using Vegas Pro, were all gonna have to to short test renders before hand, to make sure were getting what we see in the preview window.
It looks like in marks generation of text Vegas is automatically and incorrectly applying a “computer to studio levels fix” (if mark added a studio to computer levels fix the text would show identical to Vegas 17.
@LongIslander - Ahah!
mark are using a Vegas 17 project file for vegas 18? that could be the source of the problem.
@LongIslander - Yes, I did. I did this to keep things the same! Well, there you have it.
Which render template did you use in VP18 to output that video?
Magix AVC/AAC MP4 Internet UHD 2160p 25 fps (NVIDIA NVENC) but custom, all I changed was colour range to full in project settings. Just done another test in 32bit float full range and changed colour range back to limited default (basically back to default preset) and it rendered as it should? maybe that`s where I went wrong? feel silly now! lol
"all I changed was colour range to full in project settings."
Of which project? The source project of VP18 before you rendered the project?
I'm a bit confused because you said you used a float point project as a base. But in a float point project there is no color range project property setting.
Or didn't you mean the project setting, but the render setting (and the project tab of the render settings)?
After so many years of using Vegas Pro, were all gonna have to to short test renders before hand, to make sure were getting what we see in the preview window.
@_Mark_ - Is believing what we’re seeing? Use of scopes gets me through the Night.
That was the problems, the scopes didn't show any difference in either of the pixel formats, it was only in the rendered version, but may have been might fault see post above, thanks for all the help! :-)
"all I changed was colour range to full in project settings."
Of which project? The source project of VP18 before you rendered the project?
I'm a bit confused because you said you used a float point project as a base. But in a float point project there is no color range project property setting.
Or didn't you mean the project setting, but the render setting (and the project tab of the render settings)?
Source project pixel format (was 32bit float full range)
render setting was set to full range in (Magix AVC/AAC MP4 Internet UHD 2160p 25 fps (NVIDIA NVENC)
"render setting was set to full range in"
Well, that made the logical difference. Again - the result is exactly what is to be expected.
The levels of your text sample video actually are not "full", so you should not use the "full" level meta data but limited levels instead.
Yes I realise that now, like I said above feel silly now! Many thanks for all your input ans help, sorry to waste valuable time.
No, stop. This is trickier because you used a float point project as base.