vMix Forums
»
General
»
General Discussion
»
Avoid selecting "wrong" PTZ virtual input
Rank: Advanced Member
Groups: Registered
Joined: 3/22/2020(UTC) Posts: 50 Location: River Hills Thanks: 3 times Was thanked: 2 time(s) in 2 post(s)
|
I'm considering multiple PTZ cameras each with multiple virtual inputs (presets). I plan to use Preview to select my next transition. However, if one of the presets of a given camera is in Output, then attempting Preview of any of that camera's other presets will be immediately reflected in Output, which for our purposes would be production no-no. Is there some way to alert me prior to selecting a camera's preset if one of it's sister presets is already in Output?
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 8/9/2020(UTC) Posts: 156
Thanks: 3 times Was thanked: 20 time(s) in 19 post(s)
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 3/22/2020(UTC) Posts: 50 Location: River Hills Thanks: 3 times Was thanked: 2 time(s) in 2 post(s)
|
Thanks mtone. I added my +1 plus extra comments to the feature request topic you provided.
I'll delete this topic.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 10/6/2020(UTC) Posts: 98 Was thanked: 21 time(s) in 21 post(s)
|
The only workaround I found is to use a controller - in my case a Streamdeck - with activators on all shots which use the same camera, so that they all show in red when that camera is live. It does mean you need to key an eye on the buttons as well as your multiview though, so it's not a great workaround, I'll admit.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 3/22/2020(UTC) Posts: 50 Location: River Hills Thanks: 3 times Was thanked: 2 time(s) in 2 post(s)
|
Oh geez, I hadn't even thought about multiview. That adds another layer of complexity to the problem. I like matkeane's activator approach. In my perfect world, vMix would impose a big, red exclamation point center screen in all the presets, and a blinking one on the active preset.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 10/6/2020(UTC) Posts: 98 Was thanked: 21 time(s) in 21 post(s)
|
Well until there is an automatic solution, I guess you could show/hide a layer with a big red exclamation mark in each input using the same camera - but it would mean a fait bit of shortcut programming with the Streamdeck. You could even use Streamdeck internal commands to hide/deactivate buttons that would cause an unwanted PTZ movement, but there's probably a simpler solution...
I found a bit of spatial organisation helped a lot - virtual inputs using the same camera were grouped in the same column, on both the Streamdeck buttons and in the multiview display. So if you've cued any input in column 1, you need to switch to another column (and camera) before you select a different input in column 1. Works pretty well, even without looking at the activators - if your finger is on a button in column 1, use another finger in another column before you move to another row in column 1.
|
1 user thanked matkeane for this useful post.
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 3/22/2020(UTC) Posts: 50 Location: River Hills Thanks: 3 times Was thanked: 2 time(s) in 2 post(s)
|
The following seems like it would solve some of my issues and I'm looking for someone to confirm/refute my thinking: When I create multiple angles (presets) on a PTZ camera, I could also re-input the camera a second time but not configure PTZ for it. Selecting this non=PTZ version of the camera to Preview should show me where it's currently pointed, right? And, a multiview input that includes this non-PTZ version of the camera should show the current position of that camera, right? If confirmed on both counts, I could then create my triggers only on inputs that use the non-PTZ version of the camera. This would allow me to freely hit my triggers without fear they will cause unintended movement of a live PTZ camera in Output. Finally, I could then move all my PTZ presets to a color tab that I normally don't have in view, leaving in main view only the inputs that are based on non-PTZ cameras. If I really need to repoint a PTZ camera, I would first be forced to opening the color tab, and that should be enough to put me on notice that I need to be careful in what I select next. Yes/no?
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 2/23/2019(UTC) Posts: 556
Thanks: 62 times Was thanked: 130 time(s) in 118 post(s)
|
Originally Posted by: Bob Brazner When I create multiple angles (presets) on a PTZ camera, I could also re-input the camera a second time but not configure PTZ for it. Selecting this non=PTZ version of the camera to Preview should show me where it's currently pointed, right? And, a multiview input that includes this non-PTZ version of the camera should show the current position of that camera, right? That's what the original input of your camera already does. No need to re-input it, if I have understood you correctly.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 3/22/2020(UTC) Posts: 50 Location: River Hills Thanks: 3 times Was thanked: 2 time(s) in 2 post(s)
|
So, you're saying only the created inputs (from the "create input at this position" button) are PTZ. but the original is not. That's indeed good news, and thanks for pointing this out.
|
|
|
|
vMix Forums
»
General
»
General Discussion
»
Avoid selecting "wrong" PTZ virtual input
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