You have added Lumeri, it looks like ACR, but why does it not work properly?
Yesterday I made one video after a long time of absence in the premier pro and decided to test how this relatively new tool works.
well, it works disgustingly.
I had a video of a landscape which contained shadows and the sky. when I tried to draw out the shadows, it would take the sky mid tones, why? ..
I threw this video into Photoshop to do the exact same actions, and I got what I wanted from these pens very quickly, because the shadows touched only shadows, light only lights, etc.
when I tried to lower contast also, it made a strange effect harder than in ACR. too harsh.
etc.
if this is some kind of new "view" of colorfilters, can you just add ACR as a filter?
because it really saves time and works as you would expect from it.

Screen flicker when using Lumetri in Adobe Premiere.

I noticed it was only happening when I had the Lumetri SCOPES panel open and made adjustments on Lumetri, but goes as away when I close it. Is this common?

My GPU drivers are up to date and games, 3D programs work fine.

I notice the flicker only occurs when I use the Lumetri Scopes on my native display resolution of 3000×2000. If I go down to 1080p display, or even close the Scopes panel, there is no flicker. So I think that may be the issue. Which works as a fine fix for me, but I wanted to be sure.

Attached is a video and screenshot of the flicker. You can even see that the flicker is actually the same color(s) as the Scopes panel. Which lead me to believe that was the issue.
I believe the scopes panel displays so much color data in it that when displayed at a high resolution like around 4k, it causes that flicker. On my card at least. I wanted to see if this was common, seeing that many people edit on 4k displays today as it is. Thanks!

Just moved to a new computer, and while the new computer has all the same LUTs on it, the project is not applying them and is not even notifies about missing LUTs. Currently, the only way to make it apply the relevant LUTs is to go shot by shot and re-apply the LUTs for each shot separately. On a long narrative project, this "solution" is completely impractical. Either make Premiere notice that it's missing LUTs and add a re-link function similar to re-link footage.

*(and/or better yet, embed in the project file the LUTs that have been used in the project).

There's something weird going on with colour correction. The Lumetri scopes are proving to be problematic, but I'm also seeing issues with Comparison View. Basically both are hanging the program.

For example: When I go and enable Comparison Video, the Program Monitor doesn't redraw properly, and then the program is rendered useless (it's hung), and I have to End Task via Task Manager.

Pretty much the same story with scopes, except that the scopes don't even draw onto the screen at all. The bounding dialog box shows, but it's either gray, or just shows what used to be there behind it. Again, I have to End Task to get the program to reopen.

I have reinstalled, and also trashed preferences. No luck in either direction.

Premiere 13.1.2
Windows 10 Pro (1809)
i9-9900X
RTX 2070 (430.86)
64GB RAM

The idea is to help speed up the process of colour correction. Colour footage link is the idea to alter a shot in the timeline with the ability to duplicate the alterations to shots under the same file which may be used further along in the timeline. For example if I use shot A and then cut to shot B&C and then go back to Shot A instead of copying and pasting the setting I can select from the start for shots under the same file to be altered. This also means unless unselected that shotd which get altered as I continue to procress will alter at any point helping for all shots to match.

I think it would be awesome to have a better structure for LUTs. I wish it were more organized with the option of having folders. Lightroom has something similar to where you can have folders holding presets, but when I want to use a LUT in Premiere Pro, I have to pick through the long list I have aquired, or go through the browse option and go through those folders one by one. I would like to have that organization that I use in Finder (osx) within Lumetri. I've loved some of the additions to cc2019 and think this could be a nice feature as well.

I would love to have the ability to slide the low and high values of the HSL secondary key independently of each other, rather than having the slider be centered/mirrored whenever you adjust something.

For example, if you currently adjust the dark end of the Luminance slider, the bright end is also adjusted. This makes no sense. I want to adjust the dark side, not the bright side. In order to ONLY adjust the dark side, I would need to bring the dark end half way to where I want it to be (which also brings over the bright end), then shift the whole thing the rest of the way so the bright end stays where it was originally. So many steps just to keep things where they are and only adjust the thing you want.

Try it yourself right now, try to JUST select only the shadows in the HSL secondaries. Instead of just bringing the high end down to the shadow area you desire, you'll have to bring both the high and low values to the center, then shift the whole thing over. 2 steps instead of one. People don't think in this way, this dual/mirrored method of parameter adjustments. I want to adjust one parameter at a time and have it not change when I adjust another parameter.

Perhaps you can add the ability to hold alt/option and drag an end individually?

