[wsjt-devel] W10 Issues

[Josh Rovero]

This came under the category of "W10 update mangles audio devices".

Reinstalling VAC seems to have fixed it.  Not a wsjtx issue, per se, but an
"any app that uses VAC" issue.

-- 
P.J. "Josh" Rovero http://www.roveroresearch.org
Ham Radio: KK1D http://www.roveroresearch.
net
http://www.roveroresearch.info
--
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

[wsjt-devel] r7161

[Black Michael]

Oops
C:\JTSDK\src\wsjtx\mainwindow.cpp: In member function 'void 
MainWindow::fast_decode_done()':
C:\JTSDK\src\wsjtx\mainwindow.cpp:2316:12: error: 'i' was not declared in this 
scope
   if(m_msg[i][0]==0) m_bDecoded=false; de Mike W(MDB
--
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

Re: [wsjt-devel] WSJT-X v.1.7.0-rc1 r7152-dirty and Transmit Audio Source using FT-991

[Bill Somerville]

On 07/10/2016 17:12, Keith Laaks wrote:
> I would like to run using Mode=USB instead of Mode=Data/Pkt since the 
> radio applies a narrower filter to the audio when in "Data/Pkt" mode 
> as opposed to "USB" mode, which is perhaps 500Hz or more wider (I want 
> to be able to 'see more' of the spectrum).
>
> But when I select Mode=USB, the "Transmit Audio Source" is then the 
> Front/Mic and so the WSJT-X generated audio never makes it through - 
> only the audio that gets picked up via the Microphone.
>
> When I select Mode=Data/Pkt, the TX audio from the PC goes through to 
> the FT-991 via the usb-cable (of course this usb not to be confused 
> with the 'Upper Side Band / USB).
>
> So is there something I am missing here. I suspect I need to get the 
> "Transmit Audio Source" set to "Rear/Data" somehow.

Hi Keith,

the front/rear audio selection only applies to rigs like the Kenwood 
ones that require a different CAT PTT command to select the audio 
source. For rigs like your Yaesu the audio source is configured from the 
rig menu.

Having said that a better configuration is to set "Split Operating" to 
Rig and Mode to "None", that way you can set the Tx VFO mode to USB-DATA 
and the Rx VFO to USB. This is required for a few Yaesu rigs as having 
the widest Rx passband only on USB mode seems to be a common trait from 
that manufacturer.

73
Bill
G4WJS.


--
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

[wsjt-devel] WSJT-X v.1.7.0-rc1 r7152-dirty and Transmit Audio Source using FT-991

[Keith Laaks]

Hi All,

I have been building and testing on Mac OS Sierra [10.12.1 Beta (16B2338c)]
using FT-991 as radio.

In my settings I see the "Transmit Audio Source" section always remains
greyed-out;
 with the "Front/Mic" radio button ticked by default.

I would like to run using Mode=USB instead of Mode=Data/Pkt since the radio
applies a narrower filter to the audio when in "Data/Pkt" mode as opposed
to "USB" mode, which is perhaps 500Hz or more wider (I want to be able to
'see more' of the spectrum).

But when I select Mode=USB, the "Transmit Audio Source" is then the
Front/Mic and so the WSJT-X generated audio never makes it through - only
the audio that gets picked up via the Microphone.

When I select Mode=Data/Pkt, the TX audio from the PC goes through to the
FT-991 via the usb-cable (of course this usb not to be confused with the
'Upper Side Band / USB).

So is there something I am missing here. I suspect I need to get the
"Transmit Audio Source" set to "Rear/Data" somehow.

(On WSJT I was able to run using USB mode - so know it's possible)

Thanks

Keith
ZS6TW
--
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

Re: [wsjt-devel] Still suspect something Evil in latest W10 Updates

[Roger Rehr W3SZ]

You might also try uninstalling the app[s] / drivers in question and
then rebooting and then reinstalling the apps / drivers.  That has been
known to fix problems with many apps that crop up after Windows 10
updates.  Unfortunately, it does  not fix all such problems.  I had to
uninstall/reinstall VAC here to resolve some problems that cropped up
after a Win 10 update.

73,
Roger Rehr
W3SZ

On 10/7/2016 10:55 AM, Josh Rovero wrote:
> On one of my recently updated W10 PCs, when wsjtx is terminated, the
> wsjtx process remains active (according to task manager) even though
> the GUI is gone.  It is impossible to terminate HDSDR instances except
> through task manager (i.e., STOP and EXIT buttons don't work), And
> when wsjtx is launched, the audio level via VAC is zero, nada,
> niente.  Yesterday, it seemed to launch ok, but terminated (froze)
> within an hour.
>
> The RF is processed by a QS1R via CWSL to both CW Skimmer Server and
> multiple instances of HDSDR.  
>
> Wouldn't be an issue except that normally I'd be running 7 * wsjtx in
> WSPR-2 mode, 2 * wsjtx in JT65+JT9 mode, and 8 * fldigi in PSK mode on
> this box.  The flidigi VAC connections to HDSDR seem OK. CW Skimmer
> Server and CW Reporter are running OK.  Only the wsjtx/HDSDR
> connections are having issues. That connection is via VAC, which is
> working fine for fldigi and HDSDR.
>
> Will try running all applications as administrator, and see if that
> helps.  
>
> -- 
> P.J. "Josh" Rovero http://www.roveroresearch.org  
> Ham Radio: KK1D http://www.roveroresearch.
> net
> http://www.roveroresearch.info
>
>
> --
> 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

[wsjt-devel] Still suspect something Evil in latest W10 Updates

[Josh Rovero]

On one of my recently updated W10 PCs, when wsjtx is terminated, the wsjtx
process remains active (according to task manager) even though the GUI is
gone.  It is impossible to terminate HDSDR instances except through task
manager (i.e., STOP and EXIT buttons don't work), And when wsjtx is
launched, the audio level via VAC is zero, nada, niente.  Yesterday, it
seemed to launch ok, but terminated (froze) within an hour.

The RF is processed by a QS1R via CWSL to both CW Skimmer Server and
multiple instances of HDSDR.

Wouldn't be an issue except that normally I'd be running 7 * wsjtx in
WSPR-2 mode, 2 * wsjtx in JT65+JT9 mode, and 8 * fldigi in PSK mode on this
box.  The flidigi VAC connections to HDSDR seem OK. CW Skimmer Server and
CW Reporter are running OK.  Only the wsjtx/HDSDR connections are having
issues. That connection is via VAC, which is working fine for fldigi and
HDSDR.

Will try running all applications as administrator, and see if that helps.

-- 
P.J. "Josh" Rovero http://www.roveroresearch.org
Ham Radio: KK1D http://www.roveroresearch.
net
http://www.roveroresearch.info
--
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