Support@HamApps.groups.io

Re: Callsign Window

JTAlert Support (VK3AMA)

#35695

On 21/06/2021 3:53 pm, Mike Cooper wrote:

I made that fix a few days ago. After checking I see Runtime 5.0.7 is back and 5.0.6 is gone. The must have been another update?????

NET 5.0.7 is classified a security update, so Microsoft is forcing its installation.

The next JTAlert 2.50.2 works with NET 5.0.7. It was supposed to be released today, but I had to push that out by a couple of days, as some non-ham activity has had to take precedence. JTAlert 2.50.2 is in the hands of the Test team, there have been no reports of Sound issues or the Callsigns window closing, both are directly caused by an incompatibility with NET 5.0.7 and the audio library used by JTAlert. That audio library has been patched to workaround the NET 5.0.7 defect.

The information I have seen indicates the security patch of NET 5.0.7 relates to a security vulnerability with ASP NET which unless your running an ASP server on your PC its not applicable, so reverting to NET 5.0.6 should not be putting your PC at risk.

de Laurie VK3AMA

Re: Callsign Window

Mike Cooper

#35694

I made that fix a few days ago. After checking I see Runtime 5.0.7 is back and 5.0.6 is gone. The must have been another update?????

Re: Callsign Window

JTAlert Support (VK3AMA)

#35693

On 21/06/2021 3:07 pm, Mike Cooper wrote:

My JT Alerts callsign window has just started dropping in and out at random. Running Windows 10, WSJT-X 2.4.0, and JT Alert 2.50.1

Any Ideas on this?

This problem is directly related to the recent sound problems that have been discussed on the support forum. A fix (workaround) has been posted.
See https://hamapps.groups.io/g/Support/message/35446

de Laurie VK3AMA

Callsign Window

Mike Cooper

#35692

My JT Alerts callsign window has just started dropping in and out at random. Running Windows 10, WSJT-X 2.4.0, and JT Alert 2.50.1

Any Ideas on this?

Interesting Anomaly

John Petrocelli

#35691

Hello,

    I have seen an interesting anomaly. I shall describe it and also a "work around"

    When one tight clicks on a callsign in the Callsign window and then left clicks on "show QSO history", it will sometimes not show the QSO history, nothing shows at all.

   The "work around" is..............

       1) go to the Main JTAlert window and right-click on the callsign and select "show QSO history". It will show the history for the callsign shown.
       2) close the callsign history window
       3) go to the Callsigns window and right-click on any callsign and select "show QSO history". It will work OK now.

    This "work around" will be OK until the next time the "Show QSO history" window does not work again. Simply perform the 3 steps listed in the "work around"

    It seems to be somewhat random although I am not sure on this timing.

-- 


John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com

Virus-free. www.avast.com

Macros window (counts the number of bands)

kiyo

#35690

Hello

Request for improvement for JTAlert 2.50.1
The total of "%" (BANDS worked) in Macros window counts the number of bands only in the same mode as in operation, but I want you to count the number of bands regardless of the mode.

I would like to ask you to consider.
--
kiyo

Re: Multiple operator using separate Windows user login - problems

Robert Lorenzini

#35689

Mike is a great resource for the community.

Bob - wd6dod

Show quoted text

On 6/19/2021 6:47 PM, Rory Davis, N7CR wrote:

Thanks for the feedback Laurie. Mike W9MDB helped me offline and he got us up and running. He also cleared up some issues with LOTW, Log4OM and WSJT-X as well. The XYL is so happy and she's blasting away on 17M as we speak. A great big THANKS, Mike!

Now it looks like I'll have to fight her over the rig... :D

73/Rory N7CR and Harolyn KE6SVR

Re: Multiple operator using separate Windows user login - problems

Rory Davis, N7CR

#35688

Thanks for the feedback Laurie. Mike W9MDB helped me offline and he got us up and running. He also cleared up some issues with LOTW, Log4OM and WSJT-X as well. The XYL is so happy and she's blasting away on 17M as we speak. A great big THANKS, Mike!

Now it looks like I'll have to fight her over the rig... :D

73/Rory N7CR and Harolyn KE6SVR

Re: Multiple operator using separate Windows user login - problems

Laurie, VK3AMA

#35687

On 20/06/2021 8:15 am, Michael Black via groups.io wrote:
You can also run JTAlert as Administrator and it works on multiple accounts.

