Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Premiere 2017 (April 2017) BUG - Random BLACK LEVEL changes - SUCK

Community Beginner ,
Sep 05, 2017 Sep 05, 2017

I have been using Adobe Premiere 2017 released late last year (working great). After completing (so I thought) my major project, I UPDATED to the April 2017 release. Certainly the Sequence of my previous show is revised. However upon playing back the video, randomly on various scenes the BLACK LEVEL is +30 on some shots. The SHADOW LEVEL in also higher. What the hell? There is no consistent relationship I know between all the shots which have been changed. I mean a lot of them. I had to readjust the video levels to at least 40 different shots.

Has Anyone experienced this other than me?? Otherwise the update/upgrade was smooth. I am VERY detailed when it comes to proper levels, and my show was all messed up.

Eric M Manuel
605
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Sep 05, 2017 Sep 05, 2017

First, if you were on the 2015.3/4 builds, that's a completely different build series than the 2017 builds ... and there can be issues. If you're done with that project, I perhaps would suggest having the version it was "built" in still installed on your machine for working any additional things with that project unless for some reason you have to have it in the newer build.

Second, there were some things especially with some Lumetri settings & some LUTs that went screwy when migrating projects from 2015.3/4 into 2017. Mostly fixed by turning them "off", then on again in 2017.

So ... the clips that are wrong, are there LUTs/Looks and/or Lumetri applied there?

Neil

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Sep 05, 2017 Sep 05, 2017

Actually, it was the 2017.02 Adobe Premiere release I had been using.  Thought I was finished with the project (because upgrading during a project is a NO NO.  After the project, I did the upgrade.  

Later, it was brought to my attention, I had of all things, a spelling error on a lower third.  Opening up the previous sequence I made the change, (easy to do), however noticed all kind of video level problems.

Flat blacks with a +30 value higher than normal. 

Shadow levels higher

totally random best I can understand.

Took hours and shot by shot to fix stuff already completed.   Can you say screwed in the ass???

Eric M Manuel
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Sep 05, 2017 Sep 05, 2017

Did you try downloading the 2017.02 Premiere version from the Previous Versions panel? That would've been faster than readjusting everything.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Sep 05, 2017 Sep 05, 2017

Actually, it was the 2017.02 Adobe Premiere release I had been using.  Thought I was finished with the project (because upgrading during a project is a NO NO.  After the project, I did the upgrade. 

Later, it was brought to my attention, I had of all things, a spelling error on a lower third.  Opening up the previous sequence I made the change, (easy to do), however noticed all kind of video level problems.

Flat blacks with a +30 value higher than normal.

Shadow levels higher

totally random best I can understand.

Took hours and shot by shot to fix stuff already completed.   Can you say screwed in the ***???

Eric M Manuel
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Sep 05, 2017 Sep 05, 2017
LATEST

Understood ... and ... ouch.

Neil

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Sep 05, 2017 Sep 05, 2017

Did you simply open your 2015 project in 2017 or did you start a new project in 2017 and import your 2015 project? If you haven't done the latter, give that a try.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines