logo

Live Production Software Forums


Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
knbPixels  
#1 Posted : Tuesday, March 4, 2025 8:12:53 AM(UTC)
knbPixels

Rank: Advanced Member

Groups: Registered
Joined: 2/7/2024(UTC)
Posts: 99
United States

Thanks: 10 times
Was thanked: 5 time(s) in 5 post(s)
I know I've encountered this before, but can't remember if there is a solution or not. When you create an "OnTransitionIn" trigger on input A that's used on a layer of another input B, and transition in that second input, the trigger doesn't fire because input A is just on a layer.

I tried "Flatten" on both inputs and it didn't help. Is there a workaround?
mavik  
#2 Posted : Tuesday, March 4, 2025 5:30:57 PM(UTC)
mavik

Rank: Advanced Member

Groups: Registered
Joined: 4/23/2017(UTC)
Posts: 1,273
Man
Location: Germany

Thanks: 3 times
Was thanked: 173 time(s) in 155 post(s)
Of course it's not working. You deal with input B and not A. So triggers are fired for input B and not A. You can copy the trigger to input B instead.
knbPixels  
#3 Posted : Tuesday, March 4, 2025 10:38:39 PM(UTC)
knbPixels

Rank: Advanced Member

Groups: Registered
Joined: 2/7/2024(UTC)
Posts: 99
United States

Thanks: 10 times
Was thanked: 5 time(s) in 5 post(s)
Originally Posted by: mavik Go to Quoted Post
Of course it's not working. You deal with input B and not A. So triggers are fired for input B and not A. You can copy the trigger to input B instead.



Ok thanks...Anyway, if anyone knows how to get around this issue let me know
dmwkr  
#4 Posted : Wednesday, March 5, 2025 12:13:33 AM(UTC)
dmwkr

Rank: Advanced Member

Groups: Registered
Joined: 2/23/2019(UTC)
Posts: 576

Thanks: 62 times
Was thanked: 135 time(s) in 123 post(s)
Don't know what you are trying to accomplish, but layers can also be used on input A itself (including a virtual input of A), and (de)activated as needed.
knbPixels  
#5 Posted : Wednesday, March 5, 2025 12:21:19 AM(UTC)
knbPixels

Rank: Advanced Member

Groups: Registered
Joined: 2/7/2024(UTC)
Posts: 99
United States

Thanks: 10 times
Was thanked: 5 time(s) in 5 post(s)
Originally Posted by: dmwkr Go to Quoted Post
Don't know what you are trying to accomplish, but layers can also be used on input A itself (including a virtual input of A), and (de)activated as needed.



Ok so here's an example.

There's a camera input, a layout that uses that camera input on a layer, and a third input where I want to load various titles on the layers (not speaker titles, just text title inputs). We will call that third input "Text Input".


What I want to happen, is when the camera input is used on the layout input and then brought on screen, I want that to trigger the SetLayer function on the Text Input, so that the layers I specify get loaded with the text I specify.

However, since the camera input is a layer on the layout input, the trigger that I put on the camera input never fires, even when the layout using it goes to program.

What's interesting to me is that despite this somewhat expected but unfortunate behavior, automixing still works. When you put the layout to program that has the camera on it as a layer, the camera's audio will unmute if you've turned on automixing. So in that case vMix DOES see the camera go to program, but it doesn't see it when it comes to triggers.
nikosman88  
#6 Posted : Wednesday, March 5, 2025 2:01:14 AM(UTC)
nikosman88

Rank: Advanced Member

Groups: Registered
Joined: 12/24/2021(UTC)
Posts: 622
Greece
Location: athens

Thanks: 151 times
Was thanked: 84 time(s) in 80 post(s)
Hi. Maybe a companion trigger can do what you need. Make a trigger like "on condition becoming true"-->internal-->check variable and as variable use the layer name for example "$(vmix:input_cameras_layer_1_name)" operation= "your camera name" and when this true-->do the action
knbPixels  
#7 Posted : Wednesday, March 5, 2025 2:08:04 AM(UTC)
knbPixels

Rank: Advanced Member

Groups: Registered
Joined: 2/7/2024(UTC)
Posts: 99
United States