Mike W9MDB
A BETTER option and much safer than elevated applications is to simply start JTAlert from a suitable shortcut with a callsign override in the startup parameters. This would need to be done under the Windows login for which JTAlert is running correctly.

de Laurie VK3AMA

Re: Multiple operator using separate Windows user login - problems

Laurie, VK3AMA

#35686

On 20/06/2021 8:15 am, Michael Black via groups.io wrote:

You can also run JTAlert as Administrator and it works on multiple accounts.

Yes, but I NEVER recommend elevating JTAlert as a permanent fix. It is common for users who go down this path having to then elevate other applications either to get them to work with JTAlert or WSJT-X or in some cases just elevate every application on their system just to be safe!

I do hope that any users you have helped in this way that you return to them at a later date, when JTAlert has been updated, to ensure they are no longer running elevated.

Elevating JTAlert or any other normal application should only be done for testing IMO, NOT to be used as the normal method of operation as is the need for some badly designed Ham software I have encountered .

FWIW, the running as Administrator is overriding the security permissions applied to the lock file used by the Manager process to enforce its single instance (per JTAlert instance) operation.

de Laurie VK3AMA

Re: Multiple operator using separate Windows user login - problems

Michael Black

#35685

You can also run JTAlert as Administrator and it works on multiple accounts.

Mike W9MDB

Show quoted text

On Saturday, June 19, 2021, 05:14:11 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

On 19/06/2021 11:24 pm, Todd (N3PKJ) wrote:

I'd be interested in knowing if you got this to work with JTAlert 2.50.X because I have 3 PCs that I can not get version 2.50.X to work the JTAlert.manager.exe won't stay running looks like it tries to start but stops/crashes then does this repeatedly. 2.16.17 works fine for me with multiple Windows Accounts. I've spoken to Laurie about the problems I'm he told me to send him the diagnostics from the affected account, which I did, then he told me that majority of the diagnostic files were not sent & that I have JTAlert install problem. I find it hard to believe that 3 different PCs all have the exactly the same problem. I have 2 videos, had to split due to Youtube restraints, that shows exactly what is happening with these 3 PCs located at https://www.youtube.com/watch?v=URnIFyZKrD4 & https://www.youtube.com/watch?v=Np72JDDcj4Q. Not mention that with JTAlert 2.50.X experiencing the same issues that Rory is speaking of.

73,
Todd (N3PKJ)

There is a newly discovered design flaw in JTAlert 2.50.x that prevents correct operation from an alternate Windows user account. This has bee corrected for the next release.

Its a design flaw in the unique (single) instance detection for the Manager process.

Until the release, the only option is to run JTAlert from the same Windows user account (the working account) and set the "/callsign=XYL" command line parameter for a JTAlert shortcut.

de Laurie VK3AMA

Re: Multiple operator using separate Windows user login - problems

JTAlert Support (VK3AMA)

#35684

On 19/06/2021 11:24 pm, Todd (N3PKJ) wrote:

I'd be interested in knowing if you got this to work with JTAlert 2.50.X because I have 3 PCs that I can not get version 2.50.X to work the JTAlert.manager.exe won't stay running looks like it tries to start but stops/crashes then does this repeatedly. 2.16.17 works fine for me with multiple Windows Accounts. I've spoken to Laurie about the problems I'm he told me to send him the diagnostics from the affected account, which I did, then he told me that majority of the diagnostic files were not sent & that I have JTAlert install problem. I find it hard to believe that 3 different PCs all have the exactly the same problem. I have 2 videos, had to split due to Youtube restraints, that shows exactly what is happening with these 3 PCs located at https://www.youtube.com/watch?v=URnIFyZKrD4 & https://www.youtube.com/watch?v=Np72JDDcj4Q. Not mention that with JTAlert 2.50.X experiencing the same issues that Rory is speaking of.

73,
Todd (N3PKJ)

There is a newly discovered design flaw in JTAlert 2.50.x that prevents correct operation from an alternate Windows user account. This has bee corrected for the next release.

Its a design flaw in the unique (single) instance detection for the Manager process.

Until the release, the only option is to run JTAlert from the same Windows user account (the working account) and set the "/callsign=XYL" command line parameter for a JTAlert shortcut.

de Laurie VK3AMA

Re: Multiple operator using separate Windows user login - problems

JTAlert Support (VK3AMA)

#35683

On 19/06/2021 8:42 am, Rory Davis, N7CR wrote:

Has anyone had luck with setting up a separate Windows user account for a 2nd operator? The XYL really wants to get active on FT8 but I'm having trouble making it all work together.

