-
RED metadata per instance NOT clip for ‘pseudo-HDR’
Perhaps I’m missing something, but I can not find a way…
I have an .r3d with a blown out window which is redeemable if I go back to my native ISO settings. I want to put my low ISO window saver instance on V2 with an alpha output, key its highlights, and have the V1 version at a standard ISO for my normal grade.
Problem seems to be that Resolve treats the .r3d on a clip-specific level altering every instance of it in my timeline. Duplicating it on V2 does no good since a change to one ISO affects the other.
I know Scratch used to have but fixed this issue–clip specific ISO adjustments not being possible, so I don’t think it’s simply a matter of the RED SDK or RR feeding one value alone to DaVinci. There must be a workaround. It seems to me like something a lot of people out there would be doing so please do share.
Thanks!
-
1 Reply
-
I have found a solution–far from ideal, but workable should anyone stumble upon this thread. From all I can tell, Resolve will not interpret the RED settings differently for two instances of the same clip imported with an EDL/XML. The basic solution is to import the clip from the browser as seperated clips–already divided into those you specifically will need to change independent of one another.
I specifically needed a V2 track with lower ISO settings for highlight protection so I made a folder called RED Dark and added all my RED media and interpreted it at a low ISO. You could use “Split and add” here if you require clip specific adjustments rather than just darkening everything. Then I loaded my normal XML into a timeline twice, the second time conforming to my “dark” folder in the media pool and pasted this on V2 in the neutrally exposed version. An alpha output on V2 let me get my highlights back on the clips where I needed it.
I still hope I’m missing something, but if not, hope this helps someone else…
Reply to this Discussion! Login or Sign Up