Anonymous

My feedback

  1. 15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Premiere Pro » Color/Lumetri  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    @Francis - thank you for the response; I'm sorry for my late response to yours! :)

    1) No slider values changed, nor were there any LUTs added. Simply a Lumetri plug in that is native to PPro. Never installed any LUTs ever to my computer. The odd thing is that I had completed the project a week prior in CC2018. The following week, I upgraded to 2019 and was then asked to modify the existing project. Simply opening the project in 2019 caused this shift.

    2) I've experienced the issue with both the RGB Curves(Stand alone effect) and Lumetri RGB Curves (haven't had as much an issue with Hue vs. Saturation). Initially, the effect acts as normal. But once you release the mouse and the curve point is set, it will not allow you to go back and adjust that curve point. I've had to either delete and reapply (stand-alone effect) or reset (Lumetri RGB curves) in order to adjust and change them.

    3) I would get the low-level exception simply by trying to apply the Lumetri effect to a clip of video. Video is 1920x1080 Apple Pro Res 422, 29.97 Linear PCM, imported from a Ninja Blade drive and originally recorded via a Canon C100. It seemed to be an issue across all footage, but not necessarily all Lumetri pre-set choices. Ex: Lumetri>Speedlocks>Canon C300> SL Neutral Start would give me the exception, but Lumetri>Speedlocks>Canon C300> Clean Punch LDL would not.

    Does that make sense? Happy to help fix this!

    An error occurred while saving the comment
    Anonymous commented  · 

    Agreed! In this case, the project was complete and the client came back a week or so later (I'd literally upgraded the day before) and asked for a simple revision that included a new tag. I couldn't get anything to correct, so since the project was time sensitive, I imported the completed version back in, and used that to edit from, but I've seen this happen to some of my other projects trying to use the presets.

    Anonymous shared this idea  · 
  2. 11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Premiere Pro » Color/Lumetri  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  3. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Premiere Pro » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  4. 33 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Premiere Pro » Color/Lumetri  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  5. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Premiere Pro » Color/Lumetri  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 

Feedback and Knowledge Base