so ive been using N1MM for a while now mostly for contesting and it does what it does really well, no complaints there. but outside of contests i find it kind of clunky for just everyday DX logging, the interface doesnt really feel like its meant for casual use if that makes sense.

somebody at the club mentioned Log4OM and i installed it last week and honestly im pretty impressed with the general logging features, the QSL tracking and the way it pulls in clublog data is really nice. but then i started wondering if i could realistically use it for contests too or if ill still need to keep N1MM around for that.

also i run WSJT-X pretty regularly for FT8 and right now its feeding into N1MM via UDP which works fine but ive read that Log4OM can also receive from WSJT-X. has anyone actually tested that setup and does the dupe checking work properly across modes when youre logging FT8 contacts alongside SSB or CW in the same log? that part im not totally clear on.

not trying to replace N1MM for serious contesting, just wondering if anyone has found a workflow where Log4OM handles the day to day stuff and N1MM takes over for contest weekends without it turning into a total mess keeping the logs in sync

yeah i basically run exactly this setup. Log4OM for everything day to day including FT8 via WSJT-X UDP port, and then N1MM comes out of hibernation for contest weekends. the trick is i export from Log4OM to ADIF before a contest, import into N1MM so it knows what i already have confirmed, run the contest, then export N1MM's log after and merge it back into Log4OM. sounds like a pain but honestly takes maybe 10 minutes and ive only had duplicate issues like twice in two years.

the WSJT-X to Log4OM integration is solid, dupe checking works across modes in my experience, caught a few CW dupes when i was also doing FT8 on the same band during a DX weekend. one thing to watch is making sure the UDP ports arent conflicting if you ever have both programs open at the same time, learned that the hard way during a contest warmup where i had both running and wsjt-x was only talking to one of them

I switched to Log4OM about two years ago and havent really looked back for general logging. For contests I still fire up N1MM because honestly nothing touches it for that, the rate display and the bandmap during a pileup is just built different. Log4OM's contest mode exists but its not really in the same league if you're doing anything serious like a full CQWW weekend.

The WSJT-X integration I can confirm works, I've had it running that way since version 2 of Log4OM. Just set WSJT-X to log to UDP and point it at Log4OM's port, theres a setting in the Log4OM config under interfaces or something like that. Only thing i noticed is sometimes the grid square doesnt populate automatically and i have to add it manually but thats a minor thing.