Until recently (I'm on v13.1 at the moment), a user was able to roll the mouse wheel over the closed LUT drop down menu and cycle through different LUTs. These LUTs would be applied on the Lumetri layer, allowing for adjustment of intensity and interaction with other layers.

This option has recently disappeared. Once a user clicks a LUT in the drop down menu, that selection is moved to the top of the menu, causing "Browse..." to be the next LUT option when mouse scrolling.

Please see an example here: https://www.youtube.com/watch?v=Hi6DxcWCu2w

Yes, the preview window in the Lumetri>Creative panel allows cycling through LUTs, but it is at 100% intensity and without regard for other effects applied to the clip.

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!

The Lumetri Color plug-in currently does not support multiple clip selections. This is unfortunate as this forces us to use multiple adjustment layers instead of one.

Imagine we have footage from different cameras. Once all clips are laid out we could add one adjustment layer and cut it on each clip's boundary, then apply per-clip corrections (say, colors-space conversion depending on shooting mode or camera model) using the Basic Correction layer, then use the Creative layer to individually make them look uniform or whatever.

Then we'd multi-select the entire adjustment layer, now made of multiple segments aligned to the video clip boundaries, and apply Color Wheel, HSL and Vignette to all of then at once, resulting in a single segmented adjustment layer performing all three steps: the initial color space conversion, the individual adjustments, and the overall look, all with ease and on a single layer or no layer at all, acting directly on the video clips.

Does that make sense?

Enabling multi-selection requires a bit of work (like tri-state or gray-out the options that are not uniform across the entire selection) but the end result would be better as we'd do one transform instead of three, so less quantization noise I presume? At the very least it would be more convenient/faster to be able to set properties on multiple clips at once!

When new LUTs are added to the folders within Lumetri, it affects all clips within all projects that use LUTs, indicating that Adobe programs are referencing LUTs based off of a numbered list within the folder rather than the actual LUT files themselves. Eg I have a list of LUTs:

1. Orange LUT
2. Blue LUT
3. Green LUT
4. White LUT

I am using 2. Blue LUT on a clip. When I add a new LUT to the folder it looks like this:
1. Red LUT
2. Orange LUT
3. Blue LUT
4. Green LUT
5. White LUT

Now, my clip has changed to using Orange LUT. So Adobe didn't link my clip to Blue LUT, it linked it to #2 on the list, and if the list changes then so does every single clip using LUTs. Adobe Support Chat was useless and didn't even acknowledge it as a bug, which it clearly is.

Request: change LUT file referencing from a numerical list to the actual LUT file

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

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!

It would be great to be able to import Luts by folder (similar to the Essential Graphics panel) as well as creating folders within Premiere Pro and After Effects in order to organise previously imported Luts that way.
Ideally, this structure would integrate between Lumetri and the effects panel so that folders would reflect between the two panels.
Also, a way that Luts are independent of their order within any list or folder structure to avoid the current problem since Lumetri's launch to the date of this post, whereby importing new luts would offset previously used luts within a project.

Cheers

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 know Adobe envisions a world where people begin and end the post process entirely within Premiere, but in the real world, we have to send edits to outside colorists and VFX artists who dont work in Adobe-land. So it would be great if there was an option in the Lumetri Color effect to restrict the grading controls to a "CDL-compliant" mode, so that offline editors could do quick temp color grades in the offline (and preventing them from using non-CDL compliant options like Curves, Masks and Color Temp), and then have those settings able to be accurately transferred over to DaVinci Resolve (or other grading system or VFX tool, like Nuke) as a starting point for that artist.