Rank: Advanced Member
Groups: Registered
Joined: 12/11/2020(UTC)
Posts: 31
Thanks: 4 times
|
Originally Posted by: mike16437  Originally Posted by: admin Hi Mike,
The issue reported in this thread is a different issue that was resolved a few years back.
What you appear to be reporting is how cropping in vMix works, it will only crop the actual layer of that input
and not any sub inputs underneath it. This is done for performance reasons and there is no way around this at this time
other than to crop each input at the source.
Regards,
Martin
vMix Thank you, that's good information to have. I'll follow up with a separate thread for the issue I was trying to solve with this method. -Mike Hi All, I came across this issue a while back and found the above in perusing the forums. In the original thread, the OP was 'nesting' a multiview inside of another input (fixed some time ago), while Mike was looking to have crop settings transfer to a different multiview. But, I've experienced another crop/positioning issue in 23.0.0.66 without any nesting. When I change an input on a standalone multiview layer, it will sometimes be a little larger or smaller than the correct positioning. I added an overlay border to try to mask it (re-cropping really slows things down), but the size difference is still significant enough to shrink or expand an input, sometimes on top of other sources or inside the overlay border. Might there be a known cause or fix?
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
Important Information:
The vMix Forums uses cookies. By continuing to browse this site, you are agreeing to our use of cookies.
More Details
Close
