so ive been running Log4OM for a while now and honestly i like it for day to day stuff, the QSO entry is clean and it syncs with LoTW without too much fussing around. but every time a contest rolls around i feel like im fighting it, the contest modules just dont feel right to me compared to what i hear people saying about N1MM.

the thing is i dont really want to run two separate logging programs if i can help it. ive got everything set up in Log4OM, my ADIF history going back a few years, all my awards tracking. switching feels like a headache. but i tried N1MM during the last CQ WW and i have to admit the logging speed is just on another level, especially with SO2R stuff and the bandmap integration. its just built for contesting in a way that Log4OM isnt, at least from what i can tell.

anyone actually use both regularly? like Log4OM for normal hamming and N1MM just when a contest starts? or is there a better workflow. also how are people handling WSJT-X with this — right now i have WSJT-X logging directly to Log4OM via UDP and it mostly works but i get occasional duplicate entries that are annoying to clean up.

yeah that's pretty much exactly what i do — N1MM for contests, Log4OM for everything else. its a bit clunky to keep two programs installed but honestly once you get used to it the workflow isnt bad. after a contest i just export the Cabrillo and the ADIF from N1MM and import the ADIF into Log4OM to keep the master log updated. takes maybe five minutes.

the WSJT-X duplicate thing is a known annoyance. i think what happens is if WSJT-X logs the QSO and then you also manually confirm something in Log4OM you get two entries. i turned off the auto-log in WSJT-X and just let Log4OM handle it through the UDP port, that cut down on most of the dupes. not perfect but better.

N1MM is kind of the gold standard for HF contesting, i dont think anyones really gonna argue that. the SO2R support and the way it handles dupe checking on the fly is hard to beat. that said i tried using it for regular logging once and it felt weirdly overkill, like driving a racecar to the grocery store.

for the WSJT-X stuff — are you running the UDP logging on port 2333 or whatever the default is? i had dupes too and it turned out i had both the WSJT-X built-in logging AND the UDP path both active at the same time which obviously caused chaos. check your WSJT-X settings under the Reporting tab and make sure youre not doubling up the log paths. once i sorted that out it was clean.