Date   

locked Re: v2.16.7 No Sound - Realtec - Windows 10 - WSJT-X v2.2.1

Norbert Graf - DD3KF
 

Hi Laurie,

hi All,

 

Since a few days I have also had problems with the audio alerts via JTAlert. Possibly after a Windows 10 64 bit update.

 

According to my observations, this seems to be a problem of Windows 10 and not of JTAlert, because I haven't had any audio output outside of JTAlert since that time.

 

I remembered many weeks ago someone suggested a solution. I have implemented this.

 

What have I done?

 

I installed a cheap USB sound stick (less than 10 US $) and declared this stick as the default device in the sound mixer.  The stick is not used operational.

 

After that I get audio alerts from JTAlert again via my Realtek High Definition Audio device.

 

Maybe other JTAlert users can solve the sound problem in this or a similar way.

 

73!

 

______________

Norbert Graf

52078 Aachen

 

 

 

 

Von: Support@HamApps.groups.io <Support@HamApps.groups.io> Im Auftrag von HamApps Support (VK3AMA)
Gesendet: Samstag, 13. Juni 2020 23:38
An: Support@HamApps.groups.io
Betreff: Re: [HamApps] v2.16.7 No Sound - Realtec - Windows 10 - WSJT-X v2.2.1

 

On 14/06/2020 6:22 am, Ralph Smith wrote:

Jacek, thank you. I would try that if I had a Realtek analog audio output. On my PC I am using the optical digital output on the soundcard to the optical input of my speakers. So there is no other Realtec output (See below) and I have already tried them all. And the current audio set-up works wery well, except for the updated release of the JTAlert software. The JTAlert software doesnt show up as an application in the volume mixer. I suspect its not operator error, but a change in the JTAlert software is preventing JTAlert from linking with the PC's audio application.


Ralph,

In bullet point form because it is easier to read/follow...

  • There were no changes to audio management in the recent release. There haven't been any changes for several releases.
  • Application volume sliders appearing in the Sound Mixer are controlled by Windows, JTAlert has no control over that.
  • The main JTAlert.exe executable doesn't perform any audio playback and will not appear in the Mixer.
  • All JTAlert audio is managed by the "JTAlertV2.Manager.exe" process and it is this process that will appear in the Mixer.
  • Application volume sliders in the Mixer will only become visible once Windows has detected a sound-play type event from the application.
  • An example from my Realtek (digital) output tests ...
    • Mixer before first sound is played from JTAlert.

    • Mixer after Windows has detected the JTAlert sound-play event.

  • To make your life easier, you can perform Sound Output device changes and play tests from the main JTAlert window without having to open the Settings window. Via the "Sound" menu.
  • I suggest you try tests against other Sound devices regardless of whether they will produce sound. Just a test to see if those devices will show "JTAlertV2.Manager" in the mixer after a test sound is played.
  • If "JTAlertV2.Manager" repeatedly doesn't show in the Mixer for other audio devices then the likely causes are your PC protection software interfering and blocking the UDP control message sent from JTAlert to the Manager process, the "JTAlertV2.Manager" itself is not running or the Audio module of the Manager is not initialized. You can check the status of all Manager modules via the JTAlert "Help -> About" menu.

If you still can't resolve use the "Help" (or "? ") -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

 

de Laurie VK3AMA


locked Re: JTAlert 2.16.7 #JTDX #HRD : stops working after several passes #JTDX #HRD

HamApps Support (VK3AMA)
 

On 14/06/2020 5:12 pm, Ludovic Ludo wrote:
Read better : I writed "WSJT-X (last version)"... So it is the 2.2.1 64 bits.
Sorry to disagree with you.
PSKReporter shows your still running the old buggy version of WSJT-X 2.2.0



Good Luck.

de Laurie VK3AMA


locked Re: #TIP #TIP

Jim Nakajima
 

Dear Laurie,

I thought it once, but still need some rare entity in Asia.
Okay I will try it at this evening and see what happens.

Thank you for your suggestion.
JA9IFF
Jim


