Date   

locked Re: F5 Text message operation

K0GU
 

I already had that unchecked. I FT8 on JTDX if that makes any difference. I'll double check to see I didn't have the problem then unchecked the box.
--
73,  Jay  K0GU


locked v2.50.1 Second or third FT8 contact logged as FT8 with FT4 sub-mode.

Ron W3RJW
 
Edited

Thanks for all the changes. 

I'm having a problem with 2nd or 3rd FT8 contact in a run being logged with a FT4 submode. I did not go on from there. Happened more then once after pausing to check things and then making contacts again. I also did not try any other modes yet.

I log to HRD from JTAlert. Settings as normal (removal of ADIF compliant option noted).   Did I miss something else ?

64 bit version.

Best captured in EQSL.  (Having trouble adding screen capture.)


--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.4.0 rc4, JTAlert 2.50.1, HRD Deluxe v6.7.0.323
FTdx-3000, SignaLink USB


locked Re: JTAlert not decoding

dpaschal@...
 

I installed wsjt-x v2.3.1 as well as JTAlert 2.50.1 and all is working now.  Not sure what the cause was though.  You can close this one.


locked #Announcement #NewRelease JTAlert 2.50.1 is available #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The latest JTAlert version 2.50.1 is now available @ https://hamapps.com/JTAlert/

Many fixes, changes and new functionality.

JTAlert is now distributed as separate 64bit and 32bit packages. Install the package that corresponds to your Windows architecture type, x64 (64bit) or x86 (32bit).

Please review the release notes at the end of this message.

de Laurie VK3AMA

Release Notes.

