No remote audio away from home

I have been able to connect and operate all functions on a remote laptop at my home and I can receive audio fine and transmit. When at another location though I can connect and see the waterfall and all controls seem to work but I have no receive audio. My setup is: remote laptop Win10 client and Win11 server connected USB to Icom 7300. I have tried all the audio settings without result.

Truncated log:
023-01-08 15:43:57.504 INF udp: udpHandler Received radio capabilities, Name: IC-7300 Audio: ICOM_VAUDIO CIV: “0x94” MAC: 0 : 144 : 199 : 70 : 48 : 58 CAPF 20481

2023-01-08 15:43:57.504 INF udp: Got Connection status for: IC-7300 Busy: 0 Computer IP “0.0.0.0”

2023-01-08 15:43:57.504 INF udp: Got Radio 0

2023-01-08 15:43:57.504 INF udp: Find available local ports

2023-01-08 15:43:57.504 INF default: Received serial port baud rate from remote server: 115200

2023-01-08 15:43:57.504 INF system: Delay command interval timing: 75 ms

2023-01-08 15:43:57.551 INF udp: Starting udpCivData

2023-01-08 15:43:57.551 INF udp: UDP Stream bound to local port: 62450 remote port: 50002

2023-01-08 15:43:57.551 INF udp: Starting udpAudio

2023-01-08 15:43:57.551 INF udp: UDP Stream bound to local port: 62451 remote port: 50003

2023-01-08 15:43:57.551 INF udp: udpHandler Got serial and audio request success, device name: “IC-7300”

2023-01-08 15:43:57.551 INF udp: Got Connection status for: IC-7300 Busy: 1 Computer Bob-PC-wfview IP “64.229.186.223”

2023-01-08 15:43:57.551 INF audio: Output audio handler starting: “Realtek Digital Output (Realtek High Definition Audio)”

2023-01-08 15:43:57.551 INF audio: Output No audio device was found. You probably need to install libqt5multimedia-plugins.

2023-01-08 15:43:57.551 INF audio: Input audio handler starting: “Microphone (USB Audio Device)”

2023-01-08 15:43:57.551 INF audio: Input No audio device was found. You probably need to install libqt5multimedia-plugins.

2023-01-08 15:43:57.589 INF udp: udpCivData : Received I am here

2023-01-08 15:43:57.589 INF udp: udpAudio : Received I am here

2023-01-08 15:43:59.572 INF udp: Audio Watchdog: no audio data received for 2s, restart required?

2023-01-08 15:44:03.120 INF udp: CIV Watchdog: no CIV data received for 2s, requesting data start.

2023-01-08 15:44:06.662 INF rig: Using incomingCIVAddr: (int): 148 hex: “0x94”

2023-01-08 15:44:06.662 INF serial: Received rigCapabilities for “IC-7300”

2023-01-08 15:44:06.662 INF rig: Have rig ID: decimal: 148

2023-01-08 15:44:06.662 INF system: Delay command interval timing: 25 ms

2023-01-08 15:44:07.411 INF udp: udpCivData 1 or more missing packets detected, previous: “0xcd” current: “0xd0”

2023-01-08 15:44:07.433 INF udp: udpCivData : sending request for multiple missing packets : “ce:00:ce:00:cf:00:cf:00”

2023-01-08 15:44:07.464 INF udp: udpCivData : Missing SEQ has been received! “0xce”

2023-01-08 15:44:07.464 INF udp: udpCivData : Missing SEQ has been received! “0xcf”

2023-01-08 15:44:09.037 INF rig: Received 0x15 center span data: for frequency 100000

2023-01-08 15:44:25.746 INF udp: udpCivData 1 or more missing packets detected, previous: “0x828” current: “0x82a”

2023-01-08 15:44:25.815 INF udp: udpCivData : sending request for missing packet : “0x829”

2023-01-08 15:44:25.831 INF udp: udpHandler 1 or more missing packets detected, previous: “0x105” current: “0x107”

2023-01-08 15:44:25.862 INF udp: udpCivData : Missing SEQ has been received! “0x829”

Hi Ken,

What version of wfview are you using? Can you try again using one of our latest weekly public builds?

–E
de W6EL

I am using 1.53 I think but I cannot see in the program anywhere where it says the version number. It worked fine for 2 days. I am know back at home and still no audio. I tried a different remote PC and no audio on it either. I tried a public build a few days back but it would not open.

Hi Ken,

Definitely have a look over our User Manual and FAQ. It can’t hurt any.

Most likely the wrong audio device is selected on your client side, but it may have happened on the server side as well, it’s hard to know.

I would check the server log file to make sure the 7300 USB CODEC audio device is selected, and then check the client side to make sure the correct audio devices are being used. I also recommend using “Qt Audio” as the audio system by default on both sides. It generally works for most windows users.

–E
de W6EL

Hi Elliott

The Log file suggests “You probably need to install libqt5multimedia-plugins.” Is this correct it seems to be a linux file?

2023-01-09 12:53:18.804 INF udp: UDP Stream bound to local port: 58232 remote port: 50003

2023-01-09 12:53:18.804 INF udp: udpHandler Got serial and audio request success, device name: “IC-7300”

2023-01-09 12:53:18.804 INF udp: Got Connection status for: IC-7300 Busy: 1 Computer DESKTOP–wfview IP “192.168.0.146”

2023-01-09 12:53:18.804 INF audio: Output audio handler starting: "Speakers / Headphones (Realtek "

2023-01-09 12:53:18.804 INF audio: Output No audio device was found. You probably need to install libqt5multimedia-plugins.

