Date   

locked Re: New install

HamApps Support (VK3AMA)
 

On 18/06/2021 9:05 am, KS0JD-Jeff-913-558-0388 wrote:
I went one version back and everything seems to work now.
Thanks
Jeff

What version did you roll back to?

You never did answer the question I asked here,
Are you able to open the Help -> About window? That result would provide me with some insight as to what was happening. But that is irrelevant now as you have changed version.

de Laurie VK3AMA




locked Re: WSJT-X Communication Problem

HamApps Support (VK3AMA)
 

On 18/06/2021 7:35 am, Wes Atchison via groups.io wrote:
Below is my current JT Alert setup.  Getting error message saying JTA can not connect to WSJT-X.

Wes
WA


JTAlert Instance       : #1
JTAlert Start Params   : /wsjtx
WSJT-X Window Title    : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV
WSJT-X Command Line    : "C:\WSJT\wsjtx\bin\wsjtx.exe" 
WSJT-X   --rig-name    : 
WSJT-X Config File     : C:\Users\wa5tk\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version         : 
WSJT-X Revision        : 
WSJT-X Spec Op Mode    : None
WSJT-X UDP ID          : 
WSJT-X UDP Port        : 2237
WSJT-X UDP Server      : 239.255.0.1
WSJT-X UDP MCast on LB : True
WSJT-X UDP Max Schema  : 

Is this a recent problem, has JTAlert correctly previously?

That info dump tells me that JTAlert identified a running WSJT-X instance but never received any UDP traffic from it.
Some possibilities...
  1. Another application is working with WSJT-X and it is set to use unicast, not multicast UDP and has taken exclusive control of port 2237 preventing JTAlert from receiving UDP messages. Do you have any other apps working with WSJT-X? If so what are they?

  2. WSJT-X is being run with elevated privileges, set to run as administrator. The is never any normal need to do this. Check both the wsjtx.exe application file and the shortcut used to start WSJT-X to see if "Run as administrator" is checked. If that setting is set, turn it off, DON'T try and solve the problem by running JTAlert elevated.

  3. WSJT-X is being started by a third application and that application is set to "Run as administrator".

de Laurie VK3AMA


locked Re: New install

KS0JD-Jeff-913-558-0388
 

I went one version back and everything seems to work now.
Thanks
Jeff


locked WSJT-X Communication Problem

Wes Atchison
 

Below is my current JT Alert setup.  Getting error message saying JTA can not connect to WSJT-X.

Wes
WA


JTAlert Instance       : #1
JTAlert Start Params   : /wsjtx
WSJT-X Window Title    : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV
WSJT-X Command Line    : "C:\WSJT\wsjtx\bin\wsjtx.exe" 
WSJT-X   --rig-name    : 
WSJT-X Config File     : C:\Users\wa5tk\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Version         : 
WSJT-X Revision        : 
WSJT-X Spec Op Mode    : None
WSJT-X UDP ID          : 
WSJT-X UDP Port        : 2237
WSJT-X UDP Server      : 239.255.0.1
WSJT-X UDP MCast on LB : True
WSJT-X UDP Max Schema  : 
 
==================================================
UDP Ports used
--------------------------------------------------
JTAlert.exe           : 63763 60838
JTAlertV2.Manager.exe : 64243 64244 64245
JTAlertV2.Decodes.exe : 
 
 
==================================================
Audio output devices
--------------------------------------------------
[1] Speakers (C-Media PCI Audio Device)
 
 
==================================================
JTAlertV2.Manager (2.50.1.0) status
(2021-06-17 21:32:04 utc)
--------------------------------------------------
CLR Version      : 5.0.7
NET Framework    : .NET 5.0.7
Architecture     : x64 64bit
--------------------------------------------------
UDP Router       : Initialized : YES (WSJT-X)
Audio            : Initialized : YES (1 output devices)
BandData         : Initialized : YES (started : 58)
Text Msgs        : Initialized : YES (started : 17)
HamSpots         : Initialized : YES
QRZ Xml          : Initialized : YES (WA5TKU)
HamQth Xml       : Initialized : YES 
QRZ Log          : Initialized : YES 
HamQth Log       : Initialized : YES 
ClubLog Log      : Initialized : YES 
Eqsl Log         : Initialized : YES 
HrdLog Log       : Initialized : YES 
DXLab DDE        : Initialized : YES
User Alert       : Initialized : YES
Updates Check    : Initialized : YES (started : 3600)
Environment      : Initialized : YES (started : 3600)
Maintenance      : Initialized : YES (started : 3600)
--------------------------------------------------
 


