vMix Forums
»
General
»
Feature Requests
»
Group/Flatten Layers for Easier Cropping
Rank: Advanced Member
Groups: Registered
Joined: 12/16/2018(UTC) Posts: 67 Location: Newfoundland & Labrador Thanks: 1 times Was thanked: 6 time(s) in 4 post(s)
|
Hello, On some productions we have to take score from a scoreboard camera then manipulate the data to overlay on our graphics. Most of the time it is not possible to get a direct shot of the scoreboard so we need to rotate and skew the image to straighten the data on screen. Currently when cropping, it follows the angle of the original image (as seen in the first image). It also does this even if the rotated image is placed into a new blank shot, or a virtual input is created. vmix_crop.jpg (268kb) downloaded 0 time(s).Cropping also has issues when trying to crop inputs made from multiple layers, as seen in this video from Tom Sinclair of Eastern Shore Broadcasting: Fixing the Crop Problem in vMixIt was found that layers are only flattened if used in a secondary mix or as an NDI output, then brought back in as an NDI input, then it can be manipulated as one. As we have a vMix HD licence, none of these options were available to us so we looked elsewhere and found the solution in OBS. OBS has a feature that will let you group or "flatten" the layers so that the input/scene can me manipulated as one. This lets us rotate the original image, group it, then crop the image to clean up the non-level borders and send it via NDI into vMix. obs_crop.jpg (235kb) downloaded 2 time(s).-=-=- I would like to see this feature added to vMix (at all software levels). Seeing this could be done so easily in FREE software was very surprising. After watching Tom Sinclair's video, it is either not possible (vMix HD) or very easy to group/flatten layers of an input to manipulate it as one complete input. It would be much more useful to have a virtual input or creating a new blank input flatten the layers to accomplish this task. Thanks m
|
3 users thanked MarkNF82 for this useful post.
|
|
|
Rank: Member
Groups: Registered
Joined: 5/27/2020(UTC) Posts: 14 Location: Dallas Was thanked: 5 time(s) in 3 post(s)
|
THis is absolutely the current problem I have the most in vMix. There is NO reason I can fathom whrre if I have an input, let's say a background, and then a camera greenscreen removed, and then the speaker's title over them. I can see no reason why if I bring this as a layer into something else that cropping it only crops the BASE layer (which might very well be a "transparent Color input" meaning that the layer crop crops NOTHING. Or why woudl I only want to crop the base layer of th ebackground to fit in a PIP but then the greenscreen person can reach outside the box? W. T. F is that shit? No, ANY input brought into another as a layer must ABSOLUTELY be flattened to one layer.
|
3 users thanked IEBAcom for this useful post.
|
|
|
Rank: Member
Groups: Registered
Joined: 11/27/2020(UTC) Posts: 14
Thanks: 4 times
|
|
|
|
|
Rank: Member
Groups: Registered
Joined: 8/11/2020(UTC) Posts: 12
Was thanked: 1 time(s) in 1 post(s)
|
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 5/24/2020(UTC) Posts: 5
|
+1
Sure, I can use mix inputs for this but there are only three.
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 1/13/2020(UTC) Posts: 3 Location: Baltimore
|
|
|
|
|
Rank: Member
Groups: Registered
Joined: 4/17/2016(UTC) Posts: 17 Location: New Zealand
Thanks: 7 times
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 2/18/2014(UTC) Posts: 1,837 Location: Stockholm
Thanks: 144 times Was thanked: 297 time(s) in 250 post(s)
|
+1 I might add a suggested way of implementation - an option "Flatten before use" when specifying a Layer source. We have been struggling with various workarounds for this problem for many many years. Recently when Mix Inputs appeared they turned out as one fix. Unfortunately there are only three Mix Inputs, and it is an awkward solution for the problem at hand. Of course we in this topic are not the only ones who want to flatten things out ;) A quick search revealed some related topics that discuss this problem, although I did not find any real Feature Requests. (I could swear that there are some, hard to find them though). https://forums.vmix.com/...8392-Invisible-MultiViewhttps://forums.vmix.com/...ew---Fit-source-to-framehttps://forums.vmix.com/...-Bug-or-known-limitation
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 3/10/2022(UTC) Posts: 1 Location: Milan Thanks: 1 times
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 7/4/2021(UTC) Posts: 310 Thanks: 8 times Was thanked: 40 time(s) in 35 post(s)
|
+1, for the same reasons noted by richardgatarski. Originally Posted by: MarkNF82 Seeing this could be done so easily in FREE software was very surprising. There are a number of things that can be done in OBS that can't be done in vMix. It's really not that surprising. For most of them, I simply use OBS and bring it into vMix via NDI or the Virtual Cam plugin. This, however, isn't one of them--as you acknowledge, Mix inputs solve this problem, but merely are not available in the tier you've selected. I understand the frustration. I didn't love the idea of shelling out another $350 (doubling the purchase price) to get vMix 4K for a production done entirely in 1080p. But that's what I had to do to get the features I wanted/needed, so that's what I did. As your issue seems to be, not that a solution is unavailable, but that the solution is locked behind the paywall of tiers you don't have, I wouldn't hold my breath for this anytime soon (if ever). If they do add this feature, since, like richardgatarski noted, using a Mix input for this can be a bit clunky, since it's doing the same processing & solving the same problem, I wouldn't be surprised if it's behind the same "4K and up" requirement as the Mix inputs or the Output input. I also wouldn't be surprised if, for processing reasons, using it still constituted using a Mix input, albeit in a more direct/streamlined manner.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 3/7/2022(UTC) Posts: 71 Location: Munich Was thanked: 33 time(s) in 17 post(s)
|
+1, the missing of a "flatten" feature is really one of the most frustrating things in vMix.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 1/23/2022(UTC) Posts: 94 Location: Milton Keynes Thanks: 13 times Was thanked: 5 time(s) in 5 post(s)
|
+1.
My use case is that we would like multiple sources (vCall, Teams laptop via NDI, Zoom laptop via NDI, camera, etc) and multiple "master" individual person inputs, as we don't necessarily know who is going to appear on what source.
With the individual inputs (Bob, Jane, etc) we can then toggle layer 1 on those to "assign" Bob to vCall4 and Jane to Camera 2, for example. All good so far.
Where it then fails is that while I can use those "individual people" inputs to build other inputs with layers, for example a 2 box input showing Jane and Bob side by side, and have their picture change as I assign different sources, AND I can resize and move them in the layer to build the boxes, I CAN'T crop them as only the main input crops and not the layers on top.
Currently we are achieving this by building boxes which then have the source changed as well as layering on top of an "individual person" input - two steps instead of 1, more programming, more testing and more checking on air.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 3/7/2022(UTC) Posts: 71 Location: Munich Was thanked: 33 time(s) in 17 post(s)
|
There are currently two workaround to solve those problems by "simulating" the missing flatten feature: (1) you can use a Mix input as an intermediate input, as it implicitly flattens its sources, or (2) you can use a VirtualSet input with a 1:1 UVMap (see vMix-VirtualSet-Flatten in my https://github.com/rse/vmix-assets/ project), as this UVMap also implicitly flattens the sources.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 7/27/2022(UTC) Posts: 31 Thanks: 11 times Was thanked: 1 time(s) in 1 post(s)
|
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 11/8/2022(UTC) Posts: 3 Location: Bourne End
|
+1
One of the biggest issues we face with vMix. We need to be able to compose a shot and then manipulate it as a single video layer.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 1/9/2019(UTC) Posts: 77 Location: Stockholm Thanks: 20 times Was thanked: 5 time(s) in 4 post(s)
|
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 3/17/2022(UTC) Posts: 5 Location: rlp
|
|
|
|
|
Rank: Member
Groups: Registered
Joined: 8/9/2022(UTC) Posts: 10 Thanks: 1 times Was thanked: 1 time(s) in 1 post(s)
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 4/23/2017(UTC) Posts: 1,219 Location: Germany Thanks: 3 times Was thanked: 168 time(s) in 150 post(s)
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 2/18/2014(UTC) Posts: 1,837 Location: Stockholm
Thanks: 144 times Was thanked: 297 time(s) in 250 post(s)
|
Regarding the various workarounds that have been suggested in this topic, including in it´s first post.
A year ago, when I added my positive vote, I wrote "when Mix Inputs appeared they turned out as one fix. Unfortunately there are only three Mix Inputs, and it is an awkward solution for the problem at hand."
I now would like to add that in spite of the increased number of Mix Inputs introduced with v26, it is still an awkward workaround. And it typically is not possible to use for us since Mix Inputs are sometimes only possible to refer to by Mix number only in Shortcuts and the API. Imagine having 7 Mix Inputs and deleting number 3. Then Mix 4,5, and 6 suddenly becomes 3,4, and 5. Shoot...
|
|
|
|
vMix Forums
»
General
»
Feature Requests
»
Group/Flatten Layers for Easier Cropping
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