locked Re: JTAlert 2.16.7 #JTDX #HRD : stops working after several passes #JTDX #HRD

Ludovic Ludo <f5pbg@...>
 
Edited

Read better : I writed "WSJT-X (last version)"... So it is the 2.2.1 64 bits.
My message is only a feedback for the creators of jt alert.

I no longer use jtalert and I just copy/paste the lines necessary to create an adi file of
C:\Users\name_session\AppData\Local\WSJT-X\wsjtx_log.adi
to import into HRD

Best reards,
Ludovic - F5PBG
http://radioamateur.forumsactifs.com


locked Re: #TIP #TIP

HamApps Support (VK3AMA)
 

On 14/06/2020 3:08 pm, Jim Nakajima wrote:
At last night (local time) on 20m Band, decoding results were obtained more than 50 stations in one sequence, even "Do not show Worked Before (B4) Callsigns" selected, thus the "callsigns display" window by 4 x 9 was insufficient.
Is there a method to exclude the callsign from the same DXCC entity?

JA9IFF
Jim Nakajima

Jim,

The isn't a Country Filter (yet) but there is a Continent Filter under the "Alerts -> Filters" menu.

Alternatively, what I personally do in these situations, is to engage the "Show only Callsigns generating Alerts" filter or the "Show CQ only Callsigns" filter, then later when the Band has become less active I will turn those filters off.


de Laurie VK3AMA


locked Re: " New station" alert

HamApps Support (VK3AMA)
 

On 14/06/2020 3:36 pm, Wojciech Tomczyk via groups.io wrote:
I would like to set alert which alerts me for a new station ( not in my log yet on this band) calling CQ,
I simply want to avoid duplication of QSOs , and have just one QSO per band.
Any suggestions how to do it?

Tom, SP7WT
Tom,

If you want to work Stations only once per band than enable the "Ignore Mode" option for the Worked B4 Alert.

de Laurie VK3AMA


locked #TIP #TIP

Jim Nakajima
 

At last night (local time) on 20m Band, decoding results were obtained more than 50 stations in one sequence, even "Do not show Worked Before (B4) Callsigns" selected, thus the "callsigns display" window by 4 x 9 was insufficient.
Is there a method to exclude the callsign from the same DXCC entity?

JA9IFF
Jim Nakajima


locked " New station" alert

Wojciech Tomczyk
 

I would like to set alert which alerts me for a new station ( not in my log yet on this band) calling CQ,
I simply want to avoid duplication of QSOs , and have just one QSO per band.
Any suggestions how to do it?

Tom, SP7WT


locked Re: My Country Location

HamApps Support (VK3AMA)
 

On 14/06/2020 12:57 pm, ve7gtc wrote:
I have a weird problem I am trying to track down. I  use JTDX to JTAlert to Log4OM V2 (newly installed). When I tried to upload to LOTW all qso's were rejected because my TQSL certificate says I live in Hawaii (which I do) and the upload said I lived in the United States (wrong entity).  I looked at the Log4OM program config, and it was correct, Hawaii. I looked at each individual entry, and each was changed to United States. Next I reconfigured so that JTDX logging went directly to Log4OM, without JTAlert. No problem, all, entries show correctly as Hawaii. I can't figure out what, in JTAlert, would cause the change in my QTH, as my grid square and region settings are correct. Any help appreciated.
Gus  K2GT

Gus,

Nothing to do with JTAlert. The only Country information it conveys in a logging request to Log4OM is the Country (DXCC), zones, etc for the logged station.

My guess is that it is a Log4OM issue, especially if it is newly installed. Log4OM does mass QSO manipulation if you don't tell it otherwise when you import a log into its log resulting is many changes to your old QSOs. My guess is that it altered your country in the log or it had the incorrect country set for your Callsign initially when you tried to upload via TQSL. I don't use Log4Om except for JTAlert integration testing, so I might be totally wrong.

What I do know is that neither WSJT-X or JTAlert include any information regarding your operating DXCC in the log data sent to Log4OM.