Thanks: 10 times
Was thanked: 5 time(s) in 5 post(s)
Originally Posted by: nikosman88 Go to Quoted Post
Hi. Maybe a companion trigger can do what you need. Make a trigger like "on condition becoming true"-->internal-->check variable and as variable use the layer name for example "$(vmix:input_cameras_layer_1_name)" operation= "your camera name" and when this true-->do the action


So that would work regardless of if the input containing the layer is on air or not. So it doesn't really replicate the functionality of watching the program state and performing an action when an input is on a layer taken to program.
nikosman88  
#8 Posted : Wednesday, March 5, 2025 3:08:02 AM(UTC)
nikosman88

Rank: Advanced Member

Groups: Registered
Joined: 12/24/2021(UTC)
Posts: 622
Greece
Location: athens

Thanks: 151 times
Was thanked: 84 time(s) in 80 post(s)
Originally Posted by: knbPixels Go to Quoted Post
Originally Posted by: nikosman88 Go to Quoted Post
Hi. Maybe a companion trigger can do what you need. Make a trigger like "on condition becoming true"-->internal-->check variable and as variable use the layer name for example "$(vmix:input_cameras_layer_1_name)" operation= "your camera name" and when this true-->do the action


So that would work regardless of if the input containing the layer is on air or not. So it doesn't really replicate the functionality of watching the program state and performing an action when an input is on a layer taken to program.

Yes and you can do combinations like this when happen and/or your layout is on air to do the action
knbPixels  
#9 Posted : Wednesday, March 5, 2025 2:14:38 PM(UTC)
knbPixels

Rank: Advanced Member

Groups: Registered
Joined: 2/7/2024(UTC)
Posts: 99
United States

Thanks: 10 times
Was thanked: 5 time(s) in 5 post(s)
Originally Posted by: nikosman88 Go to Quoted Post
Originally Posted by: knbPixels Go to Quoted Post
Originally Posted by: nikosman88 Go to Quoted Post
Hi. Maybe a companion trigger can do what you need. Make a trigger like "on condition becoming true"-->internal-->check variable and as variable use the layer name for example "$(vmix:input_cameras_layer_1_name)" operation= "your camera name" and when this true-->do the action


So that would work regardless of if the input containing the layer is on air or not. So it doesn't really replicate the functionality of watching the program state and performing an action when an input is on a layer taken to program.

Yes and you can do combinations like this when happen and/or your layout is on air to do the action



I appreciate your trying to help, but trust me. My show is extremely complicated and just watching to see if an input is on a layer is nowhere near as simple as watching to see if an input is on a layer on program. I'm not going to go into all the ways that this feature would help me but it would be massive.
mavik  
#10 Posted : Thursday, March 6, 2025 12:58:43 AM(UTC)
mavik

Rank: Advanced Member

Groups: Registered
Joined: 4/23/2017(UTC)
Posts: 1,273
Man
Location: Germany

Thanks: 3 times
Was thanked: 173 time(s) in 155 post(s)
last resort is to get into scripting. There you can do conditional actions.
nikosman88  
#11 Posted : Thursday, March 6, 2025 5:23:30 AM(UTC)
nikosman88

Rank: Advanced Member

Groups: Registered
Joined: 12/24/2021(UTC)
Posts: 622
Greece
Location: athens

Thanks: 151 times
Was thanked: 84 time(s) in 80 post(s)
Originally Posted by: mavik Go to Quoted Post
last resort is to get into scripting. There you can do conditional actions.


Personally i think for actions like described the companion triggers and variables are more flexible
Roy Sinclair  
#12 Posted : Thursday, March 6, 2025 9:05:23 AM(UTC)
Roy Sinclair

Rank: Advanced Member

Groups: Registered
Joined: 11/23/2020(UTC)
Posts: 196
United States
Location: Wichita

Thanks: 11 times
Was thanked: 26 time(s) in 22 post(s)
Originally Posted by: knbPixels Go to Quoted Post
Originally Posted by: dmwkr Go to Quoted Post
Don't know what you are trying to accomplish, but layers can also be used on input A itself (including a virtual input of A), and (de)activated as needed.



Ok so here's an example.

There's a camera input, a layout that uses that camera input on a layer, and a third input where I want to load various titles on the layers (not speaker titles, just text title inputs). We will call that third input "Text Input".


What I want to happen, is when the camera input is used on the layout input and then brought on screen, I want that to trigger the SetLayer function on the Text Input, so that the layers I specify get loaded with the text I specify.

