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

Lumetri causing pixelated preview and output

Engaged ,
Dec 10, 2016 Dec 10, 2016

Dear all,

I just used Lumetri color effects on a clip and am getting pixelated black blocks randomly flitting across the screen, in preview and after final output.  Is this a problem with Lumetri color wheel adjustment?  I like the color correction, but I don't like the pixelated results.  When I used the old Fast Color corrector wheel, the results were not as fine-tuned, but they were clean.  I have recently worked with many similar clips, exporting without problem, and Lumetri seems to be the only effect that is giving me problems.  I'm working with HD footage shot on a Nikon D-750 DSLR -- the blue sky was shifting a bit toward magenta, although I used auto white balance during filming.  While trying to adjust to the proper white balance with Lumetri, the pixelated problems occurred, but not always in the same place.  There isn't much real white in the video, so Lumetri just seemed to be the effect that worked the best, and I got good results from it, except for the pixelated black blocks -- disappointing.  Any solutions?  It can't be an export problem, because I'm also seeing it in preview.  Thanks.

3.2K
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
Guide ,
Dec 10, 2016 Dec 10, 2016

I have said it before. Premiere Pro is getting worse and worse. I don't know why they have to keep taking away filters and transitions. The Lumetri Effects takes a toll on the GPU as does the new Lumetri Scopes. 8 months ago you could have just used another CC effect  :  (

I have noticed some effects get funky with the GPU enabled but play OK in software only mode. Want proof? Check out the video link. This video proves Premiere Pro is the worst NLE ever created - YouTube

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 ,
Dec 10, 2016 Dec 10, 2016

Would appreciate say a screen shot of the pixelation issue. Not getting that here and it would be a good help.

What's your machine specs and GPU?

As a side note ... been a pro photographer 39 years  ... digital since 2001 ... and video some years now also. I can't think of a situation that I would recommend Auto WB ... and I've spent a bunch of time cleaning up other shooters work for them when Auto WB gave them odd color. I've seen mid-scene color shifts as bad as exposure shifts. Dang near impossible to grade out.

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
Engaged ,
Dec 11, 2016 Dec 11, 2016

Dear R. Neil Haugen,

Most of the time my auto white works just fine and I find it very useful in quick-shoot situations.  This scene was of a baby hawk on a tree limb between the main tree trunk and another large limb, and manual adjustment was a bit tricky, not to mention trying to set white balance and other details before the hawk decided to leave the scene.  There really wasn't a white balance problem, just a bit of over saturation of the sky, which was creating a bit of a blue cast.  Warming the scene up a bit eliminates the rather cold, blue cast.  I certainly do set the appropriate white balance when I can, but sometimes, when the sun peaks through the clouds, then leaves, then comes back, etc., I have had great results with my Nikon's auto-white. 

I'll try to get a screen shot and my other specs out soon.

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 ,
Dec 11, 2016 Dec 11, 2016

Thanks for the added comments. Very helpful. I'd definitely love to see a screen grab of or including the Lumetri RGB Parade and Vectorscope of this scene.

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
Engaged ,
Dec 11, 2016 Dec 11, 2016
LATEST

Dear R. Neil,

I see that spell checker changed 'peek through the clouds" to "peak through the clouds", but I think you get the idea.  I'm still experimenting with the file and will let you know what happens.

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
Participant ,
Dec 11, 2016 Dec 11, 2016

I have just been bitten by this problem.  I have 5 layers of video: a 4K wide shot from a GH4 and 3 6K HD files from RED DSMC2 cameras.  My top layer (V5), where Lumetri has been giving me all sorts of problems, is a duplicate of the top R3D clip (V4), but cropped and scaled so that it fills the frame, then overlayed with whatever amount of opacity that I call for.

It just so happens that what I'm cropping to is an LCD projection screen within the image.  When Lumetri is not giving me trouble, the full-screen image of the projection screen looks as expected: LCD colors and no visible pixels (because the pixel size is way smaller than the resolution of my lens).  When Lumetri is not behaving, one of two things happen: Colors are clamped to just one channel (usually green), and they are pixelated in a way that looks like I'm shooting not an LCD screen, but an old-school color monitor, with the kind of interference patterns you'd expect when one digital array is trying to image another.  Or, I get this:

------------------------------------------------------------

- Encoding Time: 00:00:08

12/10/2016 11:46:31 AM : Encoding Failed

------------------------------------------------------------

Export Error

Error compiling movie.

GPU Render Error

Unable to process frame.

Writing with exporter: QuickTime

Writing to file: /Volumes/6TB-A/CarlPalmer2016/21Cent Stereo_2.mov

Around timecode: 00:03:52:22

Rendering effect: AE.ADBE Lumetri

Rendering at offset: 117.167 seconds

Component: EffectFilter of type GPUVideoFilter

Selector: 9

Error code: -1609629695

The work-around I have found, which is pathetic, is to Render-And-Replace all my clips in V5.

I have a late-model 2012 Mac Pro with NVIDIA GeGorce GTX TITAN (6143 MB), 128 GB of RAM, and a RED Rocket-X card running OSX Sierra (latest version).  My disappointment with Premiere Pro continues into its fourth year.  I'm starting to feel like Charlie Brown.

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