Has anyone used the region of interest option on motion vectors? I tried it but it didn’t seem to affect anything in the way that a full plate cache does.
The only way I’ve ever gotten it to work is to crop the image upstream from the action that’s doing the analysis. I know that’s not really an ROI in action, but it saves time for me since I’m running the analysis on a smaller image.
3 Likes
Hi @andymilkis
Thanks. Same experience here.
It felt like it should have have worked inside action too. I’m baffled it’s an option.
2 Likes
I haven’t checked, but I wonder if it was meant to limit where on the image the MVs affect, like if you wanted to anchor the outsides of the image. That wouldn’t speed up analysis, tho. That’s gonna happen at real-time.
1 Like
The first time I tried to use the ROI it failed me, as I recall. Never used it since. I almost always pre-stabilize and crop down to the smallest area needed. Not only does this make the computation run way faster, but it gives a better result. It’s not really an improvement on the actual quality per se, but the softness (which is really just an averaging computation I think) is much more useful when the source is already stabilized.
I agree. I just wondered if the ROI is broken or I don’t understand the functionality.
Yup…. never got this to work either. The whole Motion Vector implementation was wildly flawed from the start. It needs to be re-done from scratch. Batch Paint too.
4 Likes
Hi John, is it a specific Flame version in which you’re having this issue? Was it working before?
I’m on 2025 point something. Don’t know if it was working previously though I suspect not since @ALan said not.
Since this is a legacy issue, please open a case with Customer Support. Thank you!
1 Like