Hi, I'm happy with Log4OM2 as an occasional HF contest logger and appreciate that's not it's forte. Just two observations from this weekend's WW WPX contest:
In contest mode, you can tab forward from callsign to the Contest Rcvd field, but you can't tab back to the callsign field (or I couldn't anyway). I'm not sure where the active field is, as the cursor just seems to disappear.
I've seen previous comments about slow callsign checking when contest logging. I experienced this too. I am using a new laptop (Intel Core i7-1195G7 Quad Core 2.90Ghz, 16Gb RAM). I disabled QRZ lookup, cluster display and I don't export QSO information. I'm not sure if it is QSO count or elapsed time related, but an occasional close down and restart of Log4OM2 did the trick. Without this, the few second DUPE checking becomes an issue and slows the QSO up. After a restart of Log4OM, it's instant lookup again (I'm amazed how fast this new laptop closes and restarts the app...didn't realise my old one was so slow!). In 24 hours I logged 900+ QSOs, so nothing too taxing for the application. I had the contest start & end parameters set correctly. At a guess, I would say 3 hours of operation highlights the issue.
Hope this info helps!
Thanks.
Ian.
Occasional Contesting - Observations
Re: Occasional Contesting - Observations
Hi Ian,
I agree great product and that contests are not what it's for directly, but I too experienced a significant slow down in its performance over the weekend contest.
Dupes came up more slowly, lookups became so slow between QSO's and the messages 'not responding' came up several times during my use I too in the top bar. I restarted twice on Sunday to try and speed it back up and each restart it was fine again in terms of speed.
I also experienced on at least 4 occasions where the whole tables of my QSO's went blank with little red cross icons appearing whilst it did something to catch up. I only recorded 150 contacts over the two days as I was dipping in and out for fun so it wasn't even a big log to check.
I'd also turned off the download during contest checkbox in the options, although I kept the cluster running.
I don't think it is machine specs related problem as although my logging machine lacks your specs it is still quite reasonable.
Here I'm Running an 64bit I7 1.73GHz, 8GB Ram and I made sure I wasn't running anything else in the background on windows 10. I even did a task manager before I began and shut down all the chrome tasks before I started as I know that can be a pain sometimes. I did see that LOG4OM was up to 630MB of memory use so whilst up there its not unexpected for an application that is doing so much.
Any help from the Alpha team gratefully received as other than the slowdown hiccups LOG4OM worked really well in terms of what I wanted in the process.
Thanks
I agree great product and that contests are not what it's for directly, but I too experienced a significant slow down in its performance over the weekend contest.
Dupes came up more slowly, lookups became so slow between QSO's and the messages 'not responding' came up several times during my use I too in the top bar. I restarted twice on Sunday to try and speed it back up and each restart it was fine again in terms of speed.
I also experienced on at least 4 occasions where the whole tables of my QSO's went blank with little red cross icons appearing whilst it did something to catch up. I only recorded 150 contacts over the two days as I was dipping in and out for fun so it wasn't even a big log to check.
I'd also turned off the download during contest checkbox in the options, although I kept the cluster running.
I don't think it is machine specs related problem as although my logging machine lacks your specs it is still quite reasonable.
Here I'm Running an 64bit I7 1.73GHz, 8GB Ram and I made sure I wasn't running anything else in the background on windows 10. I even did a task manager before I began and shut down all the chrome tasks before I started as I know that can be a pain sometimes. I did see that LOG4OM was up to 630MB of memory use so whilst up there its not unexpected for an application that is doing so much.
Any help from the Alpha team gratefully received as other than the slowdown hiccups LOG4OM worked really well in terms of what I wanted in the process.
Thanks
