VAC Fails after Win 10 Creators Upgrade

User avatar
WA0VY
Posts: 36
Joined: Sun Apr 09, 2017 3:41 pm

VAC Fails after Win 10 Creators Upgrade

Postby WA0VY » Sat Jun 17, 2017 2:45 pm

MS inflicted me with the Win 10 Creators update over the last couple days. I have been reading that many of you had to reload various drivers as a result so I was not surprised when I could not get TX audio into HPSDR via VAC 1 using my ASI 5211 card. RX audio, which also goes through that card, was fine on VAC 1. I upgraded and reloaded the ASIO drivers but still no dice. I could see the audio in the ASI metering but it did not get to HPSDR. I looked for a setting that might of changed in HPSDR, disabled and restarted VAC, still no dice. I then reloaded 3.4.1 in repair mode and boom! Everything is now restored. Just passing this on in case someone else sees the issue.
73 Brent WA0VY
AB2EZ
Posts: 32
Joined: Sun Apr 09, 2017 2:29 pm
Location: Princeton, NJ

Re: VAC Fails after Win 10 Creators Upgrade

Postby AB2EZ » Sat Jun 17, 2017 3:40 pm

Brent

My Win 10 -based setup has always been finicky on Windows updates*

After installing the "Creators" update... yesterday... I had the problem you describe (VAC1 not providing audio input to the ANAN-10E on transmit).

I noticed that in the HPSDR audio settings... the VAC1 settings had changed. I was able to (re) select my desired driver (MME), and my desired output device (VoiceMeeter Input)... but, in the selection box, Voicemeeter Output was not listed as an input selection. Instead, there were two listings for VoiceMeeter AUX Output. Selecting the first Voicemeeter AUX output listing produced (as I expected) no transmit audio. But selecting the 2nd second Voicemeeter AUX output solved the problem.

Stu

*In the past, I resolved Windows 10 update-related problems by removing/replacing an old USB hub with a new one... and removing/replacing old USB audio interfaces that didn't have Win 10 driver updates available.
AB2EZ
Posts: 32
Joined: Sun Apr 09, 2017 2:29 pm
Location: Princeton, NJ

Re: VAC Fails after Win 10 Creators Upgrade

Postby AB2EZ » Sat Jun 17, 2017 5:58 pm

As an addendum to my earlier post:

I uninstalled and reinstalled Voicemeeter Banana. That fixed the problem of the missing "Voicemeeter Output" in the list of ANAN-10 VAC1 available input devices... and also in the list of Windows Sound "Playback Devices".

After reinstalling VMB, I also had to use the "Virtual IO Control Panel" and (separately) the "Virtual AUX IO Control Panel" (both accessible as applications via Start=>VB Audio) to reset both "Virtual Input" sampling rates to 48000 Hz.

I checked all of the Windows 10 audio device settings (i.e. Playback and Recording devices) to make sure they all were set to: 2Ch 16bit (CD Quality) 48000 Hz sampling.


Stu
Last edited by AB2EZ on Sat Jun 17, 2017 10:18 pm, edited 1 time in total.
User avatar
w-u-2-o
Posts: 407
Joined: Fri Mar 10, 2017 1:47 pm

Re: VAC Fails after Win 10 Creators Upgrade

Postby w-u-2-o » Sat Jun 17, 2017 7:34 pm

Sounds very typical (pun intended :D )

VMB is just another sound driver, and just as subject to the vagaries of Windows updates as any other sound driver.

I fully expect to have to reinstall both Behringer drivers and VMB based on what everyone is reporting in this thread, just like I did when the Anniversary update hit my PC. No sign of the Creator update yet, though.
User avatar
WA0VY
Posts: 36
Joined: Sun Apr 09, 2017 3:41 pm

Re: VAC Fails after Win 10 Creators Upgrade

Postby WA0VY » Sat Jun 17, 2017 10:40 pm

Interesting comment on the Win sound settings. I just checked and found mine were reset to 44100 from 48000. However, everything still worked. While driver issues were expected as soon as the update process began, I was surprised that it affected something in HPSDR, and further surprised that the fix ( a repair install) was so painless.
73 Brent WA0VY
User avatar
WA0VY
Posts: 36
Joined: Sun Apr 09, 2017 3:41 pm

Re: VAC Fails after Win 10 Creators Upgrade

Postby WA0VY » Sun Jun 18, 2017 6:29 pm

Well, I thought I was firmly back in the saddle post Win 10 Creators update but am now experiencing all manner of new craziness. Symptoms as follows:

1. Noticed a signal on RX that was like a picket fence of evenly spaced 30 db spikes all across 20 meters and beyond. If it were real, the power would be a million Janskys or so. I hesitate to even offer a theory on this. I simply cannot come up with an explanation that makes sense.

2. This morning, I tuned on 40 and then hit the two tone. The drive level and power out from my amp was exactly as expected. I TX'd SSB and saw peaks at about 1/3 of the the power on tune. FWD power reading in HPSDR was about 1/3 of where it should have been. Normally, the peaks would have been the same as output power on tune. I checked the mic, pre amp levels, ASI levels, Omnia levels and HPSDR levels. All were where they should have been. To get peaks back to the output on tune, I had to increase the drive level by 3x. The FWD power shown in HPSDR then went up to were it should have been. I checked to see if something was amiss in Win Sound settings and found nothing. I cycled the radio and HPSDR to no effect. Suddenly, I was over driving the amp and could see huge IMD products in both the spectrum analyzer and waterfall. I brought the drive level back down to where it should be and all was good thereafter.

3. I just hit tune on 20 and saw what looked like a two tone. I then hit two tone and saw the same. I cycled HPSDR and the radio to no effect. I checked again and again to see if this anomaly cleared but it was relentless. Reboot of Win 10 cleared it back to normal.

4. HPSDR lost contact with the 8000DLE. Thereafter, it could not find the radio on the dedicated LAN. I cycled HPSDR and did both a reset and power cycle of the radio. Still no contact. Searched for the radio on HPSDR Programmer, found it. Network settings were fine. Rebooted Win 10 and the connection was restored.

Win SFC found nothing wrong. I'm looking for a commonality here and hoping a clean install of HPSDR might be it. If its a clean install of Win 10, I'm going throw up. Nevertheless, I'm going to go ahead and backup and prepare. Any ideas are greatly appreciated.
73 Brent WA0VY
User avatar
w-u-2-o
Posts: 407
Joined: Fri Mar 10, 2017 1:47 pm

Re: VAC Fails after Win 10 Creators Upgrade

Postby w-u-2-o » Sun Jun 18, 2017 7:08 pm

Reinstall sound card drivers. Reinstall VMB. Reconfigure sample rates.

Try it. If it still doesn't work, fresh database.
User avatar
Tony EI7BMB
Posts: 63
Joined: Sun Apr 09, 2017 2:31 pm
Location: Dublin
Contact:

Re: VAC Fails after Win 10 Creators Upgrade

Postby Tony EI7BMB » Sun Jun 18, 2017 8:55 pm

I found some settings on the Ethernet port had been changed, might be worth a look.

Return to “PowerSDR mRX”