If Log4OM is now correctly uploading to LoTW, I suggest you put JTAlert back in the mix, it should still be OK, if it isn't then the likely cause is Lo4OM changing the dxcc as part if its input queue settings.

Let me know what you find.

de Laurie VK3AMA


locked My Country Location

ve7gtc
 

I have a weird problem I am trying to track down. I  use JTDX to JTAlert to Log4OM V2 (newly installed). When I tried to upload to LOTW all qso's were rejected because my TQSL certificate says I live in Hawaii (which I do) and the upload said I lived in the United States (wrong entity).  I looked at the Log4OM program config, and it was correct, Hawaii. I looked at each individual entry, and each was changed to United States. Next I reconfigured so that JTDX logging went directly to Log4OM, without JTAlert. No problem, all, entries show correctly as Hawaii. I can't figure out what, in JTAlert, would cause the change in my QTH, as my grid square and region settings are correct. Any help appreciated.
Gus  K2GT


locked Re: Clear B4

HamApps Support (VK3AMA)
 

On 14/06/2020 7:57 am, John Holmes W9ILY wrote:
Is this possible when using standard ADIF logging?

John W9ILY

Are you asking can the B4s be cleared for your current ADIF log when you are running in a Contest (as the OP requested)? If so, that's easy, just go into the Settings, "Alerts -> Worked B4" section and enable the "Ignore B4 status before this date" option and set the date to the date of the start of the contest.

de Laurie VK3AMA


locked Re: Clear B4

John Holmes W9ILY
 

Laurie,
Is this possible when using standard ADIF logging?

John W9ILY


locked Re: Wider window would be nice

HamApps Support (VK3AMA)
 

On 8/06/2020 11:45 pm, Mark via groups.io wrote:
JTAlert is Great, but I would like to have more information available horizontally.  I have JTAlert's display placed above the WSJT-X display and have room to expand JTAlert's information by four more display fields on each of the three existing rows.

Merk, K6FG

Sorry, that wont happen until JTAlertV3. With JTAlertV2 (the current series) all control placement in the main window is hard-code, it is a major undertaking to increase width and height in order to gain additional callsign display slots.

With the future JTAlertV3 there are no hard-code control placements in any of the windows. Every window can be resized at will and the layout with adjust accordingly. With the Callsigns display specifically, additional callsign display slots are automatically added as the window is resized horizontally, vertically, made full-screen, it doesn't matter.

de Laurie VK3AMA


locked Re: Worked B4 sometimes not working

HamApps Support (VK3AMA)
 

On 11/06/2020 12:46 am, Paul AC9O wrote:
An update... I am now running WSJT-X 2.2.1 and JTAlert 2.16.7 and both are working nicely. However, the occasional B4 is still not highlighting after a successfully logged contact.

Paul,

The non-display of B4 covers two different scenarios depending on who reported it.
  1. Non display of the "B4" after the Callsign in the JTAlert window.
  2. Non B4 coloring of a decode in WSJT-X.

If 1. applies, then likely 2. will apply.

If 1. does not apply, but 2. does, that is due to running an old WSJT-X version, this was corrected in WSJT-X 2.2.1

In your situation is it 1. & 2. or just 2. ?

de Laurie VK3AMA


locked Re: Clear B4

Don Farrar
 

Thank you.






Green statement: No trees were harmed in the sending of this email, but

billions of electrons were really agitated .



On Sat, Jun 13, 2020 at 5:41 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 14/06/2020 6:28 am, Don Farrar wrote:
I remember reading on how to clear the log in JTAlert so that when you switch from ACLog to VHF Contest log you don't get all logged B4 warnings. But I can't find that information now.
If that makes sense?

Thanks,

73,

VA3ZV Don

You don't clear the B4s, you change Logs. Your VHF contest log will likely not contain your everyday ACLog contacts. You need to tell JTAlert your using the VHF Contest Logger. See the "Tutorials -> N3FJP Contest Logs Logging" section of the Help file for instructions on proper setup (it is easy).

de Laurie VK3AMA


locked Re: Decodes window not always populating

HamApps Support (VK3AMA)
 

