Log4OM

Has anyone else had a problem with ver 2.10.0 being slow to respond on cluster picks? I didn't have this problem with the earlier version. Now it takes a second or two to load data but frequently will not move the frequency of my radio until I double click on the spotted station again. Not as fast as it used to be.
Rory, K5CKS

I briefly participated in the ARRL phone sweepstakes contest recently and had ver 2.10.0 running in contest mode with only SDR Console running. The program seemed to me very sluggish and at times I thought it was going to crash. My PC specs are:
Operating System
Windows 10 Home 64-bit
CPU
Intel Core i7 9700T @ 2.00GHz
RAM
16.0GB Dual-Channel @ 1330 MHz.

I am very new to Log4OM so I can't say how it has behaved over time.
More comments welcome!

I very much agree that there is an issue and in my case I would say it goes beyond sluggish and I would characterize it as "hanging up" if there is a heavy cluster load. See my post in the ERROR section of the forum "Log4OMv2 Hangs with increased cluster load". Although Log4om is not targeted as a contest logger, it offers the level of features sufficient for my needs. The inability to timely respond to clicks on the cluster is a real issue.

Ray Mikula
W9NZ

I see an issue where it takes very long to do a lookup after clicking a callsign from the cluster list.
Constantly i see HV0A in the callsign field ??? when ik click on a cluster callsign for a brief second the call is vissible in the then i changes to HV0A again and the program is locked for several seconds. ???

If you search these forums and Facebook you will find this is a known issue and that we are working on it!

I did search this forum and found this toppic.

And i never used and never will use Facebook.

Don't forget i only want to try to make log4om better

Thanks for the comment Terry, I am glad to know that the development team is aware of this. Keep up the great work guys! And Log4OM IS the best logging software in the world!
73,
Rory, K5CKS

I'm happy to report that the sluggishness I've been experiencing with recent versions has been greatly improved in version 2.13.0.0. I'm guessing the new caching feature has helped alot.