Super basic instructions for Voicemeeter and digi mode software audio connections

[w-u-2-o]

This should work for most any common ham software that needs to move audio to/from Thetis/PowerSDR. These are the most basic settings. There are layers and layers beneath this for various tweaks. But this should at least get you to square one: audio moving reliably between Thetis/PowerSDR and such app's as WSJT-X, Fldigi, VarAC, etc.

For this to work you need to be running either Voicemeeter Banana or Voicemeeter Potato, not the base Voicemeeter version.

Step 1: Install Voicemeeter Banana or Potato. The only difference between them is the number of audio channels supported.

https://vb-audio.com/Voicemeeter/banana.htm
https://vb-audio.com/Voicemeeter/potato.htm

Step 2: REBOOT!

Step 3: Make every virtual audio device installed by Voicemeeter run at 48KHz. This is IMPORTANT!

Go to the Windows Sound Control panel. Open EVERY Voicemeeter related device in turn on both the playback and recording tabs, select the advanced tab, and set it to 48KHz, 2 channel mode. 16 or 24 bits doesn't matter, choose one.

Example screen shot:

Capture.JPG (62.03 KiB) Viewed 27345 times

Step 4: Configure Voicemeeter and PowerSDR/Thetis.

Run Voicemeeter FIRST. Then start PowerSDR/Thetis.

You need to assign Thetis to one Voicemeeter virtual channel, and WSJT-X to a different Voicemeeter virtual channel, then connect them to each other in Voicemeeter. You only need to do this once, Voicemeeter will remember. You can also go into the Voicemeeter settings and set it to run on startup, this will help you not forget to run it FIRST.

1. In Voicemeeter, click the A1 Hardware Output button and assign it to your default PC speaker audio output.

2. In PowerSDR/Thetis, assign the Voicemeeter VAIO channel to both the VAC1 input and output. Use the MME driver. Turn stereo on. Select 48KHz sample rate. Make the buffer size 2048. Leave the four manual boxes unchecked. Leave all gains at 0dB.

3. In your digi mode program (e.g. WSJT-X) assign the Voicemeeter Aux channel for both input and output.

4. In Voicemeeter click the "send" buttons (marked A1 through B2 or B3, depending on the version) as follows:

a) On the Voicemeeter VAIO channel click the B2 button, this will send audio from PowerSDR/Thetis to WSJT-X.
b) On the Voicemeeter Aux channel click the B1 button, this will send audio from WSJT-X to PowerSDR/Thetis.

5. Leave all other buttons in Voicemeeter OFF. Leave all Voicemeeter volume sliders at the default 0dB.

6. In PowerSDR/Thetis enable VAC1

This should get you basic audio functionality running.

[rbanasik]

Hi Scott.
Is it possible to use VMPotato with the mic and headphones plugged into the G2, or must they be directly connected to the PC? I am hoping to use VM only to avail audio of a minor amount of reverb with all other processing done in Thetis. I've noted that cmASIO works only with external devices, so could you recommend an appropriate asio driver?
Thanks.
-- Bob - Ki1n

[w-u-2-o]

To use Voicemeeter all audio devices must be connected to the PC. Anything connected to the ANAN can only be accessed by Thetis or piHPSDR, Windows has no way to see or access devices plugged directly into the ANAN.

[rbanasik]

Scott.
Thanks so much for clarifying that. I was suspecting that was the case. Any one ASIO driver preferred?
-- Bob - Ki1n

[ab7r]

I NEED HELP!

This voicemeeter stuff has me going in circles.

I am following these steps but run into a couple gotchas that is keeping it from working.

Step
4-1 Done but no sound from speakers.

4-2 I don't have a VAIO channel for both input and output. (see pics)

4-3 Only have option for VM Aux input for the output. No such option on the input. (JTDX)

Just tried something. MMe was not giving any results. I changed to ASIO driver in Thetis and bam....using VM Virtual ASIO in both input and output.

But still nothing from computer speakers.

Thanks
Greg

thetis banana.jpg (40.81 KiB) Viewed 13213 times

thetis output banana.jpg (46.78 KiB) Viewed 13213 times

VM Banana settings.jpg (139.93 KiB) Viewed 13213 times