locked Re: : Todays Windows update and broken JTAlert audio - THE FIX

Jon Gefaell
 

I upgraded to the new JTAlert yesterday and experienced the issue reported. I ventured to this group, and with a simple and quick search, I found this thread and quickly understood and addressed the issue. I want to thank y'all 


locked Re: Possible work-around for NAudio's lack of .Net 5 audio port selection

Jim Cooper
 

On 17 Jun 2021 at 17:41, HamApps Support (VK3AMA)
wrote:

It is those inbuilt sound routines
that lack any ability to select an
output device, all playback goes to
the Windows default device.
I like the previously suggested concept
of locking out JTalert audio if the user
is using ONLY one sound device (default)
on the system. These days there is really
no reason at all not to add a $5 USB audio
device as a non-default audio -- esp. since
WSJT even specifically says it's not
recommended to use default audio for the
transmitted data signals.

w2jc


locked Re: Possible work-around for NAudio's lack of .Net 5 audio port selection

HamApps Support (VK3AMA)
 

On 17/06/2021 3:33 pm, TomK wrote:
Thanks for the fast work, Laurie, with the audio workaround - not to mention all else you do!

Too bad NAudio doesn’t support specific device selection. Especially with multiple apps fighting over device ports.
Using only “default audio port” can be confusing as to which apps are using a specific output audio port.

However, it may be possible to use Windows Advanced Audio settings panel to remap to a specific port - unbeknownst to the app's own port request. 
To wit: Even if NAudio limits audio port to "Default", the Windows Advanced Audio panel can possibly remap to a specific port with its remapping feature.
I’d be happy to test the Beta in that scenario. 😊

Just another thought!
TomK / KT1TK / 73

Tom,

Sorry you have it wrong. NAudio does allow for playback device selection, that is one of the reasons I was using it. But it is broken with NET 5.0.7. The code introduced in 5.0.7 that triggers the NAudio issues has been reversed by the .NET devs, but it may be months before it makes it into a new NET release. As a result I have had to temporarily abandon using NAudio and rely instead on the inbuilt sound functions of WPF, which is the new code used to create JTAlert 2.50.x. It is those inbuilt sound routines that lack any ability to select an output device, all playback goes to the Windows default device.

de Laurie VK3AMA


locked Re: Possible work-around for NAudio's lack of .Net 5 audio port selection

TomK
 

Thanks for the fast work, Laurie, with the audio workaround - not to mention all else you do!

Too bad NAudio doesn’t support specific device selection. Especially with multiple apps fighting over device ports.
Using only “default audio port” can be confusing as to which apps are using a specific output audio port.

However, it may be possible to use Windows Advanced Audio settings panel to remap to a specific port - unbeknownst to the app's own port request.
To wit: Even if NAudio limits audio port to "Default", the Windows Advanced Audio panel can possibly remap to a specific port with its remapping feature.
I’d be happy to test the Beta in that scenario. 😊

Just another thought!
TomK / KT1TK / 73


locked Re: New install

Laurie, VK3AMA
 

On 17/06/2021 2:40 pm, Chris Levingston wrote:
Clicking on View brings up the menu but I clicking on the starred items does not work so I cannot see the Callsigns Window, as per the next screen shot attached
Is the Callsigns window perhaps showing off-screen? Is there an entry for the Callsigns window in the Windows taskbar? If so then a quick Google search will return a solution to recovering off-screen windows, a common Windows problem.

Are you able to open the Help -> About window?

de Laurie VK3AMA


locked Re: New install

Chris Levingston
 

I have the same problem, but have checked that option, as per the attached.



Clicking on View brings up the menu but I clicking on the starred items does not work so I cannot see the Callsigns Window, as per the next screen shot attached.


Thanks in advance - Chris    VK5SA


locked #Important #Announcement : Status update on Broken JTAlert audio with NET 5.0.7 desktop runtime #Important #Announcement

HamApps Support (VK3AMA)
 

An update on the current status of broken JTAlert audio with the .NET 5.0.7 desktop runtime.

  • I just now finished testing a new NET build with the fix that broke audio with NET 5.0.7. It worked flawlessly.

  • After reporting my successful tests I asked the question, "Any idea on how long before the fix makes it into a public NET release, days, weeks or months?" I got the response...
    This will likely be more on the scale of months rather than weeks due to the servicing timeline.

  • That response was unexpected, but I understand the issue.

  • So I will be going with my plan "B", dropping the audio library which is broken by the NET 5.0.7 changes.
    That has already been coded and has been with the test team for a few days now.

  • I will be targeting the JTAlert 2.50.2 public release for 21-June-2021.

  • Please be aware that JTAlert 2.50.2 will no longer support audio output device selection. All audio output will be sent to the device set as the default under Windows.

  • If JTAlert audio output device selection is important to you, my suggestion is to roll back JTAlert to version 2.16.17

  • If the affected audio library, NAudio, developer codes a fix before the new fixed NET runtime is released I will reverse the "playback on the default audio device only" change. I do note that the NAudio developer has been conspicuously quite regarding this issue, so I am not expecting a fix for the NAudio library any time soon.

