Contrast change when copying clip to new project with same properties

hambonio wrote on 3/29/2024, 3:17 PM

I am having issues with different projects displaying my footage in different ways. I have ensured all project properties are 100% identical I have use the "Match Media Video Settings" to reference the exact same file to ensure the properties are the same.

All preference tabs that I can tell are also identical.

Scopes are all set the same.

In one project the footage is showing with a little more contrast and saturation than the other. One clip even appears to be a bit warmer than the other but I am pretty sure it is just due to the base contrast/saturation.

There are no Track level FX applied or project wide FX applied. I have noticed this with a few projects lately. I am not sure if there is a setting anywhere else I am missing that one project might have that the other is missing.

In my samples below the Pixel format is "32-bit (full range)" but even if I switch the project to "8-bit (full range)" the problem still exists and looks exactly the same.

I have examples of direct footage with FX Bypassed and also with FX Enabled. For the FX enabled clips I have tried copying the clip directly from one project to the other and also natively adding the clip to the new project and pasting the event attributes.

The ONLY difference between these projects are the PCs they originated on. The original started on an Intel system, the new projects initiated on an AMD system. But both of these projects are opened on an AMD system and screenshots are from the same system and should be 100% identical.

If anyone knows what is going on here I would appreciate the help! I would even be willing to share 2 separate projects with a same reference video if that might help. This is hurting my process as I have 4 VP21 licenses and edit on multiple machines and project consistency is not there and is a huge deal.

As I said I am unsure if the originating PCs have anything to do with it or what can be fixed, as everything in the projects should be identical anyway. This is the only variable I can think of.

PC these screenshots came from:

VP 21 (Build 208) - Also same version on Intel PC

AMD R9 7950x (Originating PC i9-14900k)

RTX 4090 (Originating PC RTX 3070)

96GB RAM (Originating PC 64GB RAM)

Comments

hambonio wrote on 3/29/2024, 4:27 PM

Thank you! This might be it. But intentionally trying to force this duplication with multiple clips just now, it seems inconsistent. Sometimes it loads as undefined and other times it seems to be loading as full. Why is this not copying correctly in the first place? And it also seems like a clip per clip basis. 100s of clips to go through and try to fix now..... Is there a way to make all of them show as full? I have a LOT of work in front of me.

john_dennis wrote on 3/29/2024, 4:48 PM

Tell us:

  • Vegas version of the source project.
  • Vegas version of the destination project.
hambonio wrote on 3/30/2024, 10:27 AM

Tell us:

  • Vegas version of the source project.
  • Vegas version of the destination project.

Both version are current 208

mark-y wrote on 3/30/2024, 11:27 AM

Your media color space is probably set differently in the two projects. Right-click on the media in Project Media and click Properties.

hambonio wrote on 3/30/2024, 11:32 AM

Your media color space is probably set differently in the two projects. Right-click on the media in Project Media and click Properties.

Thanks, That is what was suggested above. New issue is this seems to be inconsistent on a clip per clip basis. Some are copying over as full range as expected - and others are copying over as undefined which seems to be more of a defaulted limited color space.

mark-y wrote on 3/30/2024, 11:41 AM

Some 10 bit media types don't automatically register their color space when opened in Vegas. If they are left at Default, they will not interact properly with the transforms in Project Properties.