Skip navigation
Navarro Parker
Navarro Parker
Currently Being Moderated

32bpc glitches disappear in 16bpc

Sep 28, 2009 1:07 PM

Okay guys.  Any ideas on this one?

 

When the project is in 32bpc, I get weird black blocks on my comp.  I turn to 16bpc, and the problem disappears.  And it happens all throughout my comp. Uuuuh, any ideas? Got me stumped!

 

Picture 8.JPG

Picture 9.JPG

2054 Views   12 Replies   Latest reply: fnordware, May 1, 2012 8:50 AM
 
Replies
  • TimeRemapper
    Currently Being Moderated
    1. TimeRemapper,
    Sep 28, 2009 1:18 PM   in reply to Navarro Parker
    Report

    Hey Navarro.

    Where's the source from? Is it 32bpc footage?

     
    |
    Mark as:
  • Navarro Parker
    Currently Being Moderated
    2. Navarro Parker,
    Sep 28, 2009 1:37 PM   in reply to TimeRemapper
    Report

    Yes, they are 32bpc EXRs. All my effects are 32bpc capable.

     

    Using HD Rec 709 color calibration with Linear Blending. I can't figure out any logical reason what's causing this.

     
    |
    Mark as:
  • TimeRemapper
    Currently Being Moderated
    3. TimeRemapper,
    Sep 28, 2009 1:42 PM   in reply to Navarro Parker
    Report

    Just a shot in the dark, but are you embedding any additional channel info in your EXR sequences?

     
    |
    Mark as:
  • Adolfo Rozenfeld
    Currently Being Moderated
    4. Adolfo Rozenfeld,
    Sep 28, 2009 2:52 PM   in reply to TimeRemapper
    Report

    If you disable View > Use Display Color Management (or enable it if it it was off), does it go away?

     
    |
    Mark as:
  • Navarro Parker
    Currently Being Moderated
    5. Navarro Parker,
    Sep 28, 2009 5:58 PM   in reply to TimeRemapper
    Report

    That's a good stab at it. But no, not extra channels. No alpha channels even.  These are flat EXR's (the only kind Cinema 4D can write).

     
    |
    Mark as:
  • Navarro Parker
    Currently Being Moderated
    6. Navarro Parker,
    Sep 28, 2009 6:04 PM   in reply to Adolfo Rozenfeld
    Report

    Another good idea!  I'll try that in the morning. (Machine is busy now)

     
    |
    Mark as:
  • Mylenium
    Currently Being Moderated
    7. Mylenium,
    Sep 28, 2009 11:13 PM   in reply to Navarro Parker
    Report

    Low on memory? OpenGL? Could also be either of those.

     

    Mylenium

     
    |
    Mark as:
  • Navarro Parker
    Currently Being Moderated
    8. Navarro Parker,
    Sep 29, 2009 8:11 AM   in reply to Adolfo Rozenfeld
    Report

    Okay, I tried turning off color management. No difference.

     
    |
    Mark as:
  • Navarro Parker
    Currently Being Moderated
    9. Navarro Parker,
    Sep 29, 2009 8:21 AM   in reply to Mylenium
    Report

    It's not an OpenGL problem, because it shows up in my final render (and I never use OpenGL rendering).

     

    Memory could be a possibility. But I have multiprocessing turned off and the max amount of RAM devoted to AE.  It's around 60 32bpc layers with six Adjustment Layers. At 2K, that's going to gobble up a lot of memory (plus effects).

     

    Each 32-bit 2K layer is 35MB x 60 = 2.1GB. Plus whatever internal precomp AE has to make for Adjustment Layers. Plus whatever memory is needed for plug-ins at 32bpc.  Hmmmm....  that doesn't look good, memory-wise.

     

    Any ideas how to solve a low memory problem? Anyone got a copy of Nuke they want to loan me?

     
    |
    Mark as:
  • Mylenium
    Currently Being Moderated
    10. Mylenium,
    Sep 29, 2009 10:52 AM   in reply to Navarro Parker
    Report

    Actually, there's one thing I could thingk of: You have a non-32bpc effect somewhere inbetween. Native 32bpc effects use something called SmartFX, which is a tiled rendering algorithm for better memory efficiency. Effects not optimized to that standard might break rthe rendering order, as they are impossible to render in tiles, which in turn may lead to the odd memory problem where certain tiles of successive effects have no data to operate on.

     

    Mylenium

     
    |
    Mark as:
  • thisismyspam
    Currently Being Moderated
    11. thisismyspam,
    Feb 1, 2012 9:24 AM   in reply to Navarro Parker
    Report

    i have the exact same issue with my comp now. i tried every trick i know but it just wont go away.

    interestingly it is the same area of the image as with your example.

     

    i could however narrow it down to one layer. which when disabled led to a normal render. but without that layer it was impossible for me to use that render. so i tried to "bake" things down.  didnt help either because i coudlnt manage to render that one comp without it glitching away.  i even tried to render that layer out again from max. with a different file format (tif, open exr, tga, png, bmp) nothing resolved the issue.

    i also disabled every effect... didnt help.

    i have a 8 core i7 with 16 gig ram.  i tried to disable multicore and rendered on one  core it still did happen. and my comp is only 720p. my ram doesnt even fill up completely (12 gig assigned to afx)

     

    the interesting thing is. the error happens always on the same frames for one session/layer mix. if i disable or enable another layer it switches place (hops to another frame).

    anyone got an answer to this?

     
    |
    Mark as:
  • fnordware
    Currently Being Moderated
    12. fnordware,
    May 1, 2012 8:50 AM   in reply to thisismyspam
    Report

    I wonder if you could have a NaN pixel in there. If you had a big blur or something, that could create that block, and it would go away in 16-bit mode. Read about NaN's (and a solution) here:

     

    http://fnordware.blogspot.com/2011/04/nanny.html

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points