problem with SmartSDR v3.8 not launching properly

m5kvk

Let me start by saying this is a new issue: the Windows 11 PC concerned has been running SmartSDR with no problems for some time.

Just recently, SmartSDR for Windows has been mis-behaving - mainly by failing to launch properly. See the images for the symptoms. Three windows open but nothing more. If I quit, I get errors as shown. It doesn't happen every time.

SmartSDR for Mac has no problems, so I doubt it's the radio: which is connected to the same switch.

I've tried re-installing SmartSDR (upgrading to 3.8.21 from .20) but it makes no difference.

Mike-VA3MW

You'll need to open a support ticket for this.

m5kvk

Thanks, Mike.

I Should have thought of that first.

Mike-VA3MW

I see they are looking at it. thanks for doing that.

m5kvk

Just to close off this one. It turns out to be related to how I was accessing the remote PC.

I have Chrome Remote Desktop installed, and I have Microsoft Remote Desktop enabled. I generally use Chrome because it messes less with the audio sub-system. Microsoft has a tendency to mess up my audio - even though I have configured it to play audio on the remote system.

For some unexplained reason (maybe an update by Google?) Chrome stopped rendering the internal elements of SmartSDR. As soon as I switched to Microsoft the problem disappeared.

I've updated the support ticket to reflect this, but I thought I'd update here in case anybody experiences this.

Gaz

Gord-VA7GP

In early days of operating remotely…

I first used my TS-850, and a "remote desktop". I found audio un-usable, so I set up an alternate route just for audio: Mumble. This is an open-source voice-over-IP audio path, which needs a server (can be your own, or you can use an existing public server), and then your PC-near-radio connects to the server, and you-far-away also connects to the server. Mumble worked extremely well for me, with Windows, Linux and iOS iPhone.

Then, my Flex 6400. Initially I used Windows Remote Desktop, but again the audio wasn't to my liking, and Mumble served well. Again - one path for the graphical elements, and a totally separate path for audio. In fact, for my distant location I'd use a Mumble client on my phone, to both listen and TX. Worked very well.

But eventually I ditched all that, and simply use SmartSDR or Maestro. Simplifying my life, and allowing for quick-and-easy reformat / re-install of all PC software. One less server to administer.

So, one idea if you find your remote audio is janky - you might consider a separate audio-path that is focussed on isochronous / low-latency operation. Mumble is one; there are others.

m5kvk

Thanks, Gord

It's not a problem because I use SmartSDR for Mac from wherever I am for any voice or CW. I do use Sonobus to get audio from the remote pc, but as I only use the remote pc for data modes, I don't really need audio anyway.

The issue is that even when it's been told to ignore audio, Microsoft Remote Desktop still upsets the local audio path on the remote pc. To give me flexibility, I route all the audio feeds through VoiceBanana (s/w mixing desk) so I can tailor audio levels for different apps.