What functionality do you need in your green room?

Relatively easy to achieve an audio-only version using a single audio bus.

There are more complex versions if you also want video (requires use of one output) and/or independent producer TalkBack (requires a second audio bus).

You need to do a bit more than this, but yes this is the general idea.

I mean, you'd need to make and put something on the video output & add the guest audio to the greenroom bus (both of which I thought were a given), but I can't think of anything else that'd need to be done, nor do I do anything else.

It's a script that takes maybe 10-15 minutes to write, and almost all that time is getting the code to add or remove people on the video output multiview.

Of course, it's a bit different if you want to send everyone a special greenroom without their own video being sent back to them on a delay (which I always find preferable) but when you have more than 2 callers, that's impossible with only 4 outputs. And with only 2 callers, having 2 separate outputs isn't all that more complex than just having one, because you no longer need to fiddle around with adding/removing callers on a multiview.

If you plan far enough ahead and think things out, you don't even need to use complex scripting to figure out where people are in the multiview, because you'll already know. Same goes for if you're taking them all out of the greenroom at once.

In those cases, or if you aren't putting callers' video in the greenroom at all, it's 1 or 2 basic web scripts (depending on what all you need to do) that can be knocked out in less than half that time.

Use a dynamic input and you can use the same script for every caller instead of needing 1 per.

The answer is, again, what was already written. There's no video necessary.

The exact same procedure you use to set up a vMix Call for production is how you set up a greenroom.

Callers get video from a vMix Output and they get audio from a vMix audio bus.

Set up the video output to give the caller(s) the video you want them to see in the greenroom, and set up the audio bus to give them the audio you want them to hear in the greenroom, just like how you set up the video output to give them the video you want them to see in the production & the audio bus to give them the audio you want them to hear in the production.

If you need a video telling you how to set up and use vMix Call for a production, I'm sure you can find one.

A greenroom is the the exact same thing.

vMix Call is extremely basic in what it can do, in regard to transmitting from vMix to the guest. It takes the video from a designated output and the audio from a designated bus and sends it to the person on the other end of the video call.

That's it. That's all it does with regard to transmitting from the vMix machine to the guest. No matter how hard you try, you will never get it to do anything different.

Whatever you're using it for needs to be done within those parameters.

Whether you're setting up a production or a "greenroom", the steps and procedures are exactly the same, because the extremely basic capabilities of the program are exactly the same.



This is an entirely unrelated discussion & it's also entirely outside the scope of vMix to teach.

The answer is "Stop refusing to do that".

The second answer is "If they refuse to wear headphones, learn the different types of microphone pickup patterns, proper gain control, proper placement of microphones and speakers, and proper EQ techniques". In other words, become a fully trained audio engineer.

If you need vMix to make a video to help you, the second answer is going to be way too difficult to achieve, and we're back to the first answer of "Use headphones & don't pair speakers with a microphone if you can help it" (which, by sheer coincidence, is also going to be the conclusion you'd reach if you became a fully trained audio engineer).

That second answer is what they do for things like concerts that require microphones and speakers for a live audience.

In cases like this, where headphones or IEMs or earpieces are a valid option, that's what's done.

If you want to do it the other way, you can.

But I can assure you that there's a reason nobody in broadcasting does it the other way unless they have to, and it's because the other way is a significantly larger PITA with a lot more room for error compared to the extremely simple option of "Just wear headphones".

And I can also assure you that Heath is probably never going to make a video teaching you audio engineering.

Personally, I'm loath to send anyone a video of themselves. If they're not expecting it, especially with a variable level of delay, it can throw people off, which you don't want in a live production.

So where I can (meaning 3 or fewer callers at a time) I make a greenroom (and production, where applicable) for each caller that includes the other callers' videos, but not their own (as well as anything else they need to see).

I default my Outputs 2-4 to Inputs 1-3, then I have a Mix devoted to each, to make it simpler.

As for audio, when you know what you're doing, it's not that complicated. And you need to know what you're doing to even set up the production in the first place.

It ultimately boils down to:

-Send people audio that you want them to hear
-Don't send people audio that you don't want them to hear.
-Send people's audio to people you want to hear them.
-Don't send people's audio to people you don't want to hear them.

With vMix handling mix-minus on caller buses automatically, it's something one doesn't need to worry about, and I get the feeling that it's something a lot of people aren't thinking about to begin with.

Even if vMix didn't do it, it'd increase complexity, but it still wouldn't be complicated, because it's as simple as "don't send people their own audio".

One of the most common complaints I've seen about vMix is that their audio setup is overly simplistic.

And it is.

While I'd also like some more advanced routing capabilities, I absolutely love that it's as simple as "Click the button with the letter on it and the audio goes there".

And that buses are defined during setup as output devices, and allow labeling, makes it even simpler. You don't even have to understand what a "bus" is. You just have to know that "When I click the letter A, the audio goes to the device I defined as the letter A."

And as long you know what the word "Source" means in the context of a "To Guest" feed, setting up a Call is just a simple. Again, you don't need to understand what a "bus" is. You just need to know that the guest will hear all of the audio being sent to the letter A.

