Subhadip Sen
Well-known member
My apologies. I don't mean to denigrate the tech. HDRx™ is amazing. It's groundbreaking. I really want it. But it's not exactly the same as the real thing. Almost everything I work on uses the Foundry's motion blur. It's not always perfect.
To deny that HDRx™ isn't the same as actually capturing the true motion blur of native 18 stop sensor is to misrepresent it. I don't feel you are misrepresenting it. But every 'trick' has a dark side. I'm not saying the tricks shouldn't employed 99% of the time. Just that in the other 1% you wish you could do it natively.
Even The Foundry is the first to say that their tools are great. Their tools save time. But they don't always work perfectly.
If you like the look of Magic Motion more than normal motion blur then it's a feature. If you don't, then you'll never get it perfect. You'll usually get it pretty damn near perfect but there'll always be artifacts.
You are making a critical assumption that the MNMB implementation is exactly the same as The Foundry's current products. Which is clearly not true as Jim has said "working on...". They are no doubt fine tuning an improved implementation that works much closer to true motion blur.
Another thing worth remembering - even if the implementation is exactly the same - the blur will take its effect on the X-track, which is detailed and blur-less. Helps immensely for synthetic blur.