Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

HDRx Aces, Resolve

peter richweisz

Well-known member
Joined
Feb 2, 2017
Messages
77
Reaction score
1
Points
8
Location
Phuket/Bangkok/Thailand
Website
www.richweisz.com
I had some property shoot and i revisited using HDRx and i was running some test for a future project workflow. I was glad to see it was working pretty nicely using the newest version of Resolve studio until i switched to Aces. Older versions of Resolve got me nowhere using any of the blend modes with the helium sensor. Does anyone know if there is a 'science' behind why it is not doing anything in magic motion blend mode n Aces, but it does in simple mode?
 
Don't have an answer for you, but I would recommend splitting the two tracks and adding a slight motion blur to the high shutter one. Blends better than the standard ones and gives more control over exposure balance between the tracks.
 
Thanks a lot Christoffer. As my question did not get much traction on the forum, i contacted Blackmagic and they gave similar advice minus the motion blur: "As Magic Motion is a proprietary algorithm, you may find differences when different color sciences are being used, especially in color managed workflows like ACES. If you would like to use HDRx footages with ACES, my advice is to put Blend Type to 'None', 'Add Source' in your Node Graph and add a Layer Mixer Node, to get more accurate and manual control of the two image data streams."
I am still far from understanding why it does not work with the blend mode in the raw tab, but at least there is a work around. I experienced much longer rendering time with this method though, i assume if the red sdk was at work that would accelerate the computing time.
 
Back
Top