Using Win4YaesuSuite, Log4OM2 with Omni-Rig, W WSJT-X and JTAlert.

The setup still works with my Windows user account.
In the second account, the sound devices do not appear in the Sound ON | Sound Output Device > dropdown list. Nor does JTAlert appear in the Windows Volume Mixer. Under the Manage Settings window, both the rig sound device and the speakers are available as options, so the Speakers selection is set in the Settings window.

It appears that JTAlert is not communicating with WSJT-X either, though the settings are the same for both user accounts.

Also JTAlert and WSJT-X are not communicating with Log4OM2 but omni-rig is working OK.

Is there another/better way to add a second operator with the above combination of software?

FYI, There is a newly discovered design flaw in JTAlert 2.50.x that prevents correct operation from an alternate WIndows user account. This has bee corrected for the next release.

Its a design flaw in the unique (single) instance detection for the Manager process.

Until the release, the only option is to run JTAlert from the same Windows user account (the working account) and set the "/callsign=XYL" command line parameter for a JTAlert shortcut.

de Laurie VK3AMA

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

TomK

#35682

Thanks for the good words. I had worried about that, too!

Luckily, I have not seen that happen through 1.5 years of updates.

I was going to summarize some more things but that is protracting this thread, ha!

Unless replies deal with JTA and Win audio remapping, we should idle this thread.

Enjoy. TomK / KT1TK / 73

Show quoted text

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Dave C
Sent: Saturday, June 19, 2021 2:57 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Possible work-around for NAudio's lack of .Net 5 audio port selection

Tom,
Thanks for the detailed description of the Advanced Sound Options. I stumbled on this some while back and have used it successfully. However, I have the feeling that Microsoft sometimes tinkers with these settings at software updates. It is not uncommon for me to have to revisit my Sound settings after a Windows update.

73,
Dave

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

Dave C

#35681

Tom,
Thanks for the detailed description of the Advanced Sound Options. I stumbled on this some while back and have used it successfully. However, I have the feeling that Microsoft sometimes tinkers with these settings at software updates. It is not uncommon for me to have to revisit my Sound settings after a Windows update.

73,
Dave

Re: Multiple operator using separate Windows user login - problems

Todd (N3PKJ)

#35680
Edited

Hi Michael,

I'd be interested in knowing if you got this to work with JTAlert 2.50.X because I have 3 PCs that I can not get version 2.50.X to work the JTAlert.manager.exe won't stay running looks like it tries to start but stops/crashes then does this repeatedly. 2.16.17 works fine for me with multiple Windows Accounts. I've spoken to Laurie about the problems I'm he told me to send him the diagnostics from the affected account, which I did, then he told me that majority of the diagnostic files were not sent & that I have JTAlert install problem. I find it hard to believe that 3 different PCs all have the exactly the same problem. I have 2 videos, had to split due to Youtube restraints, that shows exactly what is happening with these 3 PCs located at https://www.youtube.com/watch?v=URnIFyZKrD4 & https://www.youtube.com/watch?v=Np72JDDcj4Q. Not mention that with JTAlert 2.50.X experiencing the same issues that Rory is speaking of.

73,
Todd (N3PKJ)

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

TomK

#35679

Great news re NAudio as it allows your code to run like you want it too. Yeah!

That further obviates any need to understand the rest of this note (for JTA at least).
Feel free to close this message now! Most others should do just that 😊

…. All masochists, read at your own risk …. It is nothing more than advanced tool ….

Nb. I had called the advanced option “Advanced Audio” when it is really “Advanced Sound”.

Re Windows Audio Sound Settings.

The Advanced Sound option provides an easy way to set an app’s audio paths even if it doesn’t have audio selections.
It acts just like an audio patch panel to reroute audio where you want it to go.
This is a Godsend since 95% of apps I know don’t have their own device selection and rely on the Windows default.

But, again, MOST USERS WILL NEVER NEED THIS!!!

Re Advanced Settings hard to find.
It took me a while to stumble over the obvious! It’s hiding in plain sight.
Alas, there are but a few hits searching for “Windows Advanced Sound Settings”
In a nutshell, when you open Audio Settings, Advanced Sound is at the BOTTOM.
For those interested, here’s how I navigate to it: I click Windows search and enter “Audio Settings”

Sound Settings then appears at the top of my results ….

The regular Sound Settings panel then opens …

