Hi Alex, Motion Blur node works much better when you connect vector generator to both inputs, one set to foreground and other to background, great videos by the way, all the best, cheers.
I saw that a while ago, but I believe (I could be wrong of course) that its more of an approximation. I did try it and I personally didn't find the results all that useful. Then again, this type of thing could be very shot dependent.
@@alexvillabon Vector Generator skips pixels to arrive at an 'approximate' velocity, hence why it can break when the image is too complex. Converting the STmap to MV is quite literally a representation of how far something has moved. Tweaking samples and shutter speed will do the rest.
Well explained! Thanks for sharing your process in detail.
I use the kronos trick a lot too! In my experience leaving the speed value at 1 works just fine
I had no idea. I’ll be sure to test it. Thanks
Hi Alex, Motion Blur node works much better when you connect vector generator to both inputs, one set to foreground and other to background, great videos by the way, all the best, cheers.
Thanks, there is always something new to learn!
Great video...
You can also create a motion vector pass directly from the stmap. Ben McEwan has a great write up on his blog.
I saw that a while ago, but I believe (I could be wrong of course) that its more of an approximation. I did try it and I personally didn't find the results all that useful. Then again, this type of thing could be very shot dependent.
@@alexvillabon Vector Generator skips pixels to arrive at an 'approximate' velocity, hence why it can break when the image is too complex. Converting the STmap to MV is quite literally a representation of how far something has moved. Tweaking samples and shutter speed will do the rest.
@@OdynophoniaTIL. Thank you