Anan 200D FT8 config

[qst]

Hi,
I want to configure my Anan 200D to work with FT8 with WSJTX. Are virtual ports necessary? I also saw a video where a friend installed the Banana Audio Voice Meter. Is that necessary? I have a Universal Audio Apollo audio interface.

Slawomir

[w-u-2-o]

You are not configuring your 200D so much as you are configuring your PC and Thetis.

You will not need any virtual serial cables. You can make the connection using TCP/IP.

Here is an example for N1MM logger: viewtopic.php?f=16&t=4065&p=18275

Anything with Hamlib works great. That includes WSJT-X, Fldigi, JS8, etc. In any Hamlib enabled software (again, like WSJT-X), type into the port setting box IP:port, e.g. "127.0.0.1:1800", or whatever you've got Thetis set to. So right where it says "COM10" or the like, just type right over the top of it.

For audio you will need some sort of audio virtual cable software. You can use VB Matrix, Voicemeeter, or the original Muzychenko VAC application.

There are plenty of examples of how to do this on YouTube. Here is just one example (you can ignore the serial port stuff, use the TCP/IP connection as described above).

[qst]

Hi,
Unfortunately, I'm still having audio issues. After installing Voice Meter Banana, a conflict arose with the Apollo Twin X4 Thunderbolt ASIO driver. I had to uninstall VM Banana and reinstall the Uaudio ASIO driver. The next problem is that there's no audio whatsoever in the Thetis Audio/VAC tab. It's blank, and there's no driver visible. I think I need to configure FT8 on a Flex-6700 or Kenwood TS-990S. I'll look for another solution on the Anan 200D, but I don't want to uninstall my Apollo interface.

Slawomir

[w-u-2-o]

There should be no conflict with your Apollo interface. I recommend reaching out to the VB Audio community here, https://forum.vb-audio.com/, or here https://discord.gg/XS6JFA6b.

Once you get your Voicemeeter/Apollo problem solved, come back to this topic and we can get you going with Thetis.

[qst]

Thanks for the reply. I restored the Apollo driver and it's working in Windows. It's also visible in my DAW. I still have an internal audio card in my computer. Why don't I see any drivers in the VAC tab? Is this a misconfiguration of the Thetis?

[w-u-2-o]

If you are using cmASIO then the ASIO drivers won't be available in the Thetis VAC setup.

If you are not using cmASIO then you should see all the ASIO drivers from Voicemeeter and the Apollo.

Also, in Voicemeeter, make certain that the Apollo is selected as Hardware Output A1. This will cause Voicemeeter to obtain it's timing from the Apollo.

[qst]

The issue has now been resolved. I installed the new version of Thetis without uninstalling the previous one, and it became a mess. Now the audio drivers are visible. I'll try using VAC with Flexradio, since DAXes are also virtual cables. I now have a clear field for experimentation. Thanks for the support.

[qst]

I rejoiced too soon. When I installed the Asio Uaudio Thunderbolt drivers in VAC1 and VAC2, I got a blue screen of death, and after restarting, the audio drivers were no longer listed in the VAC window.

[w-u-2-o]

I rejoiced too soon. When I installed the Asio Uaudio Thunderbolt drivers in VAC1 and VAC2, I got a blue screen of death, and after restarting, the audio drivers were no longer listed in the VAC window.

Is there any other software (a DAW, for instance) that is using the same Apollo driver (device)? An ASIO device, like the Apollo, can only attach to a single software application at a time.

The solution to this problem is to use either one of the Voicemeeter app's, or the VB Audio Matrix app, to route the Apollo to multiple app's at the same time.

[qst]

But the problem is a bug in Thetis, because again, no audio drivers appear in the VAC1 and VAC2 windows. The field is clear. After a fresh installation of v.2.10.3.12, the audio drivers were visible in the window. How can I fix this? I uninstalled Thetis 2.10.3.12 according to the procedure, and then reinstalled it. Unfortunately, the drivers are not visible. Could this be a bug in the data base manager?

[qst]

I reinstalled Thetis 2.10.3.12. Immediately after launching, the audio divers appeared in the VAC window. But after restarting the computer, they disappeared. I can't find the cause of this error.

[w-u-2-o]

I reinstalled Thetis 2.10.3.12. Immediately after launching, the audio divers appeared in the VAC window. But after restarting the computer, they disappeared. I can't find the cause of this error.

It doesn't seem like a Thetis bug, as otherwise there would be a lot of people reporting this behavior.

