Tim explains it (again) ;-)

"I want this"
"This is not possible, by design, as intended"
"But I want it, cause else I have to do it by hand."

It seems you are locked in your approach of the desired outcome. Since it is vMix the trick is to realize your outcome can probably be achieved by using a different approach or route.
And though lately the first response of many people in that situation seems to 'demand a new feature', wouldn't it be great if instead of waiting till they grow old, they grew as a person and operator?

First step is to accept there might be a very good reason why things are even like this. (This really works out in life in general).
You said you watched the video, let's point to the relevant point you might have missed :
- One important thing to note
- no automatic functions
For example in this case ​the possible confusion that transitions in your mix-input can influence the behavior of the input while it is used in your main mix.
Undesirable outcome averted, by making it not too easy to eff stuff up.
Let's make some effort to achieve that !

So that is why this feature is not there, if you want a better answer, all I can do is transcript Tim from the video around the second or third time he mentioned shortcuts ​:
"You gonna have to sit down and think about how you are going to control the inputs when you are using them as a part of a Mix-input."

As in "you" have to put in the work.
" It's not that it is not possible,
it is just not possible the way you want."


Well shortcuts (and triggers) are usually set for inputs, and assuming you want to start the video that you have as a separate input?
But since you saw the video you also caught the mention of shortcuts and triggers having a mix-numbers?
So you can even target your Mix-input with shortcuts.
That's the spirit, well at least half of it !

More in general I reckon this is not so much a well designed and thought out Feature Request as a simple first cry for help in starting out with shortcuts.
Though I guess that goes for a lot of these feature requests I see lately.

A feature request is not something that will be picked up and implemented in days or weeks ( or even years if it's a bad one ).
Thinking that creating a (minimal, short, unfounded & incomplete) feature request will solve a persons little own hill they are not willing to take an hour to solve is saying a lot on how people approach their use of vMix and this forum.
And though I (honestly) would love a trigger on Mix-inputs [ OnMixInputTransition or something to that order ] I think getting to a solution that will help me out today is a lot more gratifying then a FR topic.

[/rant over]

• What do you want to achieve by using a mix input?
  
• How do you use this Mix input, back into your mainMix or out to a separate output/fullscreen.
  
• Are you using 4 separate video inputs , or a video list with 4 video's ?

Quick throw at what you possibly might want to achieve with your shortcuts :
- Select a input as preview for your Mix-input.
- Play the video
- Transition the Mixinput to get your video input shown
( or if you get really nifty, get dynamic inputs involved )

Pretty sure I have no problem, though without a solution you apparently do ?

Without any kind of relevant context besides "I need this" (which sums up the opening post) no single relevant reply is possible.
Neither is design & implementation of a new feature without a proper understatement of what it is you are not able to do.

But sure, no lessons. No problem, it's your party!
Good luck growing old ! :) Lighten up, it helps.

be creative ;-)

https://forums.vmix.com/...ng-for-Dummies#post99504

I think I largely agree with you as well, and there indeed should always be room for proper formulated feature requests.

But let me summarize my feeling on this thread: "It's not necessarily a bad feature, but it sure as hell is a lousy request."
I think this topic doesn't even come close to something that would be considered something a useful feature request could or should be.

And luckily you just provided a pretty decent example yourself.
I probably don't have to mention on how many points this topic and yours differentiate from each other.
(Though while I'd gladly be of service, I'm pretty sure it won't be appreciated).

Obviously some people just want to vent (noticed that in a different topic on v25 as well) and sit back and wait.
I just had a go at the suggested workaround from doggy ( which as usual is more elegant then my crude sequence of functions ) .
But apparently the spoonfed workaround is as much appreciated as my constructive breakdown of the usefulness of the starterpost.

To everyone his own I guess, though that may cause some backlash from differentiated opinions and feedback might be expected.

While i do not always explicitly mention it but when i post a solution (scipt or whatever) that can cover (or part) the current FR it should be taken as "untill FR is implemented" this can help you out in the mean time.

But it often appears that a solution is not always wanted ( sure i want this , give, give it to me until you ask for a beer) and +1's are easely given just like a child wants a toy to never look back at.

As vMix says; explain your FR properly, wel though of and how you envision its use and not just as a "I need this". such properly formulated requests have had succes in the last decade! and no , adding a button is not always as easy as it sounds (wel the button itself is , not the workings behind it )

0.2c

You're still ignoring the explicitly stated reason for the behavior you want changed.

I'm done trying to help you.

You came in with a request that will be ignored, because it brings no ideas to the table & merely presents an already defeated position.

When people, myself included, pointed that out to you, rather than go back to the drawing board (or merely sign onto my request that adapted yours into something that'll do pretty much exactly what you want in the way you want to do it, but with a chance of actually working out), you're digging in your heels and saying "Well, Martin can always ignore me".

He almost definitely will.

If decisions are influenced by the number of users in agreement, he'll almost definitely ignore mine too.

But, unlike you, I know that I actually did my best in presenting a well-thought out idea that accounts for decisions that have already been made & the logic behind them, rather than just throwing stuff at the wall to see what sticks with a massive "I don't care" attitude.





Personally, I can appreciate that, and I think it's definitely helpful to provide a stop-gap if one is known.

It wasn't necessarily you that I was referring to either.

I could also be completely off-base in my reading, as I mentioned, and everyone could be implying the same. Tone among strangers with the written word is difficult, to say the least.

Spino,
Did you try to "create virtual input"?

ok, it should be clear by now that vMix is reluctant to grant this FR (for now) for reasons stated in the video for one.

Regarding the use of shortcuts to do what you want the video also explains how this can be done partially and a (base) working script was given to fulfill your request for automation of (original post): or as is mentioned just here above

FWIW: a script can be called like a function with a shortcut or constantly check a situation and be turned on or off

We all know it never hurts to do a FR (well argumented ones) but most of us know when to accept facts too and get on with what is currently available until the FR fairy grants our wish

Ok doggy, I accept your arguments, your replay is written in an acceptable way. What I don't accept are some replays like life lesson.