The option for Advance Sound appears at the very BOTTOM of that panel (green highlighter above)
I click on that and get the Advanced Sound options as show below …

My system has a VERY long list of apps. I edited out all those not pertinent to this crowd <laugh>.

The very first mapping option is that of the Windows Default itself and also System Sounds.
Most systems would have the Input/Output of those two set to their Microphone/Speakers

In my nerdy audio setup, I set my default Mic/Speakers to be my virtual mixer, VoiceMeeter.
Same idea, just different paths. 99% of users should just leave them set to Mic/Speakers.
The remapping magic happens with the individual entries for each running app.

Note that I said “Running”. That is because only running apps will appear in the list.
No worries. Even if you set an app’s paths then close that app, its remap is retained.
So, be sure that the apps whose audio you want to remap are running so you can see and set them.

In the above example, I have WSJT, JTA, and GridTracker running so I can alter their paths.
Note: JTA and GT are both set to “Default” (which itself is set at the very top).
I left them as default since they both have their own device selection (now working).
Note: FireFox’s output is remapped to “Cable C” which is an input to my virtual mixer.
That way, I can control and/r mix the audio from Firefox as I see fit.
Note: My mixer, VoiceMeeter, then maps back to Windows default after its mixing is done.

Another case where this is handy is where JTA, WSJT and HDSDR are fighting for ports.
My remapping to different paths (my mixer’s inputs in my case), the conflict is resolved.

That’s about it. As I said, most people will never need this flexibility but its there and easy to use.
Re funky changes to system? Nope. Safe, simple, and transparent.
The remapping is totally transparent and doesn’t alter anything deep under the covers.
Win simply looks for any audio remaps of an app and reroutes audio accordingly.
It allows you to set the audio path for any of the currently active apps.
The app must be active to see it in the list and enter the remap.
All apps default to the default path as specified at the top of the panel.
You can then set the app’s desired audio in/out paths (Mic and Speaker).
Prior to any remapping, each app defaults to the default paths which are set at the very top of that panel.

In summary, the Advanced Sound options affords you the same flexibility as an app having its own path option – except it even works for all those apps that don’t have their own audio device option. I think the order of precedence is app path then Win Remap.

KT1TK / TomK / 73

Show quoted text

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Friday, June 18, 2021 4:57 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Possible work-around for NAudio's lack of .Net 5 audio port selection

On 18/06/2021 6:29 pm, TomK wrote:

As always, thanks for your time, Laurie.
Even so, the Windows Advanced Audio Remapping remains a key player in my Digital Zen workflow.
It should work with any paths that go to Windows default - be they NAudio, LaurieMagic, or lesser players 😊
I use it now to redirect most of my Digital Zen audio paths – WSJT, Motu-Mics, general web audio, etc.
I’ll happily await your next magical iteration.
TomK 73

While Windows may offer a solution via Advanced Audio Remapping, which I have failed to find any mention of in my searches, if it requires an end user to make configuration changes to their system, that alone is enough to make it a non-starter IMO. If I can't get users to read simple release notes, getting them to make complicated (I am guessing here) configuration changes to their system would be a support nightmare.

All is not lost, earlier today a updated version of NAudio was released. That version doesn't suffer from the NET 5.0.7 induced sound playback failures. I reversed all the sound playback changes in the soon to be released JTAlert 2.50.2, bringing NAudio back into the code. A new build has been sent to the Test team. My own tests and the initial reports from the Test team all confirm that audio playback is now working correctly on systems running the latest NET 5.0.7 Desktop Runtime.

I had planned to ship JTAlert 2.50.2 on 21-June, but due to todays recoding/testing activity, I have pushed that out an extra day to 22-June.

de Laurie VK3AMA

Re: Multiple operator using separate Windows user login - problems

Michael Black

#35678

Hi Rory,

If you're around tomorrow perhaps we can link up and take a look.

I've set up a 2nd account like that before.

What's a good time to call you and what's your #? I'm usually available after 0800 Central time.

Mike W9MDB

Show quoted text

On Friday, June 18, 2021, 06:39:45 PM CDT, Rory Davis, N7CR <n7cr@...> wrote:

[Edited Message Follows]

Has anyone had luck with setting up a separate Windows user account for a 2nd operator? The XYL really wants to get active on FT8 but I'm having trouble making it all work together.

Using Win4YaesuSuite, Log4OM2 with Omni-Rig, W WSJT-X and JTAlert.

The setup still works with my Windows user account.