[w-u-2-o]

Greg--immediately seeing a couple of problems.

First, it would appear you installed Voicemeeter Potato. I can tell because I see a "VAIO3" devices in the list. When Potato gets installed it also installs Banana and the base Voicemeeter versions. I don't know why, but it does, and it can be confusing. So make sure that you are running the Potato x64 version and not any other.

Second, Voicemeeter device names are extremely confusing. They even change with driver selection. So don't feel bad about picking the wrong ones, which is what your main problem is. Don't use ASIO without an ASIO audio interface available. With the MME driver selected, and using the second "B2" virtual channel in Potato for Thetis, you want to select "Voicemeeter Out B2" for Thetis VAC Input, and "Voicemeeter Aux Input" for Thetis VAC Output.

If you'd like to listen to receiver audio via your PC speakers, then you need to activate the route from B2 to A1. That's as simple as activating the A1 button on channel B2 (the Thetis channel).

I'm going to assume you have similar issues in JTDX. Use "Voicemeeter Out B1" and "Voicemeeter Input" there.

Yes, the naming conventions in Voicemeeter are stupid. No argument from me! But it's a great bit of software, nonetheless.

[ab7r]

Thanks for the help! I seem to have it working but with the asio driver. Made a dozen contacts today that way. Later I will try MME as you say to see if it works that way for me.

Thanks again
Greg

[ab7r]

And... merry Christmas!

[w-u-2-o]

Glad you got it going.

If it's working with ASIO definitely stick with that. There's far less latency.

[ab7r]

had to put checks in the buffer latency manual boxes for asio to work.

[w-u-2-o]

You can try shaving down those values to see how low you can get them and still have good, solid audio.

[N7KD]

I am having trouble getting WSJT-X to work with Thetis v2.10.3.6 and WSJT-X. My Radio Settings in WSJT-X are good since the Test CAT and Test PTT both do what they are supposed to. The receive level meter in WSJT-X shows no signal. There is also no audio on transmit, just a solid tone. Here are screenshots of my settings for Thetis Audio, VMB and WSJT-X Audio.

WSJT_AudioSettings.png (36.05 KiB) Viewed 12531 times

VMB_Shot.png (160.32 KiB) Viewed 12531 times

ThetisSettings.png (65.77 KiB) Viewed 12531 times

Any help would be appreciated.

[w-u-2-o]

In Voicemeeter put your B1 and B2 master faders back up to 0 dB.

In Thetis VAC set the output to "Voicemeeter Input".

[N7KD]

B1 and B2 faders at 0dB. Now receiving in WSJT-X with both VAC and WSJT-X input settings at Voicemeeter Out B1.

Both VAC and WSJT-X output settings now at Voicemeeter Input (VB Audio etc etc). Monitoring output of first virtual input by selecting A1 I can hear the WSJT-X audio in the A1 speaker output signal shown in Thetis spectrum display only when first virtual input set to B1 output the same as the second virtual input. In the examples given, one of the virtual inputs was supposed to be set to B1 and the other to B2. So this appears to work (I had a QSO with KK7IEU) but the settings are not what was expected. ???

It is almost as if Voicemeeter was deliberately designed to be difficult to understand.

[w-u-2-o]

B1 and B2 faders at 0dB.

Good!

...both VAC and WSJT-X input settings at Voicemeeter Out B1.

Wrong! You made more changes than I specified

There's more than one way to skin a cat, but the "proper" way to set this up is to have WSJT-X assigned to one virtual channel for input and output, and Thetis assigned to other virtual channel. Then all mixing and routing is done in Voicemeeter. In this most basic of cases, never assign the same Voicemeeter input or output to both programs.

Change your B1 and B2 routes (aka "sends") back to the way they were. Deselect A1 on all channels for now (you can reselect it later). Reassign WSJT-X Output back to "Voicemeeter AUX Input".

It is almost as if Voicemeeter was deliberately designed to be difficult to understand.

For those who understand audio mixing boards Voicemeeter is quite straightforward, EXCEPT for the INCREDIBLY confusing naming conventions on the "B" series of "virtual" channels

When looking at Voicemeeter you have only a single virtual channel, "B1", so that's easy.

