I’ve been holding off as a newbie, trying to avoid being “that guy,” but my patience has worn through. A Win10 Pro box running wfview as a “radio server” provides everything but audio. In the “radio server” page, RX Audio Input is set to CABLE Output and TX Audio Output is set to Speakers (VB Audio Point).
The other Win10 Pro Box running as a client has Rx Audio Input set to Cable Output (VB Audio Point). The TX Audio Output is set to Speakers (VB Audio Point).
All of these settings are my fault, trying to get to the ones the [might] work. So far, no good. The Audio System box on either page does not light up unless the radio is disconnected, and it is unclear what any of the setttings might do. I have scoured the documentation, but to no avail.
Any help from any successful connector would very much be appreciated.
On your server side, the audio devices selected under “Radio Server” need to be the radio’s USB audio devices. They will generally be named something with “USB CODEC” in the name, but the exact name can vary.
Make sure to Save Settings.
On the client side, you might want to start just by selecting your usual Speakers and Microphone devices before you dive into VBCABLE. Just to keep it simple until it works.
With all that said, I do encourage you to wait a day or two for version 1.60 to come out, which may work better for your purpose.
Damn near set up. But. Can use mic on IC7300 and it shows transmitting. On the client, I can press the transmit button and talk but power meter shows zero. CW shows normal signs. Any suggestions before what’s left of my hair is on the floor?
You need to tell the radio where to find the transmit audio. On the wfview client, Settings → Radio Settings → Modulation Input: (or Data Mod Input if using datamodes) needs to be USB to allow the audio from wfview to be used.
Also on the wfview client, you can enable a second meter, Settings → User Interface → Secondary Meter Selection. If you select TxRxAudio or TxAudio, this will show whether your audio is getting as far as wfview.
Did you check the meters as I said in my previous message?
We really need to see logs to be able to diagnose further as there are many possible causes. Can you click Log → “Send to Termbin” and post the URL you receive into a reply (on both the client and server)?
Well that’s an interesting one, this is the problem (from the server log):
2023-03-07 07:58:35.698 INF audio: Output failed to open device Unanticipated host error
This means that PortAudio encountered an error opening the output device (tx audio) sadly it hasn’t reported any more information.
I would recommend trying Qt Audio or Rt Audio on the server instead. One of the main reasons that we support 3 different audio systems is that it gives you 66% more chance of finding a configuration that works!
I would expect the IC-7300 devices to be called Speakers/Microphone (USB Audio CODEC) but I notice in the server configuration you have selected the USB Audio Device for output:
No you need to work out which of those is actually your IC-7300 and ONLY use that (your server is currently configured to use one USB Audio CODEC and one USB Audio Device, that is definitely incorrect.