@PE4KH last time I checked, and my current setup is built around, #cqrlog on linux was the option with the most integration features, and more complete overall.
Curious about what your next steps will be, good luck!
Boy howdy, that was a bit of a hassle. Most things worked on the first go, though each app of course needed configuration, & some were helped by copying config files from the old computer to the new(er) one.
#CQRLog was the worst. I hoped that copying the entire directory (with its databases) would work, but it threw many errors. Had to un-install #MySQL then install #MariaDB (which is really MySQL), then import #ADIF files from the other one's exports. But I got there.
I need some #HamRadio help with the #DXCluster feature in #CQRLog
The documentation I've seen about filtering is written by and for people who really love man pages for advanced networking stuff.
I need something SIMPLE. Like check boxes in a GUI.
How do I tell it "Only show spots if they were HEARD by a station IN MY COUNTRY?!
The fact that some station in France can hear some other station in Europe is beyond not useful.
I'm going to try something a little different.
Usually, I'd tell #CQRLog to start a fresh log just for a contest or event, e.g. #WinterFieldDay
But for now, I'm going to install GridTracker, & feed it no old logs, and set it up to injest only fresh logs from WSJT-x and fldigi.
Then GridTracker will show me what states I haven't yet worked (multipliers for Field Day), and maybe even prevent me from working a dupe (same station-band-mode).
I THINK it works that way.
#GridTracker WSJT-x and #CQRlog
How to use CQRlog for overall log management, yet still also use GridTracker, and have them cooperate.