When looking at Voicemeeter Banana, which is what you are using, there are two virtual channels. B1 shows up with either "B1" in the name or simply "Input" in the name. B2 shows up with either "B2"in the name or "AUX" in the name.

When looking at Voicemeeter Potato there are three virtual channels, the third being "B3". B3 shows up with either "B3" in the name or "VAIO3" in the name.

Yes, it's a stupid, confusing, annoying naming convention. But other than that the program is fantastic.

[N7KD]

OK so now Virtual Channel 1 (Voicemeeter Out B2) routed to B1 and Virtual Channel 2 (Voicemeeter AUX Input) routed to B2. Everything still works. Still trying to wrap my head around this.

[w-u-2-o]

https://www.youtube.com/results?search_query=voicemeeter+tutorial

Enjoy with your favorite beverage!

[N7KD]

Still an issue if set up the way you suggest. You said the "'proper' way to set this up is to have WSJT-X assigned to one virtual channel for input and output, and Thetis assigned to other virtual channel. Then all mixing and routing is done in Voicemeeter." This does not seem possible since I don't see how both input and output of WSJT-X or both input and Output of Thetis can be routed to the same Virtual Channel. Such choices are not available in the pulldown menus.

The settings of both WSJT-X and Thetis have "Voicemeeter AUX Input" as "Output" so both are sending audio to the second Virtual Input in Voicemeeter so both WSJT-X and Thetis are sending output to the same Virtual Input not to different ones as you stated. The settings of both WSJT-X and Thetis have "Voicemeeter Out B2" as "Input". So the Inputs of both WSJT-X and Thetis are being sent to the same first Virtual Input and that seems to violate what you said, but WSJT-X works with these settings.

If I turn off the B1 output bus routing of the first virtual channel so its output is not routed anywhere, both receive and transmit still work. The first virtual channel does not seem to be doing anything.

Maybe my thought process here can help you figure out what I am missing or not understanding.

[w-u-2-o]

I took a few figures out of the Voicemeeter Potato manual (available on the VB Audio website) and marked them up to try to illustrate the audio paths for you. Please carefully note the names of the devices as shown are for the MME driver and will change slightly when using other drivers (yes, there's that nasty naming convention thing again).

Does this help at all?

Voicemeeter Setup.png (652.82 KiB) Viewed 12399 times

[N7KD]

It may help but the diagram you sent shows that WSJT-X Input in WSJT-X Audio Settings is connected to something called "Voicemeeter AUX Output". Unfortunately there is nothing with that name in my Windows 11 Sound Control Panel or in the WSJT-X Audio Settings Input pulldown menu. Right now I have the WSJT-X Input in WSJT-X Audio Settings connected to Voicemeeter Output but this is the same as the Thetis Audio Input Setting choice. No audio is getting to the WSJT-X application but the audio from the radio is going to my speakers and there is nothing in VMB that controls it.

[N7KD]

The labeling of the Voicemeeter Ins and Outs is terribly misleading. Here is what actually works.

Thetis Audio Settings:

Input: Voicemeeter Out B1
Output: Voicemeeter In 2 (why this works instead of "Voicemeeter In" remains a mystery to me)

WSJT-X Audio Settings:

Input: Voicemeeter Out B2
Output: Voicemeeter AUX Input

The Voicemeeter manual illustrations you sent to me conveniently omit the B1 and B2 suffixes which are necessary in choosing the correct outputs. I kept trying to do what the manual incorrectly showed.

Please accept my extreme gratitude for your help.

[N7KD]

One thing leads to another. Now that I got WSJT-X and fldigi working using Voicemeeter, I can no longer use single sideband on the G2 since I can't get the microphone plugged into the XLR connector on the back of the G2 to deliver audio. Nothing in the hardware setup has changed except for putting Voicemeeter into the mix for the digital modes.

I tried to make a new settings profile by using a new database but can't figure out how to get mic output from the G2 to drive transmit audio in Thetis.

[w-u-2-o]

I don't have a G2, so I'm at a little bit of a disadvantage. However, step 1 is to disable VAC in Thetis, step 2 would be to enable the balanced mic input in both Thetis and p2app.