de Laurie VK3AMA




locked Re: cannot install JT Alert #FT8

JJ Clements <algarvian1943@...>
 

Hello OM Bill,

Eureka !

With 5.0.6 it worked immediately.

Thank you so much for your help.

I delayed the update for 7 days. After 7 days and Windows will update does this mean that JT Alert stops ???

Regards,

PA2JJC de Jan

Op 16/06/2021 om 20:45 schreef JJ Clements via groups.io:

Hello Bill,

I am sure I have 64-bit installed.

I shall try to do install version 5.0.6

Thanks

73's

Op 16/06/2021 om 18:18 schreef g4wjs:
On 16/06/2021 16:10, algarvian1943@gmail.com wrote:

--
Hi all. I am trying to set up JTAlert. I downloaded and installed NET version 5.0.7 However when I open JT Alert  it says it cannot find NET.0.7 ! And invite me to install it again ?
What can be the reason for this. Is it perhaps that there is an older NET version ? How can I connect Version 5 in order that JT Alert will recognise it ?
Thanks
PA2JJC
OM,

you have probably installed the wrong version of Microsoft Windows Desktop Runtime, you need the 64-bit version if you are running the 64-bit version of JTAlert. Note also, for a short while at least, you should install version 5.0.6 as v5.0.7 triggers a defect in a component that JTAlert uses. Just to complicate things, Windows Update will try and automatically update to 5.0.7 as that release is a security update, so you may have to pause Windows Updates for 7 days if you want to keep JTAlert working.


--
Hi all. I am trying to set up JTAlert. I downloaded and installed NET version 5.0.7 However when I open JT Alert  it says it cannot find NET.0.7 ! And invite me to install it again ?
What can be the reason for this. Is it perhaps that there is an older NET version ? How can I connect Version 5 in order that JT Alert will recognise it ?
Thanks
PA2JJC


locked Re: cannot install JT Alert #FT8

JJ Clements <algarvian1943@...>
 

Hello Bill,

I am sure I have 64-bit installed.

I shall try to do install version 5.0.6

Thanks

73's

Op 16/06/2021 om 18:18 schreef g4wjs:

On 16/06/2021 16:10, algarvian1943@gmail.com wrote:

--
Hi all. I am trying to set up JTAlert. I downloaded and installed NET version 5.0.7 However when I open JT Alert  it says it cannot find NET.0.7 ! And invite me to install it again ?
What can be the reason for this. Is it perhaps that there is an older NET version ? How can I connect Version 5 in order that JT Alert will recognise it ?
Thanks
PA2JJC
OM,

you have probably installed the wrong version of Microsoft Windows Desktop Runtime, you need the 64-bit version if you are running the 64-bit version of JTAlert. Note also, for a short while at least, you should install version 5.0.6 as v5.0.7 triggers a defect in a component that JTAlert uses. Just to complicate things, Windows Update will try and automatically update to 5.0.7 as that release is a security update, so you may have to pause Windows Updates for 7 days if you want to keep JTAlert working.


--
Hi all. I am trying to set up JTAlert. I downloaded and installed NET version 5.0.7 However when I open JT Alert  it says it cannot find NET.0.7 ! And invite me to install it again ?
What can be the reason for this. Is it perhaps that there is an older NET version ? How can I connect Version 5 in order that JT Alert will recognise it ?
Thanks
PA2JJC


locked Re: New install

algarvian1943@...
 

Hi OM no I shall try this thankd 73 de Jan

Op wo 16 jun. 2021 18:22 schreef g4wjs <bill.8@...>:

On 16/06/2021 00:31, KS0JD-Jeff-913-558-0388 wrote:
> I am getting this
>
> Unable to communicate with the WSJT-X process.
>   UDP Port : 2237
>   IP Address : 239.255.0.0
>   Values read from WSJT-X config file...
>     C:\Users\darby\AppData\Local\WSJT-X\WSJT-X.ini
>
> WSJT-X Detected Instance...
>   Process Window Title : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and
> IV3NWV
>   Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"
>
> Decode alerts and logging will be unavailable until corrected.

OM (Jeff?),

