Brightness, Gamma, Blacklevel on 4444's from DaVinci?

Hi, Guys!
I graded a sequence in DaVinci Resolve 9. As a client-monitor I use a panasonic plasma connected to the BlackMagic DeckLink card in my MacPro.
I do know that it's not a calibrated monitor, but what I see is a relative problem rather than a absolute one.
I render the sequence in Resolve to a series of ProRes4444 files, export an XML and import the whole shabang into FCPX. I rendered at "Unscaled Full Range Data", because I don't need to be TV safe.
When I look at the footage in FCPX the blacks are at 0% on FCP's internal Waveform as opposed to below that and the whites are a good deal lower than 110% where they start to clip.
The images look flatter and less crisp than what I graded them to in resolve.
Does FCPX remap the black/white levels or do some gamma voodoo?
Remember I'm looking at the output of the two programs on the same monitor connected to the same I/O card, so even if the plasma is not a calibrated client-monitor at least it should look the same, no?
Help appreciated.
Director of Photography, Director, Editor
Vienna, Austria

Use of Compressor's gamma adjustment is (commonly enough) needed if your blacks are too pure for NTSC. That certainly seems to be the case with your material.
Personally, I would export out of After Effects to the Animation codec, then drop that file into Compressor for export directly to MPEG-2 and .ac3. Of course using the Gamma Correction filter - I'd start testing with a setting of 1.05 and move up if that's not enough.
And yes, NTSC televisions (and DVDs) are affected by what is called Setup - it means blacks are very different from the digital realm. (while the link pertains to digital video, the phenomenon still applies to you)