2023-01-09 12:53:18.804 INF audio: Input audio handler starting: “Microphone (USB Audio Device)”

2023-01-09 12:53:18.804 INF audio: Input No audio device was found.

2023-01-09 12:53:18.804 INF udp: udpAudio : Received I am here

2023-01-09 12:53:18.804 INF udp: udpCivData : Received I am here

2023-01-09 12:53:18.804 INF rig: Warning: Spectrum sequence max was zero, yet spectrum was received.

2023-01-09 12:53:18.836 INF rig: Warning: Spectrum sequence max was zero, yet spectrum was received.

2023-01-09 12:53:18.851 INF rig: Warning: Spectrum sequence max was zero, yet spectrum was received.

2023-01-09 12:53:18.882 INF rig: Warning: Spectrum sequence max was zero, yet spectrum was received.

2023-01-09 12:53:18.898 INF rig: Warning: Spectrum sequence max was zero, yet spectrum was received.

2023-01-09 12:53:18.914 INF rig: Warning: Spectrum sequence max was zero, yet spectrum was received.

2023-01-09 12:53:18.945 INF rig: Using incomingCIVAddr: (int): 148 hex: “0x94”

2023-01-09 12:53:18.945 INF serial: Received rigCapabilities for “IC-7300”

2023-01-09 12:53:18.945 INF rig: Have rig ID: decimal: 148

2023-01-09 12:53:18.961 INF system: Delay command interval timing: 25 ms

2023-01-09 12:53:21.023 INF rig: Received 0x15 center span data: for frequency 100000

Hi Ken,

Per the FAQ, that is a linux-related message that accidentally made its way into windows.

Can you please verify the version you are running? See the FAQ for how to do this.

–E
de W6EL

wfview version 1.50
“This copy of wfview was built against Qt version 5.15.2”

I know at one point 2 days back I had to mute my audio from the server PC screen as I was receiving Radio audio on the PC speakers, I no longer have that audio suggesting the radio audio is not getting to the server PC?

Hi Ken,

The server should definitely not be making audio through the server’s PC speakers! Yikes! Sorry about that!

Try upgrading to the latest of our weekly builds. I believe we are on version 1.54 now. A lot of work has gone into audio device selection (and more work is continuing in this direction).

Make sure the log file on the server indicates the 7300 USB CODEC is being used.

–E
de W6EL

in fact 1.55.

  • 1.51
    Fix for squished screen
    Only request passband when there is a scope available
    Change default passband colors.
    Fix passband colorswatch
    Ignore second VFO scope data (for now)
    Silently ignore server audio issues if server is not enabled.
    Always use 8bit encoding for audio device names
    Make multimedia-plugins message only for Linux
    Add PSK modes to IC-7610 and to passband.
    Add passband for FM mode
    Added click-drag tuning. Needs refinement but it’s a start.
    colorpicker: Move to 3 columns
    passband indicator
    Remove logging of audio device realm
  • 1.52
    added cluster spotting including color picker suport
    optional SQLITE in memory for spots (disabled)
  • 1.53
    modified band buttons to look more alike the layout on the rigs
    audio selction combobox shows full devicenames
    Fixed color preset zero issue.
    Fixed unusual set of conditions in which manual CI-V address would fail
    to identify the connected radio.
    Fixed broken RTS preference. Added preliminary (and untested) support
    for the IC-703, 737, 738, and 756.
    added libs for suse builds; it also builds on leap 15.5
    Add skimmer support (setting not saved)
    Add AR Cluster support
    +1.54
    Various wfserver fixes
    logging using termbin edge case fix
    +1.55
    Compiles with QT5 and 6 now
    Many audio-fixes
    Fix wfserver device detection
    Prevent memory leak on exit
    Dawid Szymanski - SQ6EMM/SN6M ‘standardHFfix’; fixed missing 160m band
    Support hotplug audio on QT6+
    Remove Exception from RT audio as it doesn’t exist in newer versions of RTAudio
    Tidy-up device enumeration for Qt audio
    Log enumeration of audio devices
    Fix codec selection issue in both QT5 and 6
    Make sure compilation with QT5 still works

and we’re ahead of this but the verson has not been updated yet as we still haven’t pushed to master.

Public builds do not run when I add wfview-master-20230109–03-00-01.exe to my Wfview directory and run it I get an error message “The application was unable to start…”

Any more text in that message? Details help!

I tried WFview.exe after trying the public build and it would not run anymore showing a COM port 3 error. I then ran the build (ver 1.55 ) again and it ran ok but still no remote audio.

I should have said I installed ver 1.55 on the Server PC. I then tried it on the remote PC and it will not run with the "the app was unable to start error 0xc000007b. When I tried Public builds a few days back i got the same error.

Hi Ken.

The latest installer will install version 1.50 (you can tell what version is installed by looking in the About box) to then use any of the weekly public builds, you must copy both the latest wfview exe and the .dll files (Qt5Xml, portaudio_x86 and qcustomplot2) into your wfview program directory. Only then will you have v1.55!

73 Phil M0VSE

Hi Phil,
Some success! I reinstalled 1.50 on the server. I then installed 1.55 on both server and remote with the files you mentioned and ran 1.55. I received some audio in the form of clicks on the remote. I then ran Wfview 1.5 on the server and the audio on the remote is finally working correctly. I then tried 1.5 on the remote but no audio. Im at a loss though why it worked fine for two days with 1.5 on both PCs but now requires 1.50 server and 1.55 remote?
I noticed when I reinstalled 1.5 that it retained the settings from the previous install. Does it not clean out the registry on uninstall?