2.50.1 (2021-May-01)

  *** Includes Callsign database file version 2021-05-01 (2021-May-01)

  New:

    - JTAlert: Is now distributed as individual x86 (32bit) & x64 (64bit) builds.
       Windows 32bit requires the x86 build, while Windows 64bit can run either
       the x86 or x64 build. The x64 build is recommended for Windows 64bit.
       Note: The .NET desktop runtime architecture must match the architecture
       type of the JTAlert installer, x86 or x64.

    - Messaging window: Ability to delete all messages. Available via the right-click
       menu of any visible message or the right-click menu of the Options (gear) icon.

    - Callsigns, Messaging, Activity and Band Heat windows: Window background color
       and other areas depending on the window are now user settable. Note: this is
       not full featured window theming (set for a future release) just the most
       prominent areas can be altered. The Config popup, tooltips and context menus
       are not changeable they will still obey the color theme you are using for Windows.
       See under the Colors section of the Options popup (click the gear icon).

    - Callsigns window: The callsign right-click context menu can be customized.
       It can be turned off completely or individual entries can be hidden.

    - Activity window: Data column text alignment is adjustable, either Left, Right,
       Center or Mixed, where Mixed is Right aligned for the Tx counts and Left
       for the Rx counts. See the Bands view of the Options popup (click gear icon).


  Changed:

    - Callsigns window: The divider-bar between the main callsigns view and the
       callers view is now moveable, drag while holding the left mouse button
       down. The callers view can now display multiple rows or columns depending
       on the display position and the area available after dragging the divider.
       The callers view width/height after moving the divider is remembered and
       restored at startup. The callers view no longer auto-opens when callers
       first appear and no longer auto-closes when there are no callers.

    - Callsigns window: Online indicator (star icon) now has a size selector.
       Previously it used the QSL flag size selector. See the Options popup
       of the Callsigns window.

    - Messaging window: WSJT-X DX Call changes now no longer auto populate the
       Callsign field if a message is already being composed. That is if the
       message field contains text, the DX Call change is ignored.

    - Statsbar hiding: The option to hide the statusbar for windows has been
       removed. The statusbar is now always shown. This change affects the
       new Activity, Callsigns & Messaging windows introduced with 2.50.0.

    - WSJT-X highlighting: B4 and ignored Callsign highlighting in the WSJT-X window
       can now be turned off via a checkbox in the Settings window, "Applications
       -> WSJT-X / JTDX" section. Note this does not apply to JTDX, it doesn't
       support decode coloring.

    - FT4 logging: The option to log FT4 QSOs as Mode=FT4 rather than the adif
       compliant specification has been removed. This affects all Logs except
       ACLog, HRD5, and HRD6 (up to 6.2).

    - FT4, Q65 & FST4 logging: FT4, Q65, & FST4 mode QSOs are now logged using the
       official adif specifications (3.1.2) of Mode=MFSK & Submode=Q65, FST4 & FT4
       respectively.


  Fixed:

    - Windows 32bit (x86): Installer would incorrectly report the .NET 5 Desktop
       Runtime was not installed. JTAlert would execute with several fatal errors.

    - ADIF log: Very slow import at startup. (2.50.0 defect)

    - Q65 decodes: Not displayed in the Callsigns window. (2.50.0 defect)

    - All loggers: Solar data (SFI,A,K) not logged. (2.50.0 defect)

    - WSJT-X: Control key pressed state, for changing WSJT-X TX frequency, not used
       when Callsign is clicked in the Callsigns window. (2.50.0 defect)

    - Messaging window: Incorrect scaling (zooming) applied to messages and the
       Options popup. (2.50.0 defect)

    - Callsigns window #2 and higher: For all instances except #1, not following
       the JTAlert window state (minimize, restore or bring forward) despite the
       "Follow JTAlert window" setting being enabled. (2.50.0 defect)

    - Callsigns window: DT median value in statusbar not shown or doesn't change
       over time. (2.50.0 defect)

    - DXLab integration: The DXKeeper, Pathfinder and DXView lookups missing
       from the right-click context menu of the callsign displays in the Callsigns
       window. (2.50.0 defect)

    - Config backups: Config backup files, older than 7 days, not being deleted
       by the automated file maintenance routine.


  Unresolved Defects:

    - Marathon Alert: Triggered countries and zones not being shown in the callsign
       info tooltip of the Callsigns window. (2.50.0 defect)

    - Messaging: Only available on the first instance (#1) of JTAlert and its child windows.



locked Re: F5 Text message operation

HamApps Support (VK3AMA)
 

On 1/05/2021 4:12 am, K0GU wrote:
I had this happen shortly after 2.50 came out. The station that got the unintended message replied to my ramblings about Cycle 25. I would like to be able to turn this auto call select feature off.
--
73,  Jay  K0GU

That option already exists. Turn off the "Follow WSJT-X DX Call" setting. Simple!

   

de Laurie VK3AMA




locked Re: Greetings from Japan; Japanese language sound file revision request

HamApps Support (VK3AMA)
 

On 30/04/2021 5:47 pm, shibata.naoki@... wrote:
Hello, I've been a JTalert user since 2015, and want to say thank you for all development efforts.

Just upgraded my installation from 2.1.xx to 2.50, and found Japanese version sound files.
Tried it and found that announce grade is professional, but the translations for some alerts are completely wrong.

I strongly recommend fixing the translation of, at least, the followings:
CQ: -> (now) Q wo miru (meaning "see Q")  (should be) CQ, or shii kyuu
New State -> (now) atarashii joutai (meaning "new status")  (should be)  atarashii shuu
New VE Prrovince -> (now) atarashii shuu (new state)  (maybe changed to ) atarashii kanada (canada) no shuu
Wanted DXCC -> (now) DX  (maybe) DXCC
Wanted Callsign -> (now) Shimei tehai ("wanted" as in seeking criminals)  (should be)  hoshii kohru(call), or hitsuyou na kooru(call)

please consider revising the Japanese sound file at the next possible opportunity.

73,
NIcky/JH8JNF

Hi Nicky,

Thanks for the report on the sound files.

All the sound files are computer generated. For non-english voiced sounds there is an additional translation step where the English word or phrase is first translated to the target language, Japanese (Kanji) in your case, than that translation is used to generate the audio files. It is that first translation from English to Japanese that is the problem. For single words that have multiple meanings depending on the context in which the word is used, it is possible that the wrong English->Japanese translation is used to generate the voice file. That is what you're experiencing.

I can override the the English->Japanese translation for individual sounds as all translations are recorded in a database which is then used to drive the audio generation. All the Japanese translations are in Kanji. Are you able to provide Kanji translations for the incorrect sounds?

de Laurie VK3AMA


locked Re: F5 Text message operation

K0GU
 
Edited

> I start typing a response to an F5 message while calling CQ.  When a NEW station calls me back,
> their call replaces the call in the DX Call (WSJTx) and also in the F5 message window.

I had this happen shortly after 2.50 came out. The station that got the unintended message replied to my ramblings about Cycle 25. I would like to be able to turn this auto call select feature off.
--
73,  Jay  K0GU


locked Re: JTAlert not decoding

Laurie, VK3AMA
 

On 1/05/2021 2:01 am, dpaschal@gmail.com wrote:
If I click View and then I click any of those with the yellow star beside them or press the function key (F3, etc), I do not get any other window popping up.  Like View, Callsigns Window does not show another window.
That indicates that either the JTAlertV2.Manager.exe process is not running  or the UDP comms between the main JTAlert.exe process and the Manager process is being blocked. Both scenarios indicate likely Protection software interference.

What does the JTAlert "Help -> About" window show in the "Current operating state" section. Post the results. DON'T post an image!, use the clipboard copy icon to copy the entire contents of that section and past into a message.

On the subject of posting images. Please stop the posting of imgur hosted images. It is not needed and is often scaled down such that it is unreadable (like your most recent image). Simply insert the image in your message, all email clients support this as does the groups.io web interface.

de Laurie VK3AMA


locked Re: Independent audio alert s #FT8

Laurie, VK3AMA
 

On 30/04/2021 11:08 pm, Pat N6PAT via groups.io wrote:
The reason I ask is that with my Flex 6700 I run many instances simultaneously for different bands. If I could specify custom band specific audio alerts for wanted DX , States, etc. such as "Wanted DX on 10 meters" that would save me having to search each band in WSJT-X for the wanted DX if the time interval elapses and the wanted call sign disappears from the call sign window.
Try using the Decodes window. It provides a single display of decodes from all JTAlert instances. Set it to display only Alerted decodes and perhaps move the Band column over adjacent to the Callsign Column and if the other data is of no interest hide those columns. End result is a display of Callsigns and Bands of decodes generating Alerts.

de Laurie VK3AMA


locked Re: Independent audio alert s #FT8

Michael Black
 

Here's some more powershell that will display a popup box and an audio alert.
You could customize the popup message to include the alert info.

But you already get audio alerts from JTAlert so you need something else?
You can build custom text-to-speech stuff too.

rem powershell [console]::beep(1000,300);[console]::beep(500,300)
powershell -c (New-Object Media.SoundPlayer 'C:\ProgramData\HamApps\Sounds\_Wanted_Call.wav').PlaySync();
powershell (New-Object -ComObject Wscript.Shell).Popup("""This is my popup box!!""",0,"""Done""",0x0)

Mike W9MDB




On Friday, April 30, 2021, 09:33:36 AM CDT, Pat N6PAT via groups.io <n6pat@...> wrote:


That sounds good but I'm looking for real time audio and visual alerts while I'm working on my computer.


locked Re: JTAlert not decoding

Tom Melvin
 

Looks like you don’t have comms between wsjt-x and JTAltert - the ????m in the header - that should show the band you are on - ??? means no comms.

Take Log4OM OUT of the equation - it ay be clashing on ports e.g. don’t start it. Stick with WSJT-X and JTAlert ONLY.
Double check wsjt-x has all three boxes ticked for UDP.

Any messages on start up - check JTAlert -> Help for list of running services (Sorry not in shack at present and can’t remember which help option shows it.

Tom
GM8MJV

On 30 Apr 2021, at 15:32, dpaschal@gmail.com wrote:

I have LOG4OM2 and WSJT-X running. I am able to launch JTAlert but the window is presents has no decoded information in it. I will link a screenshot. I think I have it configured correctly but would appreciate a step-through of things to check. I have attempted to watch some youtube videos on it but the information on getting these three applications working is a bit sparce.

<a href="https://i.imgur.com/s4his7i.png"><img src="https://i.imgur.com/s4his7im.jpg"></a>

-David, WB4IHY


locked Re: JTAlert not decoding

dpaschal@...
 

If I click View and then I click any of those with the yellow star beside them or press the function key (F3, etc), I do not get any other window popping up.  Like View, Callsigns Window does not show another window.


locked Re: JTAlert not decoding

Joe Subich, W4TV
 

That is as expected. With 2.50.0 the decoded callsigns have been to a
new "CALLSIGNS" Window. Click "View -> Callsigns Window" to open that
window.

Click Help -> Open JTAlert 2.50 features Help File (F1) for info and
help on all the new windows/features in 2.50.

73,

... Joe, W4TV

On 2021-04-30 10:32 AM, dpaschal@gmail.com wrote:
I have LOG4OM2 and WSJT-X running.  I am able to launch JTAlert but the window is presents has no decoded information in it.  I will link a screenshot.  I think I have it configured correctly but would appreciate a step-through of things to check.  I have attempted to watch some youtube videos on it but the information on getting these three applications working is a bit sparce.
<a href="https://i.imgur.com/s4his7i.png"><img src="https://i.imgur.com/s4his7im.jpg"></a>
-David, WB4IHY


locked Re: Independent audio alert s #FT8

Pat N6PAT
 

That sounds good but I'm looking for real time audio and visual alerts while I'm working on my computer.


locked JTAlert not decoding

dpaschal@...
 

I have LOG4OM2 and WSJT-X running.  I am able to launch JTAlert but the window is presents has no decoded information in it.  I will link a screenshot.  I think I have it configured correctly but would appreciate a step-through of things to check.  I have attempted to watch some youtube videos on it but the information on getting these three applications working is a bit sparce.  

<a href="https://i.imgur.com/s4his7i.png"><img src="https://i.imgur.com/s4his7im.jpg"></a>

-David, WB4IHY


locked Re: unable to launch program

dpaschal@...
 

You can mark this one closed.  After about a day or two of not being on the air with it, I decided to take a day off and launch JTAlert to try and troubleshoot it.  It opened right up.  However, now it is not decoding.  Which is what it was doing before it wouldn't even launch.  So I will open another topic on that.


locked Re: Independent audio alert s #FT8

Michael Black
 

The email alert tells you the band.

Mike W9MDB




On Friday, April 30, 2021, 09:15:41 AM CDT, Pat N6PAT via groups.io <n6pat@...> wrote:


I don't think that would work. I'm looking for the ability to allow independent instance customized audio alerts to indicate which band (instance) is triggering the alert(s). I dedicate each instance to a particular band.


locked Re: Independent audio alert s #FT8

Pat N6PAT
 

I don't think that would work. I'm looking for the ability to allow independent instance customized audio alerts to indicate which band (instance) is triggering the alert(s). I dedicate each instance to a particular band.


locked Re: Independent audio alert s #FT8

Michael Black
 

Have you thought about using the JTAlert email notices?  You can have them sent to your phone too.

I've got a powershell script that is available on my QRZ page that works with numerous email source.

Mike W9MDB





On Friday, April 30, 2021, 08:09:07 AM CDT, Pat N6PAT via groups.io <n6pat@...> wrote:


Laurie,

You mentioned that independent instance profiles would be something in a future release. Would that include independent audio alerts as well?

The reason I ask is that with my Flex 6700 I run many instances simultaneously for different bands. If I could specify custom band specific audio alerts for wanted DX , States, etc. such as "Wanted DX on 10 meters" that would save me having to search each band in WSJT-X for the wanted DX if the time interval elapses and the wanted call sign disappears from the call sign window. 

Thanks, Pat


locked Independent audio alert s #FT8

Pat N6PAT
 

Laurie,

You mentioned that independent instance profiles would be something in a future release. Would that include independent audio alerts as well?

The reason I ask is that with my Flex 6700 I run many instances simultaneously for different bands. If I could specify custom band specific audio alerts for wanted DX , States, etc. such as "Wanted DX on 10 meters" that would save me having to search each band in WSJT-X for the wanted DX if the time interval elapses and the wanted call sign disappears from the call sign window. 

Thanks, Pat

3161 - 3180 of 37666