v0ttis wiki

This is my private wiki. It is also the home of my small “blog”.

For information about how to contact me please refer to my website.


Using Zoom (or in fact, any other video conferencing solution) together with vMix is not completely trivial. In this post I am going to explain how I do this with a single PC.

Of course one could use the built-in vMix Calls, which already handles a lot of things like N-1 audio routing, but there are quite some limitations.



You need the following software installed and running on your vMix machine:

Configure Zoom Client
  1. Start the Zoom Client and connect to the desired conference
  2. For the camera, select “NewTek NDI Video”
  3. For the microphone, select “Line (NewTek NDI Audio)”
  4. For the speaker, select “CABLE Input (VB-Audio Virtual Cable)”
Configure vMix and NDI
  1. Configure return audio bus
    1. Add a new audio bus in the vMix settings (you can use “Enabled” as the audio device)
    2. Add everything that is assigned to the master bus to the new audio bus
  2. Configure return video feed
    1. Activate NDI for an additional output (not Output 1 as we will use a different audio bus) in the vMix settings
    2. Using the cog icon, assign the newly created audio bus to this output
  3. Configure the NDI Virtual Input
    1. In the Windows taskbar tray, right click on the NDI Virtual Input icon
    2. Select the previously configured vMix output
  4. Configure screen capturing
    1. Add a new “NDI / Desktop Capture” input
    2. Select “Local Desktop Capture”, then select the Zoom client (“Zoom 2” in my case)
    3. As Window Capture Method, select “WindowsGraphicsCapture”
    4. Resize the Zoom window so it best fits your production aspect ratio
    5. Using the vMix input settings, you can now zoom into the window so it does not show any GUI elements anymore
  5. Configure the audio input
    1. Add a new “Audio Input” input
    2. Select “CABLE Output (VB-Audio Virtual Cable)”
    3. Assign the input to the master audio bus, but not the return feed audio bus

Optional Steps and Remarks

If you want to talk to your guests before you put them on air, remove their audio from the master bus and put them on your headphones using the “S” button. Create a new microphone input with your own microphone and assign it only to the return feed audio bus. Keep in mind to assign the guests back to the master bus and remove your microphone from the return bus before putting them on air.

It is recommended to keep the Zoom client on a dedicated screen.

2020/08/24 10:18 · v0tti

A few months ago Aruba introduced the MPSK authentication feature for their WiFi systems. With MPSK it is possible to have a PSK protected SSID but with a per device/MAC password. Unfortunately it is only officially supported to work with the Clearpass Policy Manager from Aruba. However, we figured out how to use it with the FreeRADIUS RADIUS Server.

Configure the SSID

From the WebUI, create a new SSID with MPSK authentication. It is not possible to select an existing RADIUS server, just create a new dummy server. Now, edit the SSID profile and now change the dummy server to your (previously configured) FreeRADIUS server.

Configure the FreeRADIUS Server

When a client connects the controller will send a RADIUS request to the server. In the response you have to include the vendor-specific attribute Aruba-MPSK-Passphrase. FreeRADIUS already includes this with correct encoding and encryption (check if your version already includes this VSA, otherwise place the linked file at /usr/share/freeRADIUS/dictionary.aruba (this applies to Debian)). Here is an configuration example, please note that “ClearTextPassphrase” is the clear text password for the requesting device: Aruba-MPSK-Passphrase := “ClearTextPassphrase”.

If you operate a proxying RADIUS, like we do, your config could look like this:

post-proxy {
     update proxy-reply {
          Aruba-MPSK-Passphrase := "%{proxy-reply:Tunnel-Password}"
Some Notes

Using MPSK without Clearpass is not officially supported and TAC probably won't help if any problem occurs. The controller will cache the password for a period of time (seems to be a couple of hours).

Most of the work explained here was done by Maximilian Graul at FeM, thanks!

If you have any feedback to this article, please let me know!

2020/02/29 15:36 · v0tti
  • start.txt
  • Last modified: 2020/06/29 14:11
  • by v0tti