Just bought an iMac Pro to find out Premiere doesn't export correct color after grade. Massive desaturation & contrast lost after export. I've uninstalled and reinstalled, This is not the "quicktime" problem most of these complaints are chalked up to, and it is not a "mac" problem most write it off as. My previous iMac this was not an issue, now it has become a work stopping problem that has me wondering if i should throw in the towel and switch to Final Cut. Do you plan to fix this problem with an update soon? (late 2017 iMac Pro base model, Latest updated Premiere pro)

Reproducable bug in the latest version of PR (v13.1.2 @the time of writing).
Here's an annoying one:
1) Turn on the "Comparison View" in horizontal or vertical split mode (side-by-side seems to be unaffected)
2) In the Lumetri panel try to use ANY of the color pickers (i.e. the WB Selector in "Basic Correction" tab, ANY of the pickers in the "Curves" tab or ANY of the pickers in the "HSL Secondary" section – it doesn't matter, "pick" your poison really [pun intended])
3) Watch PR crash hard

Reproducable on OSX (AMD) and WIN10 (RTX2080)
Anyone else joining the party?

Please fix this! TIA!

In addition to my very old and ignored post about how Lumeti shifts colors dramatically, I discovered today that Lumetri also destroys details in footage. This might be related to the fact that it throws certain colors all over the place.

See attached video, especially the end where I zoom in. The clip used is a 10 bit 4k file from a Panasonic GH5. And yes I do an extra severe edit for demonstration purposes.

Lumetri Curves adds loads of noise, as well as looses loads of detail. While the old RGB Curves keeps all details crisp, does not add noise, and does not shift colors.

LUMETRI IS A JOKE. I seem forced to switch to DaVinci Resolve as as Adobe does not know what color is anymore.

The past 2 iterations of PPCC have been a disaster when attempting to use Lumetri color. When scrubbing through clips with Lumetri applied, sometimes the color will shift (in the monitor) to a completely desaturated (log-like) image ... even though my original footage was not shot in log.

When scrubbing back across, sometimes the color shifts back to the proper corrected look, but other times I simply have to toggle the fx lumetri effect on/ off to get it to return to normal.

The absolute worst part of this, is that during exports, sometimes PP will manifest that same glitch by EXPORTING a clip in the washed out look. Considering some of my projects are 6-10 minutes long, and sometimes it's just an individual random clip, this is infuriating.

I work with a couple of LUTs and use a home and work computer. I have the same LUTs I need on both computers but I have more LUTs on my home computer. The problem is I will use a LUT at work and even though I have the same LUT at home when I open the project at home it applies a different LUT to the shots I have already colored. For example, lets say I have a LUT named "Color" and it is the first LUT listed in my lumetri list. When I open the project at home Lumetri will apply the LUT that is first on the list regardless if it is "Color" or not. So I have to go back in and reapply the correct LUT to each shot.

What I am suggesting is that Lumetri tries to locate the exact name and apply said LUT rather than going on position. Obviously if the same name does not exist, it should have a default.

I have the Lumetri panel always open in a group of tabs, but it's not the panel that's shown/active (usually it's the Effect Controls Panel).

Often I'll need to tweak color using Lumetri for a slight exposure boost or white balance shift, so I click the Lumetri tab, make the edit, then click back to Effect Controls tab showing on top of that panel group.

But this still leaves the Selection Follows Playhead on and I have to go disable it every time.

The best would be a preference for this behavior - whether it's auto-enabled by Lumetri's activation or not.

This is a very odd problem and I can't figure it out. The Lumetri Scope panel won't display color information for some jpgs. The panel works for some jpgs and for others it doesn't. The jpgs are all in the sRGB color space. The ones that PPro can't process are larger files (it can seemingly handle smaller ones) but it's not a lag issue because no matter how long I leave the cursor on the pictures the Lumetri Panel never displays color information. It's as if I've got the cursor over an empty timeline.

If I go into Project Settings and turn off the GPU the RGB waveform and vectorscopes WILL display the color information in the Lumetri Panel. But turning GPU off and on isn't a long-term solution, I don't think. Help?

I'm running the latest version of Premiere Pro CC. My drivers are updated. Windows 10. Quaddro P4000 card.

I've attached a movie file to illustrate the issue.

I posted about this in the Facebook "Moving to Adobe Premiere Pro" group. Another PPro user was having the same issue. Link here: https://www.facebook.com/groups/premierepro/permalink/2268992836511765/

Then another PPro user posted about the same issue today: https://www.facebook.com/groups/premierepro/permalink/2272207486190300/?comment_tracking=%7B%22tn%22%3A%22O%22%7D