However, since the camera input is a layer on the layout input, the trigger that I put on the camera input never fires, even when the layout using it goes to program.

What's interesting to me is that despite this somewhat expected but unfortunate behavior, automixing still works. When you put the layout to program that has the camera on it as a layer, the camera's audio will unmute if you've turned on automixing. So in that case vMix DOES see the camera go to program, but it doesn't see it when it comes to triggers.


Use a MIX input. You can create triggers that are applied when an input is used in a MIX. So if your multilayer page uses a mix as an input you can set up the trigger so it is run when that input is made LIVE in that mix.
knbPixels  
#13 Posted : Thursday, March 6, 2025 9:06:33 AM(UTC)
knbPixels

Rank: Advanced Member

Groups: Registered
Joined: 2/7/2024(UTC)
Posts: 99
United States

Thanks: 10 times
Was thanked: 5 time(s) in 5 post(s)
Originally Posted by: Roy Sinclair Go to Quoted Post
Originally Posted by: knbPixels Go to Quoted Post
Originally Posted by: dmwkr Go to Quoted Post
Don't know what you are trying to accomplish, but layers can also be used on input A itself (including a virtual input of A), and (de)activated as needed.



Ok so here's an example.

There's a camera input, a layout that uses that camera input on a layer, and a third input where I want to load various titles on the layers (not speaker titles, just text title inputs). We will call that third input "Text Input".


What I want to happen, is when the camera input is used on the layout input and then brought on screen, I want that to trigger the SetLayer function on the Text Input, so that the layers I specify get loaded with the text I specify.

However, since the camera input is a layer on the layout input, the trigger that I put on the camera input never fires, even when the layout using it goes to program.

What's interesting to me is that despite this somewhat expected but unfortunate behavior, automixing still works. When you put the layout to program that has the camera on it as a layer, the camera's audio will unmute if you've turned on automixing. So in that case vMix DOES see the camera go to program, but it doesn't see it when it comes to triggers.


Use a MIX input. You can create triggers that are applied when an input is used in a MIX. So if your multilayer page uses a mix as an input you can set up the trigger so it is run when that input is made LIVE in that mix.


Tried that, triggers still didn't fire.
nikosman88  
#14 Posted : Thursday, March 6, 2025 11:46:17 AM(UTC)
nikosman88

Rank: Advanced Member

Groups: Registered
Joined: 12/24/2021(UTC)
Posts: 622
Greece
Location: athens

Thanks: 151 times
Was thanked: 84 time(s) in 80 post(s)
Originally Posted by: knbPixels Go to Quoted Post
Originally Posted by: dmwkr Go to Quoted Post
Don't know what you are trying to accomplish, but layers can also be used on input A itself (including a virtual input of A), and (de)activated as needed.



Ok so here's an example.

There's a camera input, a layout that uses that camera input on a layer, and a third input where I want to load various titles on the layers (not speaker titles, just text title inputs). We will call that third input "Text Input".


What I want to happen, is when the camera input is used on the layout input and then brought on screen, I want that to trigger the SetLayer function on the Text Input, so that the layers I specify get loaded with the text I specify.


If i understand well what you need,still believe that companion is very easy to do. A trigger like this LAYOUT.png (2,459kb) downloaded 1 time(s). will do the trick. Or scripting in same logic
Originally Posted by: knbPixels Go to Quoted Post

I appreciate your trying to help, but trust me. My show is extremely complicated and just watching to see if an input is on a layer is nowhere near as simple as watching to see if an input is on a layer on program. I'm not going to go into all the ways that this feature would help me but it would be massive.

You dont need to watch if the specific input is on the layer,because that why it is called trigger. Companion will watch it (in a way pretty much like vmix watches the internal triggers) and if condition matches it will do the action

As for the feature request. Personally i also need some things for my workflow but until then,im trying to do workarounds
Mayberry3  
#15 Posted : Tuesday, April 1, 2025 3:35:10 PM(UTC)
Mayberry3

Rank: Newbie

Groups: Registered
Joined: 4/1/2025(UTC)
Posts: 1
East Timor

I'm using Rails and it does not provide support for database specific actions like triggers, stored procedures and various constraints (not all of them).


Osceola County Property Appraiser
Users browsing this topic
Guest
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.