Are you using a completely new database? If not, please try this with a default database where the only change is selecting the 200D model type.

[qst]

I'm using the old database because after installing the new version of Thetis, I already had the skin and all other settings. I thought I'd have to reconfigure the skin, meters, etc. after the new installation. It's strange that when I start Thetis by pressing the POWER button, the TUN, MOX, and 2TON windows are dim. They only light up brightly after turning on the POWER button. How do I enable the default database?

[qst]

I changed the database to the default one, and there are still no drivers in the VAC window. The TUN, MOX, and 2TON windows are also blank when Theyis starts. Everything else works fine. Until I resolve this issue, I won't be able to configure FT8 on the Anan 200D.

[qst]

Problem solved. In Win10, I had three DAWs. Two of them had their own ASIO drivers. I uninstalled those DAWs, and the number of audio drivers decreased. Only Universal Audio ASIO and a few Windows drivers remained. Now all audio drivers load into Thetis and are visible. Thank you for your support. Slawomir

[w-u-2-o]

Wow, that's a lot of DAWs!

[qst]

Qubase and FL-Studio.
Now I want to configure FT8. Do I absolutely need virtual cables in the VAC1 and VAC2 windows? If I have an Apollo Uaudio and the ASIO drivers are installed, isn't that enough? I wanted to use the Flexradio DAX I have in my system, but the configuration didn't work. Does anyone know if anyone is working with Thetis on FT8 using DAX? As a last resort, I'll use VAC Muzychenko,
Slawomir

[Trucker]

DAX from Flex Radio isn't compatible with Thetis. The suggestion to use VAC is your best option.
James
WD5GWY

[qst]

So, all I have to do is install Voicemeeter Banana. In addition to VM Banana, do I need to install VB Audio Virtual Cable? If so, which one?

[K1LSB]

I've been using VM Potato with Extensions for years, I can't imagine needing any additional virtual cables.

Mark

[K1LSB]

I've been using VM Potato with Extensions for years, I can't imagine needing any additional virtual cables.

Mark

Edit: I don't use WSJTX but I do use fldigi. And I don't use VAC, everything goes through cmASIO. But that's just how I've got my Potato set up, everyone's setup will be different.

[w-u-2-o]

The problem that (I assume ) you want to solve is to connect two ASIO devices (Apollo and Thetis) along with an MME device (WSJT-X, or most any other digi mode software) all together and control which audio goes where. For this you need a software version of an audio mixer that can accept those three sets of inputs and outputs simultaneously. AFAIK, only Voicemeeter can do this. Or you need an software version of an audio crossbar switch that can do the same. AFAIK, only VB Audio Matrix can do this.

You might, and I stress "might", be able to use the Uaudio application by itself to do that, but I do not know enough about it to say definitely.

The ASIO drivers for the Apollo are in support of Uaudio, Voicemeeter, etc. By themselves they are not enough.

I do know that you need something that is equivalent to Voicemeeter, and that Voicemeeter will work to do what you want.

Voicemeeter comes in three variants, plain, Banana, and Potato. I recommend you install Potato, as it has the most number of channels available and you seem to have a complex setup that might benefit from that.

If you are familiar with professional audio mixers then Voicemeeter should not be too much of a learning curve. If you are not, then prepare to watch some Voicemeeter tutorials on YouTube.

I recommend connections as follows:

- Apollo ASIO speaker output to Voicemeeter Hardware Output A1 (do this first, as it will cause Voicemeeter to take on the Apollo settings for sample rate, etc.)
- Apollo mic input to Voicemeeter Hardware Input 1
- Thetis VAC ASIO input to Voicemeeter Virtual ASIO (channel strip B1--yeah, the Voicemeeter naming conventions are TERRIBLE)
- Thetis VAC ASIO output to Voicemeeter Virtual ASIO (channel strip B1)
- WSJT-X input to Voicemeeter Out B2 (channel strip B2)
- WSJT-X output to Voicemeeter In 2 (channel strip B2)

Then simply operate the mixer send (aka patch, aka route) buttons to send audio from B1 to B2 and from B2 to B1 for digi stuff. You can route B1 to A1 to listen to the Thetis audio output. You can route A1 to B1 for mic audio to Thetis.

Another alternative is to use VB Audio Matrix and just patch the crossbar connections you want, rather than use Voicemeeter.

You can patch in a DAW using VB Audio Matrix (simple) or using the VAIO Insert Driver feature of Voicemeeter (not hard, but confusing at first).