have you checked the JTAlert Settings menu option "Multicast on loopback
interface"?



--
73
Bill
G4WJS.






--
Hi all. I am trying to set up JTAlert. I downloaded and installed NET version 5.0.7 However when I open JT Alert  it says it cannot find NET.0.7 ! And invite me to install it again ?
What can be the reason for this. Is it perhaps that there is an older NET version ? How can I connect Version 5 in order that JT Alert will recognise it ?
Thanks
PA2JJC


locked Re: New install

g4wjs
 

On 16/06/2021 00:31, KS0JD-Jeff-913-558-0388 wrote:
I am getting this

Unable to communicate with the WSJT-X process.
  UDP Port : 2237
  IP Address : 239.255.0.0
  Values read from WSJT-X config file...
    C:\Users\darby\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV
  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

Decode alerts and logging will be unavailable until corrected.
OM (Jeff?),

have you checked the JTAlert Settings menu option "Multicast on loopback interface"?



--
73
Bill
G4WJS.


locked Re: cannot install JT Alert #FT8

g4wjs
 

On 16/06/2021 16:10, algarvian1943@gmail.com wrote:

--
Hi all. I am trying to set up JTAlert. I downloaded and installed NET version 5.0.7 However when I open JT Alert  it says it cannot find NET.0.7 ! And invite me to install it again ?
What can be the reason for this. Is it perhaps that there is an older NET version ? How can I connect Version 5 in order that JT Alert will recognise it ?
Thanks
PA2JJC
OM,

you have probably installed the wrong version of Microsoft Windows Desktop Runtime, you need the 64-bit version if you are running the 64-bit version of JTAlert. Note also, for a short while at least, you should install version 5.0.6 as v5.0.7 triggers a defect in a component that JTAlert uses. Just to complicate things, Windows Update will try and automatically update to 5.0.7 as that release is a security update, so you may have to pause Windows Updates for 7 days if you want to keep JTAlert working.



--
73
Bill
G4WJS.


locked cannot install JT Alert #FT8

algarvian1943@...
 


--
Hi all. I am trying to set up JTAlert. I downloaded and installed NET version 5.0.7 However when I open JT Alert  it says it cannot find NET.0.7 ! And invite me to install it again ?
What can be the reason for this. Is it perhaps that there is an older NET version ? How can I connect Version 5 in order that JT Alert will recognise it ?
Thanks
PA2JJC


locked Re: Logging with HRD Log V6 (Submode) #HRD

Gary - AC6EG
 

Hi Laurie
Using JTAlert v2.50.1 (beta) with WSJT-X v2.5.0-rc1 to log to HRD v6.7.0.357 with MySQL / MariaDB.
On 5/5/21 I reported to you that I had been unable to reproduce this problem. I later discovered and corrected three log entries with Mode FT8 (FT4). I immediately started using the beta version of JTAlert and after several weeks of operating FT8 & FT4 have not seen any more of these mode errors.  Your beta looks like a winner!  Oddly enough, eQSL accepted my three Mode FT8 (FT4) submissions as matches to corresponding Mode FT8 eQSL's.  
Gary - AC6EG


locked Re: : Todays Windows update and broken JTAlert audio - THE FIX

HamApps Support (VK3AMA)
 

On 16/06/2021 8:36 am, richard clare wrote:
my issue is that microsoft keeps reinstalling 5.0.7 every day after I have removed and installed 5.0.6. Is there a solution for this? 
Thanks, Richard wb6ewm

The definitive solution is to downgrade to JTAlert 2.16.17 and wait till the new 2.50.2 is released.

2.50.02 corrects the crashing no-sound problem induced by the 5.0.7 runtime patch but at the expense of only outputting audio to the Windows default audio device, there is no sound-card selection possible.

I am currently waiting on a new runtime beta from the MS devs for me to test. How that goes and if an official runtime fix is made publicly available within the next couple of days I will reverse the JTAlert 2.50.2 no-sound device changes and then make it a public release. So, I am in a holding pattern at the moment. Regardless, there will be a public release of JTAlert 2.50.2 in a couple of days time, what form that release takes regarding the sound output device selection is unclear at the moment.

de Laurie VK3AMA


locked Re: New install

KS0JD-Jeff-913-558-0388
 

I am getting this

Unable to communicate with the WSJT-X process.
  UDP Port : 2237
  IP Address : 239.255.0.0
  Values read from WSJT-X config file...
    C:\Users\darby\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.4.0   by K1JT, G4WJS, K9AN, and IV3NWV
  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

Decode alerts and logging will be unavailable until corrected.

2261 - 2280 of 37666