On 7/01/2021 12:40 pm, Steve Roth wrote:

Unfortunately, it did not work. I used my two-month log entries from HRD, and used that to create the new "B4" adif per the app, which I loaded.  I did several tests to see if old qso's would show up as "B4", but they did not.

There will likely be something unusual with the ADIF file you used. Send it to me direct and I will test it. Send to  vk3ama.ham.apps [at] gmail.com

de Laurie VK3AMA

Fair enough.... thanks Laurie!

73,

Marlo
KA2IRQ

Laurie is working on an updated user interface that will
eliminate the "4 row" limitation. Just how far along that
is - and when it will be ready for public release - I do
not know as I no longer have access to the beta group.

73,

... Joe, W4TV

You could set JTAlert to show only CQs only, or Alerts only, or both. You could also select to not show B4s. Any of those, or any combination, would reduce the number of calls being displayed.

Or um, use the decodes window...

JTAlert has 36 “boxes” that display the received stations. Many times there are more than 36 with the remaining stations not displayed.

 

Please consider increasing the number of boxes. Maybe another row which would be 45 stations displayed. Perhaps the number of boxes could be adjusted by user in Settings.

 

Otherwise, JTAlert is a very handy app and I appreciate having it.

 

Thank you and 73,

Dick, KD4S

_._,_._,_

---

Dick,

You could set JTAlert to show only CQs only, or Alerts only, or both. You could also select to not show B4s. Any of those, or any combination, would reduce the number of calls being displayed.

73,

Jim N6VH

JTAlert has 36 “boxes” that display the received stations. Many times there are more than 36 with the remaining stations not displayed.

 

Please consider increasing the number of boxes. Maybe another row which would be 45 stations displayed. Perhaps the number of boxes could be adjusted by user in Settings.

 

Otherwise, JTAlert is a very handy app and I appreciate having it.

 

Thank you and 73,

Dick, KD4S

Hi,

 

I am having a random problem with WSJT-X and JT Alert apparently conflicting somehow.  First, I little information about my setup.  I am using a Yaesu FT-991A which has an internal sound card and is connected to my Windows 10 computer via a USB connection.  When I run WSJT-X all by itself, it seems to work flawlessly.  However when I run it with JT Alert, something happens randomly that on a transmit cycle, my transmitter will key up but there is no output power showing on my wattmeter.  If I close JT Alert, sometimes the problem is solved and other times I have to shut down WSJT-X as well to get things working again.  BTW, I have Sound OFF in JT Alert if that makes a difference.

I am running WSJT-X v.2.2.2 and JT Alert 2.16.17

 

JT Alert is a great program, just wish I could use it with WSJT-X reliably.  Any suggestions for a fix would be greatly appreciated.

 

Thanks and 73,

Dave

K5HC

Hi Mike, mny tnx!

73s, Camillo iz6gvc

Hi Mike, I find the info directly on the help of the JTAlert sw?

Thanks, Camillo iz6gvc

Hi,
I made a new PC with W10, now I would to transfer all the settings of JTAlert on the new PC.
How I can make this operation?

Thanks, Camillo iz6gvc

Is it possible for the 4x9 grid of decoded callsigns to be sorted by
priority?  Often I'll see a call go by that got highlighted, but on
the next sequence (i.e. 30 seconds later), even though the call was
decoded again, there can be too many callsigns to put in the grid, and
the one I wanted to see again no longer fits.  This means it's not
there to click on.  I could be in the middle of a QSO which would
prevent me from clicking on it when I saw it go by the first time.

I'd prefer the highest-priority calls to be in the upper-left-hand
corner, while the lowest priority calls are in the lower right corner.
Whether they are sorted vertically first then horizontally or vice
versa doesn't matter to me.

Short answer... NO

Long answer... Any sort of callsign sorting will require that all decodes have been processed and delivered by WSJT-X before JTAlert can produce a sorted display. That could be several seconds of dead (non-display) time depending on you PC capability and how busy the Band.

If you're overflowing the 4x9 grid with callsigns, there are a couple of options...

1. Apply one or more Alert filters when you're on a busy band to remove the Callsigns you're unlikely to want to work, say filter out the B4's or Callsigns not generating alerts.
   
   
2. Use the Decodes window, it has no limit on the Callsigns displayed in a period, unlike the main JTAlert window. You can even view decodes from a previous periods. Callsigns in the Decodes window obey the same mouse clicks as the main JTAlert window.
   

de Laurie VK3AMA

I don't see that "Log WSJT-X COntrest Exchanges (DXK...."  in version 2.16.16..

I have >> 

Mark  N3RDV

There are more options, you need to scroll down. Did you miss the highlighted vertical scrollbar (on the right) in my original post?

I don't see that "Log WSJT-X COntrest Exchanges (DXK...."  in version 2.16.16..

I have >> 

Mark  N3RDV

Is it possible for the 4x9 grid of decoded callsigns to be sorted by
priority? Often I'll see a call go by that got highlighted, but on
the next sequence (i.e. 30 seconds later), even though the call was
decoded again, there can be too many callsigns to put in the grid, and
the one I wanted to see again no longer fits. This means it's not
there to click on. I could be in the middle of a QSO which would
prevent me from clicking on it when I saw it go by the first time.

I'd prefer the highest-priority calls to be in the upper-left-hand
corner, while the lowest priority calls are in the lower right corner.
Whether they are sorted vertically first then horizontally or vice
versa doesn't matter to me.

--
Jim Reisert AD1C, <jjreisert@...>, https://www.ad1c.us

had to reset all groups.

is this one working?