ROTA-Radio

Why ROTA?

When I = 0 and O = 0

Today while working through my morning Checklist to get the Dell laptop set up for a digital modes session, I ran into some problems. I had already documented most of the problems right in the Checklist post itself. However, I had a longer session with Gemini AI that would have made the Checklist + add-on comments even more cumbersome. So, I decided to include the longer chat here instead. If you like, you can go back to the context for this chat by clicking on the Checklist link above.

My Question:

Good morning, Gemmi!

I’ve been updating this post: https://rotaradio.wordpress.com/2026/03/26/the-rota-remote-digital-master-checklist-windows-dell-edition/

And, I decided to follow the directions myself when I couldn’t get my Mk2 and Icom Remote Utility to talk properly to each other.

I ran into something I wanted to ask you about because it doesn’t make sense that my setup is working. Here’s the specific area and question:

In Remote Utility’s main window where I verified the Virtual Audio is: ICOM_VAUDIO-2 (I=X O=X), the I=0 and the O=0. In other words, I/O are both showing ZERO. You had said they shouldn’t be ZERO, and that that was the crux of the problem we were having yesterday. Well, now they *are* zero, and this setup is still working:

Mk2 > LAN > Dell laptop (software path for audio is: Remote Utility > FLRig > JS8) and it’s all working properly with those I/Os showing ZERO. Did I miss something, or should this NOT be working? (my blog readers will want to know!)

Gemini’s Answer: 

Good morning, Paul! It sounds like you’ve discovered the “Secret Logic” of the Icom Remote Utility.

You didn’t miss anything, and it should be working. The reason those I=0 O=0 readings were the “crux” of the problem yesterday, but are currently “lying” to you today, comes down to how Windows handles virtual devices.

The “Silent Pipe” Explanation

Why was it a problem yesterday?
What to tell your blog readers:
Summary Health Check:

In the Icom Remote Utility, the I (Input) and O (Output) indicators measure the audio flowing specifically through the Remote Utility’s own internal processing.

Here is why they show ZERO even though JS8Call is singing:

  1. Direct App-to-Driver Connection: When you tell JS8Call to use ICOM_VAUDIO-2 as its soundcard, it is talking directly to the Windows Driver. It’s like JS8Call has plugged its own cable into the wall jack.
  2. The Utility is the “Gatekeeper,” not the “Meter”: The Remote Utility created that wall jack (the virtual driver) and it’s keeping the tunnel to the Mk2 open in the background. However, it often only “meters” the audio if the RS-BA1v2 Control Software (the one with the knobs) is the one sending the audio.
  3. The “Third-Party” Bypass: Because you are using a third-party app (JS8Call) to drive the virtual cable, the Remote Utility sees that the “tunnel is busy,” but it doesn’t always “count” the packets in its little visual display.

Yesterday, the I=0 O=0 was a symptom of a Mute or a Level 0 setting in the Windows Mixer. In that case, the “pipe” was physically blocked by the OS.

Today, the pipe is Open, the audio is flowing, but the Utility’s visual meter is simply looking at the wrong part of the stream. Think of it like a water meter on the main street: if you tap into the pipe after the meter, the meter stays at zero even though your sprinklers are running full blast.

You can add a “Tech Note” to your post:

“Don’t panic if I/O shows Zero: The [I=0 O=0] status in the Remote Utility main window can be misleading. If your Windows Sound Settings and JS8Call are both pointed at the Virtual Audio Driver, the audio ‘bypasses’ the Utility’s visual meter. As long as you see signals on your JS8 waterfall and your Mk2 shows Power/ALC on transmit, you are golden!”

  • Waterfall moving? Yes.
  • Mk2 transmitting power? Yes.
  • ALC looking good? Yes.

Conclusion: The setup is perfect. The Utility is just being a “quiet” host today.

Well, I don’t know about you, but I don’t buy the whole “just being a ‘quiet’ host today” bit. That said, my setup and the Checklist I used to get things “set up” did work. Still works. I guess some things will just have to remain a mystery. Oh, and I try to remember what Gemini (I call ‘her’ Gemmi) says on the bottom of every chat: 

Gemini is AI and can make mistakes. 

Leave a comment