The first account all these apps are shut down and logged out of the account before attempting the second account.

.
In the second account, the sound devices do not appear in the Sound ON | Sound Output Device > dropdown list. Nor does JTAlert appear in the Windows Volume Mixer. Under the Manage Settings window, both the rig sound device and the speakers are available as options, so the Speakers selection is set in the Settings window.

It appears that JTAlert is not communicating with WSJT-X either, though the settings are the same for both user accounts.

Also JTAlert and WSJT-X are not communicating with Log4OM2 but omni-rig is working OK.

Is there another/better way to add a second operator with the above combination of software?

Re: JTAlert is blank #FT8

ag5pc@...

#35677

I changed the WSJT-X startup to include "rig-name" and everything started working. Norton is still installed and running.

JTAlert Instance : #1

JTAlert Start Params : /wsjtx

WSJT-X Window Title : WSJT-X - Flex60001 v2.4.0 by K1JT, G4WJS, K9AN, and IV3NWV

WSJT-X Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe" --rig-name=Flex60001

WSJT-X --rig-name : Flex60001

WSJT-X Config File : C:\Users\Al\AppData\Local\WSJT-X - Flex60001\WSJT-X - Flex60001.ini

WSJT-X Version : 2.4.0

WSJT-X Revision : c19d62

WSJT-X Spec Op Mode : None

WSJT-X UDP ID : WSJT-X - Flex60001

WSJT-X UDP Port : 2237

WSJT-X UDP Server : 127.0.0.1

WSJT-X UDP MCast on Loopback : True

WSJT-X UDP Max Schema : 3

==================================================

UDP Ports used

--------------------------------------------------

JTAlert.exe : 53280 52050

JTAlertV2.Manager.exe : 59184 59185

JTAlertV2.Decodes.exe :

==================================================

Audio output devices

--------------------------------------------------

[1] Speakers (Realtek High Definition Audio)

[2] DAX RESERVED IQ RX 1 (FlexRadio Systems DAX IQ)

[3] DAX RESERVED AUDIO RX 2 (FlexRadio Systems DAX Audio)

[4] DAX RESERVED MIC AUDIO (FlexRadio Systems DAX MIC Audio)

[5] DAX RESERVED IQ RX 4 (FlexRadio Systems DAX IQ)

[6] DAX RESERVED AUDIO RX 1 (FlexRadio Systems DAX Audio)

[7] DAX RESERVED IQ RX 2 (FlexRadio Systems DAX IQ)

[8] DAX RESERVED AUDIO RX 8 (FlexRadio Systems DAX Audio)

[9] DAX RESERVED AUDIO RX 6 (FlexRadio Systems DAX Audio)

[10] DAX RESERVED IQ RX 3 (FlexRadio Systems DAX IQ)

[11] DAX Audio TX (FlexRadio Systems DAX TX)

[12] DAX RESERVED AUDIO RX 3 (FlexRadio Systems DAX Audio)

[13] DAX RESERVED AUDIO RX 4 (FlexRadio Systems DAX Audio)

[14] DAX RESERVED AUDIO RX 7 (FlexRadio Systems DAX Audio)

[15] DAX RESERVED AUDIO RX 5 (FlexRadio Systems DAX Audio)

==================================================

JTAlertV2.Manager (2.16.17.0) status

(2021-06-19 00:47:40 utc)

--------------------------------------------------

NET Framework : .NET Framework 4.8.4341.0

CLR Version : 4.0.30319.42000

--------------------------------------------------

UDP Router : Initialized * : YES (WSJT-X - Flex60001)

Audio : Initialized * : YES (15 output devices)

BandData : Initialized * : YES

Text Msgs : Initialized * : YES (started : 17)

HamSpots : Initialized * : YES

QRZ Xml : Initialized * : YES (AG5PC)

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 Chk : Initialized * : YES

Maintenance : Initialized * : YES

Re: New install

Chris Levingston

#35676

Hi Laurie.

I already looked for it off-screen and it does not appear in the taskbar.

The Help>About window does not work.

HOWEVER, I wondered whether the previous version of JTAlert was causing problems, so installed HRD, WSJT-X and the latest build of JTAlert on my laptop (which has never had any of them installed, and is only used for Zoom club meetings and to give me a big display on my Nano VNA) and it all works fine there.

I guess that I now need to completely uninstall the old JTAlert installation while keeping the log and settings, so open to any advice.

As always, your help is greatly appreciated - Chris