Oh yeah...forgot John is an IC7300...I did a similar thing with another
operator who had a rigblaster.The same sequence should work for most anybody
since the general idea is the same.
Mike
On Saturday, May 26, 2018, 11:21:22 AM CDT, John L. Broughton
<2silverhon...@gmail.com> wrote:
Just a couple comments.
I don't have a rig blaster and I don't have a laptop; I have a Dell desktop.
There was a latency problem which would not let us connect using Quick Assist
as I have HughesNet satellite Internet. We used TeamViewer instead.
Mike was a great help.
73,
John, WB9VGJ
John L. Broughton
www.wb9vgj.us
wb9...@arrl.net
2silverhon...@gmail.com On 5/26/2018 5:45 AM, Black Michael via wsjt-devel
wrote:
He had several problems. Here's what we did.
#1 Uninstall all sound drivers (with the remove files option). Reboot
without rig USB plugged in. #2 Tested his speakers and microphone (PC-based) to
ensure they worked using Voice Recorder -- this is a sanity check that your
sound setup works the way you think it should. #3 Plugged in rig and relabeled
the USB Codec drivers to make them easy to distinguish #4 Adjusted levels on
Windows Playback/Record cotrols to 0dB #4 Adjusted rig blaster to 12 o-clock
position. #5 Adjusted rig USB AF level to then get 30db+ on the waterfall (not
all rigs can do this so this may have to be done from rig blaster)
The decoding problem he had was due the signal levels being low from the rig
and over amplified in the Windows controls. So that's why he was getting
intermittent decodes as any gain over 0dB in the Windows controls buys you
nothing so there was lots of quantization going on.
He also has latency problems on his older laptop causing dropouts on
transmission but they are very short so don't affect him a whole lot.
de Mike W9MDB
On Saturday, May 26, 2018, 7:35:17 AM CDT, Barry Smith <b...@g4iat.co.uk>
wrote:
In message <e0b4ef0f-8c67-2ac0-9e6b-cdaf55764...@gmail.com>
"John L. Broughton" <2silverhon...@gmail.com> wrote:
> All,
> I want to thank Mike, W9MDB, for spending considerable time with me on
> the phone and connected to my computer this morning which resulted in
> resolving the audio problem. His expertise did the job; I never would
> have figured it out.
> Now looking forward to my 16th digital QSO with him...
> 73,
> John, WB9VGJ
> John L. Broughton
It could be useful to know what you/he did to resolve the problem in
case others experience the same problem.
Barry
G4IAT
IO83
--
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
| | Virus-free. www.avg.com |
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
