Copy link to clipboard
Copied
I open the image on the computer and it look normal but when i imported it to premiere pro it looks like this. The image was edited with lightroom so i have no idea what the problem is.
Copy link to clipboard
Copied
What settings did you apply to export from Lightroom? That looks like there are saturation issues.
Oh, and what does the Lumetri scopes panel Vectorscope YUV show?
Neil
Copy link to clipboard
Copied
This are the setting I use.
And the vectorscopes look like this.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
The Vectorscopes are showing way out of bounds saturation. So the image is what I would expect given that saturation levels.
The question is ... is Premiere really screwing up or is it elsewhere?
Any way you could upload one of those images for us here to check on our own rigs?
Neil
Copy link to clipboard
Copied
Yes you can download it here : https://mega.nz/#!NdtUzKZT!8MYqIWKxOswoyiS9mgwV4SGcyF3H-yd0Gg7jHqvzER4
Copy link to clipboard
Copied
This is how it appeared in my system ...
Look at the Vectorscope YUV in the upper left corner ... it isn't showing anything out too close or over that thin line that makes sort of a hexagonal shape in the scope. That hexagonal line is the boundary ... anything crossing that line is outside the correctly reproducible colors of the Rec.709 color space. That is of course if the scopes are set to Rec.709.
Which is easy to check ... right-click inside the scopes panel, Color Space ... 709 should be set as the active color space.
So ... if your scopes are set to Rec.709, and your monitor is set to Rec.709 ... I'm puzzled as to what is happening on your screen. Are you on a Mac or Pc? Desktop or laptop?
Neil
Copy link to clipboard
Copied
I already have both color spaces to 709 and mine vectorscopes dont look like yours. I recently change my pc to a better one, on the old one it worked well but on the new one I have this problem. I have an Samsung LU32R590CWUXEN 31,5" monitor and a Radeon power color RX 5700 XT 8GB with a AMD ryzen 7 2700
Copy link to clipboard
Copied
I'm wondering if there's a Master Clip effect applied ... in the ECP, the Effects Control Panel. Click on the clip in the sequece so it's selected, then click on the Master Clip tab to the left at the top of the ECP.
See if it lists anything. In my example, the clip is a RED clip, so it's showing the RED media master clip options.
Neil
Copy link to clipboard
Copied
Might be a graphics card issue.
Copy link to clipboard
Copied
I dont think so, there is a new graphic card and on the desktop and in lightroom i see it perfect
Copy link to clipboard
Copied
No, i hadn´t aply any effects to the Master clip
Copy link to clipboard
Copied
Premiere is not Lightroom.
Make sure it has the latest driver from the Manufacturer.
Copy link to clipboard
Copied
I have latest drivers for the card but i find a solution what i want to now is if i do this it will slow the editing? i change from speed up for GPU (openCL) to only sofware and now it works well but will it slow down the funcionalities?
Copy link to clipboard
Copied
If its works in MPE software mode it means there is an issue with the driver.
Copy link to clipboard
Copied
Using software only in the Project settings Mercury Acceleration options may slow processing down, but if it is the only way to get the work done right, well ... for the moment, that's what you may have to do.
I know that especially for Resolve at the moment, many users in R16.x can't use the latest Nvidia driver as it's "broken" in Resolve. That can happen in Premiere also, sometimes the latest driver is the issue, and we need to roll back a driver.
Neil
Copy link to clipboard
Copied
OP should try driver 431.86 https://www.nvidia.com/Download/driverResults.aspx/151052/en-us
Copy link to clipboard
Copied
Nvidia newest studio driver is 441.66
Copy link to clipboard
Copied
Yes, I am encouraging OP not to use the latest version.
Copy link to clipboard
Copied
The new driver is an issue for a number of Resolve users also. So many R users are also suggesting reverting to the same driver that jP mentions.
Neil