so ive been running Log4OM for general shack logging for maybe two years now and honestly i like it a lot, the QSO management and the clublog integration works pretty well for me. but every time contest season rolls around i end up installing N1MM on a separate machine because thats just what everyone else seems to be running for things like SS or CQWW and i want to make sure the exchange stuff is working right without having to be the weird guy on the network who cant sync rates properly.

anyway the thing thats starting to annoy me is that i also run WSJT-X pretty regularly, mostly FT8 on 40 and sometimes 60 when the band is doing something interesting, and getting WSJT-X to play nice with Log4OM over UDP is mostly fine but i feel like ive got three different programs doing three different jobs and none of them talk to each other as cleanly as id like. like the dupe checking across both logs is kind of a mess when i switch modes.

does anyone actually use N1MM as their daily logger too or is it really just a contest thing in your shack. im wondering if theres a cleaner way to handle this or if everyone just kind of accepts the multi-software situation

yeah N1MM is really a contest tool first and everything else is kind of an afterthought. i tried using it for general logging a few years back and the everyday QSO stuff just felt clunky, like its not designed for that workflow at all. for WSJT-X i just let WSJT-X log to its own adif and then import into Log4OM at the end of each session, its not perfect but it works and the dupe thing doesnt bother me that much since i mostly know what ive worked anyway.

the UDP logging from WSJT-X direct to Log4OM should work though, i had it set up that way for a while. think i had port 2237 or whatever the default is and it was logging in near realtime. had one issue where Log4OM wasnt catching every QSO if i was clicking through them fast on a busy FT8 pileup but it got most of them. probably a timing thing.

I run N1MM for every contest and nothing else, and Log4OM handles everything in between. Honestly I've just accepted it's a two-program shack and the ADIF export at the end of a contest weekend into Log4OM takes like two minutes so it doesn't bother me. The dupe checking cross-program thing is a real issue during like a casual operating period right before or after a contest but that's pretty edge case for me.

One thing that helped was setting up a master ADIF in Log4OM and doing a fresh import before any big contest so N1MM at least has a reasonably current worked-before database. Not seamless but it cuts down on the confusion. WSJT-X UDP to Log4OM has been rock solid for me for the past year or so, I think they fixed some of the timing stuff in a recent Log4OM update but dont quote me on that.