Similar Messages

  • Looking for bright ideas for moving address book from MacBookPro that can't be upgraded from OS 10.5.8 (big bummer!) to iCloud and iPad2

    Looking for bright ideas for moving address book from MacBookPro that can't be upgraded from OS 10.5.8 (big bummer!) to iCloud and iPad2

    Have you tried exporting the contacts from address book on your mac to your desktop and importing them into the iCloud contact file using the import command from the menu when you select the gear icon.

  • Auto brightness does not work after upgrade from iOS5 to iOS6 on my iPod touch. Is this intended by Apple, or is it a bug?

    I attempted to ask this question, yesterday. However, I am not used to typing with my thumbs, yet, and messed it up some. So, I will give this another try. Auto brightness does not work after upgrade from iOS 5 to iOS 6 on my iPod touch. Is this intended by Apple, or is it a bug?

    Have you looked at the previous discussions listed on the right side of this page under the heading "More Like This"?
    iOS 6 changed how that feature works.

  • When importing rendered clips from davinci into premiere they look darker and more contrasty.

    After importing the graded and rendered clips from davinci into premiere pro cc they look darker and more contrasty. I've checked the exported files from DaVinci and they look totally fine if you play them with any media player, but when I import them in Premiere Pro CC, they appear darker and way more contrasty than I've graded them in Resolve. Anyone have a solution for that?
    Thanks!
    Andrew

    This is a long-standing and complicated issue.  To start with, different media players interpret footage differently.  You can hope for the best, but there can be no expectation that footage in one player will look the same in another.  Ridiculous, but true.  The situation is further aggravated by different display cards and different monitors, and no prevailing standards of how color and levels are interpreted.
    In your specific case, you need to look at the waveforms, in Resolve and in PPro.  It sounds as if the blacks are being crushed in PPro, which could mean you're monitoring them at 64 in Resolve, but they're being output at 0 or remapped to 0 in PP.   This may also relate to whether you've monitoring with data or video levels in Resolve. 
    Is there a setting in PPro which covers how values are mapped, as data or video?  I think so, but just can't recall....  Anybody?  Staff?

  • Why I cannot to import .XML exported from DaVinci Resolve or Premiere?

    Both have options to export to FCPX. But it don't work. When I go to File -> Import -> XML in FCPX, the files .XML exported from DaVinci or Premiere, appear hide or unable to select.

    Hello Neil,
    Thanks for the response. I understand about the Speedgrade / Premiere thing. What we are trying to do is essentially the reverse. I use DaVinci Resolve, my client is using Premiere to edit. They want me to do essentially a best light pass on the footage without rendering it out. I then would export a CDL / EDL from Resolve and they would load that into Premiere or Speedgrade whichever would then display the simple color grade using the Adobe color tools. The CDL generated from Resolve is a cross platform basic color information inside an EDL. Anyway I can't find a way for Premiere / Speedgrade to read this info yet. Supposedly It will in Final Cut X, although I haven't tried it since I don't have Final Cut X on my computer.
    John

  • Brightness/Gamma problem

    I've noticed that a movie in Quicktime 7 pro looks brighter than the same movie viewed inside Final Cut Pro and After Effects. Anyone know what this is?
    G5 dual 2g   Mac OS X (10.4.6)  

    The MPEG-4 exports should automatically adjust to the gamma settings of the viewing machine. This prevents a file created on a Mac from appearing too dark on a PC. Older codecs don't support auto gamma correction.
    You may get a better answer in the Final Cut Discussion pages. I don't own FCP.

  • After Effects CS 5.5 renders brighter gamma than my CS3.  Files gamma don't match

    I just upgraded to After Effects CS 5.5 last week.  I had a project come back that was originally done in CS3.  All the renders were done as the animation codec with an alpha channel.  When I open the CS3 project in CS5.5 and render out a composition it is brighter than all the original comps rendered out of CS3.  I have tired the checking the legacy quicktime check box in project settings but that didn't change anything.  I also have tried several color management settings.  Does anyone has any ideas of things to try. 
    Thanks

    Have you considered, that this may be related to the global Gamma change Apple introduced in OSX 10.6.7? It would be relevant for Quicktime, as QT is monitor profile aware. With regards to ProRes, that's its own story of madness for which Todd has some info on his blog. Maybe look into that as well. Concerning your effects I would look into whether hardware acceleration could be at play here, i.e. turn off OpenGL in the prefs, if enabled. Several filters do use this option and in light of the eternally lasting problems with this, it#s always a good idea to give it a look...
    Mylenium

  • Is there a way to import a CDL / EDL generated from DaVinci Resolve into Premiere/Speedgade to have it show the basic color from Resolve?

    Trying to take a basic color pass from Resolve for a client in Resolve and send a CDL / EDL to them with the media. They will load media, open EDL and have the timeline populate showing the basic color applied using either Premiere or Speedgrade. Tried Adobe support (worthless)!  Any help would be great.
    Thank you

    Hello Neil,
    Thanks for the response. I understand about the Speedgrade / Premiere thing. What we are trying to do is essentially the reverse. I use DaVinci Resolve, my client is using Premiere to edit. They want me to do essentially a best light pass on the footage without rendering it out. I then would export a CDL / EDL from Resolve and they would load that into Premiere or Speedgrade whichever would then display the simple color grade using the Adobe color tools. The CDL generated from Resolve is a cross platform basic color information inside an EDL. Anyway I can't find a way for Premiere / Speedgrade to read this info yet. Supposedly It will in Final Cut X, although I haven't tried it since I don't have Final Cut X on my computer.
    John

  • FCP X can't find clips exported from Davinci Resolve

    Doing a roundtrip from FCP X to Davinci Resolve Lite and back.  XML imports into Resolve OK, then I render the media and export an XML from Resolve to the same folder.
    When I import the XML from Resolve into FCP X, it imports the timeline but just black media -- in Events, there are green rectangles with the names of the "old" clips, meaning what they were called in FCP to begin with. However, Resolve has rendered them with "V1-0001" appended to the name of the clip.  I have tried this with several different Resolve settings ("Render clips with unique names" both on and off.)
    Any way in FCP X to "reconnect media" as there used to be?

    Yes, I imported them. They appear as separate clips (that is, separate from the blank ones that come in with the XML).

  • Over bright gamma?

    This is a bizzare one, and i'll start from the beginning to make everything clear as to what has happened and going on.
    One of the macs at my work place seems to be what looks to me like the gamma or contrast has been turned up too much so that there is no distinction in shades of dark colours, and greys look white so editing photos and designing is being affected when going to print.
    It all started back on their old G5 mac when the apple displays were swapped (same type, the ones with the clear plastic and touch sensitive buttons). She's obviously upgraded to the intel mac pro and copied all the settings across which has transfered this problem with it.
    I booted up the old mac today, and as the desktop is loading I noticed a massive change in the brightnesses of the wallpaper as it finished loading (went from normal/light to a darker blue).
    When I logged into the macs via VNC the bits that are meant to be grey are grey, and everything looks like the other mac pro we have, i.e perfect but still on the screen of the actual mac, those bits are white.
    I've tried calibrating the screen, but I cannot seem to get what ever is causing this whiteness/lack of distinction to go away. I've even tried a PRAM/NVRAM reset (on the old mac to see if it would cure it there first before trying on the production mac).
    Any ideas if there is something elsewhere that needs resetting or turning down?
    Message was edited by: AndrewMurphy

    Changing the Color under System Preferences -> Color -> Display Profile has no effect I assume since you tried Calibrate?
    Try checking under System Preferences -> Universal Access -> Seeing -> Contrast slider under Display
    If that doesn't work then try another monitor, if you haven't already, and see if it persists.
    May have to go pull some plists if this doesn't fix it though.

  • Shortcuts: Change brightness to F1 and F2 key from

    Good morning All.
    The F1 and F2 keys on my Apple Wireless Keyboard no longer control the brightness settings for my LED Cinema Display.  The shortcut has changed to F14 and F15.  The keyboard itself still works fine - and the F1 and F2 buttons do still work.  It's not a hardware issue.  I'm on OS X 10.9.4.  I've had this Mac Mini for 2 years, sometime in the last 10 days this shortcut changed.
    I want to change the shortcut to F14/F15 to F1/F2 . I called Apple to ask how I could change the shortcut back to F1 and F2, but they did no know the answer. I've gone to Keyboard Settings/Shortcut/Display - and I see "Decrease display brightness" set to F14.  Above that it says "To change a shortcut, select it, click the key combination, and then type the new keys" I could not figure out what that implied since I don't have an F14 or F15 button on my keyboard.
    Thanks for anyone's help!  I can barely use the screen now, too dark!
    -Awatto1976

    Thank you for articulating - same thing just happened to me today...out of no where. No changes made... but brightness F1 and F2 keys stopped working. After reading your post, found they got remapped to F13 + F14. Trying BTT and other remapping apps w/no success.
    Any updates?

  • Gamma shift  from After Effects

    Hi,
    We had to apply graphic work over a QuickTime Uncompressed 8 bit footage from Final Cut Pro.
    The graphic work was done in After Effects.
    The After Effect output was done using QuickTime Uncompressed 8 bit, the very same codec.
    ...but all the footage has a gamma shift ( upward ) and a slightly increased color saturation...
    What's wrong ?
    If we export Uncompressed 8 bit from FCP and reimport in FCP, there is NO gamma shift. ...so it seems to be an After Effect setting (or problem).
    thanks !

    Well I must specify that we haven't had any problems with gamma when working between After Effects and FCP in Mac OS X. It's just if you bring some material from PC to MAC you might notice that graphics are too bright, because FCP thinks all the RGB material is made with gamma 1.8. So FCP maps RGB colors to YUV (television colorspace used by DV, Uncompressed 8-bit etc.) with gamma 1.8.
    BTW FCP doesn't collaborate with color management in OS X. So it doesn't make any difference how FCP handles RGB material if you change OS X gamma to 2.2.
    FCP works in YUV and After Effects in RGB so that's why you don't see gamma problems when exporting material from FCP. I think you should first check from Apple Software Update you have the newest Pro Applications Update. I remember Uncompressed 8-bit codec had this kind of gamma problem with After Effecs couple updates before.
    G5 DP2.5 (3.5GB RAM)   Mac OS X (10.4.5)   FCP 5.04, AJA Io, XSAN 1.2

  • Color edited in DaVinci then exported from Premiere the color changes a lot in final product. Are my export setting wrong?

    I used davinci lite resolve to color edit my footage then I exported round trip to Final cut pro (premiere). Then exported out of premiere and it doesn't look the same at all. What can I do to fix this problem? I have exported from davinci in 10 bit uncompressed with the same issue.

    Should I have imported the whole PRIVATE FOLDER from my hard drive?
    Actually yes and ingest via the Media Browser. That is the best way.
    For now: Rename folder the footage is in and see if you can relink.

  • Difference in video brightness/contrast across viewer applications

    I am using FCP->Color>FCP roundtrip to grade Red footage. After I grade the clips in Color and send them back to FCP, I see a difference in brightness/contrast of the graded clips when playing in FCP. And when I export the final output to quicktime and play it in quicktime player, I see further difference in brightness and contrast. Essentially the clips appear darker when played in QT player. Now I am confused as to which application is showing the correct brightness/gamma level? Is there a way to make all the applications play the video at same/true brightness/gamma? Any insights would be highly appreciate. Thanks!
    -Pranab

    There is a distinction between PCIe-based GPUs and I/O cards that you have to be aware of. COLOR's user interface, render/scopes and output are split between the two. A graphics processor handles the user interface (PCIe is better, application won't run on on-board integrated or AGP), and actual grade values for judgement are based on a PCIe HD-SDI I/O card like AJA Kona3, or Blackmagic (Intensity?) which are NOT graphics cards, they are video interfaces.
    For GPUs, if the application is running, that's a good indicator. However, preferred cards have been evolving over the past 5 years. My first system was configured with a Quadro 4500FX which was a total waste of money. I deliberately chose an ATI X1900XT for the next tower, which was a significant improvement. My third MacPro is running fine with the default ATI 2600HD, which is as plain vanilla as you can get. Some users report speed advantages with the newer 4870 series, but I fail to see significant differences -- COLOR in its current delivery will never deliver "real-time" preview playback on any card, and it still takes a very long time to render, in comparison with some other grade offerings. Fourth machine, I'm still deciding, but it would be great if Apple got the FX4000 thing happening, and I'll get to that.
    Nvidia does suffer from some bit-depth processing issues in that it does not directly support 10-bit codecs, but can be switched into the more intensive "float" mode. It also has some other transient issues.
    Looking outside Apple COLOR, consider that Blackmagic Resolve ("DaVinci") is predicated entirely on nVidia's CUDA-processing technology and is restricted to implementation on 2 or 3 very specific cards, as opposed to the FCP-centred, but ATI/AJA-leaning Apple solution, which, although somewhat restricted, is 90% more likely to run on almost anything PCIe that you can stick into a MacPro. However, the color science and cross-platform (AVID support, for example) that DaVinci offers makes it very tempting, and that's why I'm paying a lot more attention to nVidia these days.
    If you are looking for HDSDI PCIe cards, then AJA, with IO, Kona3, and so on definitely has the edge and can extend capabilities up to and beyond 2K processing, but many users select other solutions that suit their individual needs -- not everyone delivers theatrical Digital Cinema or needs to.
    jPo

  • Gamma problems

    Hi there . . . . .
    When I export stuff from AE in most formats (H.264, MPEG4 etc) the render is pale, washed out and much lighter than my AE project.
    I know there is a gamma issue with H.264 and quicktime, but MPEG4 (in a Quicktime wrapper) now also seems to suffer the same problem, whereas it didn't pre-Snow Leopard ?
    Anyone got any clues as to the root of the mismatch between AE and Quicktime player ?
    P.S. If I render out as ProRes the problem disappears ?
    Cheers
    Lee.

    Thanks for putting in hours of time, this whole area is a pain. I need to point out that while I understand the technical issues, the guy who knows the practical issues is out due to a family emergency so I will be a poor balm.
    Where to start?
    After Effects uses RGB internally to represent color. Using the export menu has Quicktime drive the whole export process, which includes having quicktime call back into AE to render an RGB frame for quicktime to go compress. When using the render queue, AE is master, it renders a frame and then pushes it to quicktime. When we do the pushing, we get the opportunity to set some setting that sometimes help with gamma and color shifts. I'll call out what we do in the render queue path that we can't do in the Export menu path due to the underlying architecture.
    The problem with gamma and color shift almost exclusively occurs with Codecs that run in YCrCb. This includes all ProRes (I'm lumping in ProRes 4444 even though it can do RGBA) and even PhotoJPEG if you aren't at highest quality (I think above 75%). These codecs are often defined to be in either the Rec601 or Rec709 color space (http://en.wikipedia.org/wiki/Rec._709). My guess is PhotoJPEG is sRGB, but that is a wild guess. Quicktime makes certain assumptions about the RGB color buffers it gets. These assumptions are different in Snow Leopard, Leopard, and Windows.
    Since the codec is expecting color to be represented a certain way, the assumptions and associated color conversions when going from RGB to YCrCb is where things go awry.
    By default Quicktime assumes RGB buffers are in a monitor color space. I believe this means sRGB (http://en.wikipedia.org/wiki/SRGB) with a 1.8 gamma on Leopard (technically not sRGB, but what can you do), sRGB with 2.2 on Leopard, and sRGB with 2.2 on Windows. Since Rec709 and sRGB have the same color primaries, any incorrect assumptions here only appear as brightness/gamma changes.
    The idealized black box export path for the Export Menu is:
    AE->RGB (untagged)---Color Conversion in Quicktime--->YCrCb--->compressor.
    In CS4 (maybe CS3?) we added the ability to tag the RGB buffer with the gamma. AE also will request RGB frames from Quicktime with the GAMA tag applied when importing. This is controlled with the "Legacy Quicktime Gamma" preference. I believe the export half of this will only affect the Render Queue and not the Export menu.
    The intent behind using the gama tag was to make the RGB to YCrCb conversion more predictable. Alas, the tag ends up in the resultant movie and can influence other consumers of the file (like FCP). Further confounding things. This is why we added the Legacy Quicktime Gamma checkbox, we could not make every single test workflow work. The Legacy workflow does not add the tag.
    Lastly, not only does each product on the market talk to Quicktime differently (i.e. some use RGB, some use YCrCb buffers directly, some obey the gama tag for color conversions, some don't), but some codecs themselves implement color conversions. Also, some 3rd party codecs install their own color conversion routines that compete with the Apple defined ones and will cause different RGB to YCrCb conversions even when NOT using their codec. Also, Quicktime makes different guesses based on which OS you are running.
    Since a couple of ProRes codecs were shipped after CS4, they don't work correctly out of the box. They need some custom settings (http://blogs.adobe.com/toddkopriva/2009/12/prores-4444-colors-and-gamma-s.html).
    Also, pixel dimension will also affect the color conversions as some codec use non-HD stuff as Rec601, not Rec709 which leads to another source of shifts.
    In the end the RGB to YCrCb color conversions are influenced by:
    1) Your export path (Export Menu, vs Render Queue)
    2) The operating system you are running
    3) Which codecs are installed on the system (even if you aren't using them)
    4) The setting of the Legacy Quicktime Gamma Setting
    5) The particular destination application.
    6) The pixel dimension of the footage.
    I also feel the need to point out that while ProRes may be in Rec709 (which nominally has a gamma of 2.2), Final Cut Pro will correctly convert YCrCb Rec709 to Monitor RGB (Gamma of 1.8 on Pre Snow Leopard) for display. By default After Effects does no display color correction. When importing a file that starts in YCrCb Rec709 we convert it to RGB Rec709 (Gamma 2.2) if AE does the decoding. This means something like a DV file will look different in AE and FCP on a mac with 1.8 display gamma. If you use an external preview device, I do not believe you will see any difference, but things will look different on the mac monitor.
    I'm hungry enough now that I'm just going to make more errors than I already have.
    I hope this helps someone.
    --chris

Maybe you are looking for