I agree, Resolve is cumbersome: no command line processing/rendering, no drag and drop to the bin, needing to disable the ODT in the prefs prior to export to get linear exr's etc. Beyond that, the colours don't match Nuke (mainly reds), although maybe they will once both are using ACES 1.0. I'm guessing all the information about the primaries are in the CinemaDNG metadata and, maybe, utilised correctly when going to ACES linear exr's through Resolve.
I also like the idea of just doing this in Nuke Studio and forgetting about Resolve. I tried out the new CinemaDNG reader in Nuke, but it seems it clips at 1. The way around it is to pull down the exposure in the Read node then add an exposure afterwards to go back up by the same amount, but it doesn't really match the dynamic range and primaries of going the ACES route. Re: log encoded ProRes instead of CinemaDNG, yes it seems to be even more of a moving target getting to linear with the correct primaries. I'm kind of hoping now they have their own custom sensor that BMD will eventually publish the relevant colour science details in a straightforward way like Arri have. Michael On 13 July 2015 at 19:03, Gary Jaeger <[email protected]> wrote: > Hey I’m curious if anybody on Windows has downloaded the free version of > Fusion to compare how the various flavors work there? > > Gary Jaeger // Core Studio > 249 Princeton Avenue > Half Moon Bay, CA 94019 > 650.728.7957 (direct) > 650.728.7060 (main) > http://corestudio.com > > > On Jul 13, 2015, at 4:00 PM, Gary Jaeger <[email protected]> wrote: > > > > Yeah, that’s been my experience as well. Frustrating. > > > > Gary Jaeger // Core Studio > > 249 Princeton Avenue > > Half Moon Bay, CA 94019 > > 650.728.7957 (direct) > > 650.728.7060 (main) > > http://corestudio.com > > > >> On Jul 13, 2015, at 3:56 PM, chris <[email protected]> wrote: > >> > >> hiya, > >> > >> don't have a good answer to your exact problem, but i thought i'll add > that i've done several tests between the "Video" "Film" and "RAW" recording > with a blackmagic pocket and for the life of it i couldn't find a way to > match them exactly in any application (not even in resolve, which is from > the same company!) > >> > >> i found that their provided "Log to Rec709" LUT gives quite different > results then if recorded in-camera in video mode - which is a pity because > the cameras video colours usually look better to me (but clip > shadows/highlights). > >> > >> might be that i was doing something wrong all the time (and if i have, > please let me know because i'd love to solve this), but i thought i'd add > this just in case that the problem is not your workflow but rather the > provided LUT (tried several others. > >> > >> wanted to get to the bottom of this for quite a while but as always > other things come up all the time. > >> chris > >> > >> > >> > >> > >> On 7/13/15 at 12:00 AM, [email protected] (Gary Jaeger) wrote: > >> > >>> Thanks Simon. The “close enough” solution is always where I’ve ended > up before, but I thought I’d actually try and solve it this time. Silly me. > >>> > >>> So I’m assuming you mean OCIOFileTransform, which I’ve used before for > various things, like when I made my own via MatchGrade and exported a .csp > file. That seems to work, but I can’t read any of the resolve luts into > that node. They fail with an error. I do have one called > “BMDFIlmToLinear.cube” that reads in, but doesn’t seem right either. Not > sure where I got that file, and it’s not the same as the “BMDFIlm To > Linear.cube” files that are installed with Resolve. > >>> > >>> It did occur to me though that it might be better to just use a > MatchGrade node. While that seems to sort of work for .mov files, I can’t > get the same method to work for the .dng files. > >>> Anyway, take a look if you have time. Curious about your thoughts. > >>> Gary Jaeger // Core Studio > >>> 249 Princeton Avenue > >>> Half Moon Bay, CA 94019 > >>> 650.728.7957 (direct) > >>> 650.728.7060 (main) > >>> http://corestudio.com > >> > >> _______________________________________________ > >> Nuke-users mailing list > >> [email protected], http://forums.thefoundry.co.uk/ > >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
