For the Lumetri Color Effect’s curves controls (Hue vs Sat, Hue vs Hue, and Hue vs Luma), cyan is in the center, while red is on the far left and right sides. This is inconvenient, because most users will probably want to adjust skin tones more than anything else, and skin tones are almost always somewhere in the reds and yellows. Therefore, I propose that red be in the center by default, while cyan is on the edges.
NOTE: Because a horizontal scroll bar is already available, it is possible for the user to essentially do this themselves... but because skin tones are the most common thing I adjust, I find that I have to manually scroll that bar all the way to the left or right, 80% of the time I use these controls. So it would definitely be less hassle (for me) if red was already in the center.
There may be a good reason to have cyan in the middle, but I can't think of it.

ProRes RAW has been implemented inside of Premiere now but it is cumbersome. My workflow remains the same as before support has been added where I need to conform my footage to LOG inside of FCPX and then import that to Premiere. This makes all the work that went into implementing ProRes RAW into Premiere useless to me because I still have the same workflow as before.

I am suggesting taking an approach like FCPX where in the clip options there be a selector for “RAW to LOG Conversion” that allows you to conform the linear footage that ProRes RAW is into a more traditional LOG file.

This would make it exponentially easier to handle.

When adding Lumentri to a video clip and changing any setting in these tabs: Curve, Color Wheel & Match, HSL Secondary or Vignette there is a bad black and white noise band that is added. This happens on old and new projects. On old projects, if one of these tab settings is already changed, the bad is already on the footage. All renders have it on the video when exporting from both Premiere or Encoder.

Happens of both of my systems:

i7 5960x // Geforce GTX 1070 // 64gb Ram // Windows 10 Version 1909

and, HP Zbook, Xeon E3-1505M v6 // Quadro P5000// 64gb Ram // Windows 10 Version 1909

When working in Premier Pro color doesn't match the color of the same file in Quicktime Player. It seems that Premier is displaying rec709 color with 64 Black. With so many people now working at home without dedicated rec709 calibrated viewing monitors, and with so many people working on content that is not destined for rec709 broadcast, but will only play on the web, could we get an option for display on a computer monitor so color in Premier and Quicktime Player will match? Final Cut seems to allow this through Apple's ColorSync and Resolve has a rec709-A option that aims to address this issue. Files destined for the web all seem to match between quicktime player, Safari, Chrome (Youtube and other social and streaming platforms). With so much content destined for these platforms it would be extremely helpful to have a viewing option that allows viewing in Premier to match the color of the render in Quicktime Player. Thank you!

Resolve provides a color transform function with .idt (Input Device Type) preset for a large number of cameras. When used with ACES, I can apply an input device type for match my camera (v-LOG, s-LOG, f-LOG, REC 709, REC 2020 HLG, etc.). This brings my footage into as neutral a space as possible. I can then apply an output device type (ACES, or any number of cameras such as ARRI, Sony, RED, etc.).

Using Resolve's color transform and ACES color management I can quickly get my GH5 clips into a neutral space and then apply an output device type that gives my footage the look of virtually any camera I want.

My Premiere has been crashing on startup for a while, since some of the latest Premiere 2019 versions (not sure when it started). I was hoping it would be solved in v14, but nothing changed.

My Premiere crashes right before the timeline preview shows up, when I open a project with sequences and some footage already imported.

I noticed that it only crashes if the playback needle is on a footage with Lumetri applied, so I've done a few tests.

I've "solved" the issue by creating a dummy project, with a single sequence and an adjustment layer with Lumetri applied to it.
If I open this dummy project first and then open my working project, it does not crash. It seems like Lumetri crashes on startup and takes Premiere down with it.

Running Mac OSX 10.13.6 and Premiere v14.3.2