On 12/06/2020 6:23 am, John Holmes W9ILY wrote:
In have "Delete Old Records" checked and I do not use any filters.
Thanks.

John W9ILY

John,

When you get this non-population at startup what does the "View" message show in the Decodes status-bar? Does it show "0 Recs" or some-other value?

As a test, could you run a couple of JTAlert sessions with the Decodes set to delete all records on startup. Does the window still not populate the new JTAlert decodes?

de Laurie VK3AMA


locked Re: Decodes window not always populating

HamApps Support (VK3AMA)
 

On 12/06/2020 10:27 am, Joe Spear wrote:
I have the startup options set to "delete old records" and I do not apply a filter to the decodes display.

Joe W4WT

Joe,

When you get this non-population at startup what does the "View" message show in the Decodes status-bar? Does it show "0 Recs" or some-other value?

As a test, could you run a couple of JTAlert sessions with the Decodes set to delete all records on startup. Soe sthe window still not populate the new JTAlert decodes?

de Laurie VK3AMA


locked Re: Clear B4

HamApps Support (VK3AMA)
 

On 14/06/2020 6:28 am, Don Farrar wrote:
I remember reading on how to clear the log in JTAlert so that when you switch from ACLog to VHF Contest log you don't get all logged B4 warnings. But I can't find that information now.
If that makes sense?

Thanks,

73,

VA3ZV Don

You don't clear the B4s, you change Logs. Your VHF contest log will likely not contain your everyday ACLog contacts. You need to tell JTAlert your using the VHF Contest Logger. See the "Tutorials -> N3FJP Contest Logs Logging" section of the Help file for instructions on proper setup (it is easy).

de Laurie VK3AMA


locked Re: v2.16.7 No Sound - Realtec - Windows 10 - WSJT-X v2.2.1

HamApps Support (VK3AMA)
 

On 14/06/2020 6:22 am, Ralph Smith wrote:
Jacek, thank you. I would try that if I had a Realtek analog audio output. On my PC I am using the optical digital output on the soundcard to the optical input of my speakers. So there is no other Realtec output (See below) and I have already tried them all. And the current audio set-up works wery well, except for the updated release of the JTAlert software. The JTAlert software doesnt show up as an application in the volume mixer. I suspect its not operator error, but a change in the JTAlert software is preventing JTAlert from linking with the PC's audio application.

Ralph,

In bullet point form because it is easier to read/follow...
  • There were no changes to audio management in the recent release. There haven't been any changes for several releases.

  • Application volume sliders appearing in the Sound Mixer are controlled by Windows, JTAlert has no control over that.

  • The main JTAlert.exe executable doesn't perform any audio playback and will not appear in the Mixer.

  • All JTAlert audio is managed by the "JTAlertV2.Manager.exe" process and it is this process that will appear in the Mixer.

  • Application volume sliders in the Mixer will only become visible once Windows has detected a sound-play type event from the application.

  • An example from my Realtek (digital) output tests ...

    • Mixer before first sound is played from JTAlert.



    • Mixer after Windows has detected the JTAlert sound-play event.


  • To make your life easier, you can perform Sound Output device changes and play tests from the main JTAlert window without having to open the Settings window. Via the "Sound" menu.

  • I suggest you try tests against other Sound devices regardless of whether they will produce sound. Just a test to see if those devices will show "JTAlertV2.Manager" in the mixer after a test sound is played.

  • If "JTAlertV2.Manager" repeatedly doesn't show in the Mixer for other audio devices then the likely causes are your PC protection software interfering and blocking the UDP control message sent from JTAlert to the Manager process, the "JTAlertV2.Manager" itself is not running or the Audio module of the Manager is not initialized. You can check the status of all Manager modules via the JTAlert "Help -> About" menu.

If you still can't resolve use the "Help" (or "? ") -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.


de Laurie VK3AMA


locked Clear B4

Don Farrar
 

I remember reading on how to clear the log in JTAlert so that when you switch from ACLog to VHF Contest log you don't get all logged B4 warnings. But I can't find that information now.
If that makes sense?

Thanks,

73,

VA3ZV Don