Then, once you know that (which, again, is the level you should be at if you're using vMix to setup a production), it becomes a simple "If I send audio to the letter A, the person on the other end of the video call will hear it. If I don't send the audio to the letter A, the other person won't hear it."

And then, whatever that audio is, be it the production or a producer or another guest or hold music or whatever, if you send it to the letter A, it'll be heard by the person listening to the letter A by video call. If you don't, it won't. Figure out what you want them to hear, and, based on that, either send it to the letter A or don't.

And where you route the audio coming from the call is no different than how you route any other audio within in your production. Either you want it to go somewhere or you don't. Send it to the letters you want it to go, don't send it to the letters you don't want it to go. Do you want it to go to your headphones? Then click the letter that corresponds to your headphones. Do you want it to go to other guests? Then click the letter that other guests are listening to. And so on.

Same with things like automix. Do you want something to be muted in all the letters if it's not in the output? Turn automix on. Do you want it to be audible in at least one letter when it's not in the output? Turn automix off and set where it's audible by changing the letters.

Like I've said, I'm fully willing to admit that I've grown with vMix in a way that I can't put myself in the shoes of a new user.

But I genuinely cannot understand how people find this so difficult--especially when those people are presumably using this not-cheap software to run productions utilizing these same concepts.

And these demands for greenroom tutorials are even more baffling to me, because, by the time you get to that, you're not only presumably past the point where you've set up a production using these same concepts, but you've also presumably set up a call using these exact same concepts.

When I read these questions, to me they sound like "I've figured out how to set up video and audio routing to give a caller everything they need to see and hear during production. Now I need a tutorial for doing that exact same thing I've already done."

The only difference I can see is that the inputs default to muted when they're not in the output, but that's as simple as unmuting it and/or turning automix off.

Not quite this simple, which is why I include it, and forcing audio on or off, in the button presses between LIVE and GREENROOM.

If automix has previously been on before they go into Greenroom, and right before the button press they weren't on output, then their audio will be off. So, in order for them to be audible in the Greenroom, you need to force the audio on (as well as doing the bus routing to ensure they're not heard on output). However, if you leave automix on, then then next time you do a cut on output, they will no longer be heard in Greenroom because automix will have turned off their audio again.

Similarly, on the way back to LIVE, you need to turn back on automix, so that the next time they are cut to output, their audio comes on too. It's also a good idea to force off their audio, otherwise they could then be audible on output before they're visible.

I discovered it today and im trying the trial. When people are in their greenroom we can send them (if we have) a link from our stream so they can watch vmix output. When we pull them into vmix call the link changes to actual vmix output from vmixcall pc that we accepted the call. So yes as i see text messages is the way either per caller like pm them or general to all of them. Either way could be to send them a stream output from our vmix in testing vps server or CDN stream there our mic,so they can hear us when they are in callcontrol greenroom
The amazing thing is that per caller can be routed into different vmix machines/calls. So before me as guest be on the "air vmix call", they can route me into other vmix call pc and then send me in the main vmix pc,without the need from me,to have different vmixcall link/code!
So yes one can have Vmix HD version and if he needs in the show 3 callers,not the same time,can anyone of them,have link from controlapp, connect in controlapp greenroom anytime even all together and then we as producer can with the one same vmixcall link,put them in our production 1 by 1,without worrying that vmixcall will be interrupted

Easy enough to do. I knocked up a system for our company in a few hours. We customise a login page with client's branding, caller enters their name then sees whatever we've determined as a holding message - that could be some text and images, or a live video of the stream. We can then place any caller into any vMixCall number we determine. And can then put them back on hold or kick them off the system entirely.

No individual or global messaging on ours, but would be easy enough to add in.

Maybe we should release it and start changing $200 a year for external access?!

I read and re-read all the answers one by one.
Each one contains very useful information.
Thank you very much.

For myself,
I think I understood the audio data paths and audio routing correctly.

Actually my scenario is simple.
In the live broadcast,
I have vMix calls coming from two different cities at the same time.
I am the vMix operator and the moderator of the broadcast.
In other words, there are 3 people talking on the broadcast output screen.

I am using a HyperX Quadcast microphone.
Master Output is "none" and
Headphone Output is 3.5 mm headphone (for viewing if necessary)

I see the output video on the TV connected with HDMI and hear it from the TV with Bus C.
Guests listen to the broadcast with the master.
I can also do this with Bus A, Bus B for each guest.

Even if the sound in the room is on the TV away from the computer,
I think my microphone is taking the output broadcast sound and sending it back to the broadcast and the guests.

Before moving on to using headphones, as a last step,
I will try to manually turn my own microphone sound on and off (using shortcuts).

Turn it off when the guests are talking and I am silent,
Turn it on when I am talking.

(There is no problem when there is a broadcaster + a guest on the call.)

The most important part for me is to prevent the repetition in the sound, that is, the echo.

And I care a lot about being able to do this solution without using headphones.

Because I see that there are multiple broadcasters who can do this.

I don't know if they use web-based like Restream, Streamyard,

While I was a live broadcast guest in TV studios,
I have now decided to be a broadcaster myself from my own social media accounts.

After trying Obs, Piriszm Live Studio, Wirecast,
my choice was vMix 4K.

I apologize for this long message, many details of which concern only me.

But it was important to be able to explain myself correctly and learn correctly.

I would like to thank each and every one of you again.

Thank you very much for your answer.

I definitely take your advice very seriously.

As Bus C, I set the LG TV connected directly to my laptop with hdmi.

(webOS TV (NVIDIA High Definition Audio)

Also the default bus setting is Master.

All Guests receive the audio from the call as master.

I did not need to separate the guests into Bus A and Bus B.
They should all reach every audio and video going to the broadcast.

Output 1 goes to the guests and I use this TV as FullScreen to watch the broadcast live.

When I had only one guest on the broadcast, there was no echo even with the automatic gain microphone setting, but when the second guest joined, I had an echo problem.

If I think I absolutely cannot do it, I will switch directly to the headphones.

But as you can see,

If I have a chance, I want to try and learn.
:)

Thank you again for your understanding.