so ive been running N1MM for contests for probably 4 or 5 years now and honestly its fine, does what it needs to do, but ive been messing around with Log4OM for general shack logging and i actually really like it for day to day stuff — the QSL management and the way it handles LoTW sync is way cleaner than anything ive tried before

my problem is WSJT-X integration. right now i have WSJT-X talking to Log4OM no problem for FT8 and FT4 and that all works, but when i fire up N1MM for a contest weekend the whole UDP port situation turns into a mess. i think i had it set up at some point where both were kinda-sorta getting the log data but i honestly dont remember what i did and now its just not working right

so the question is — does anyone actually run both N1MM and Log4OM simultaneously and have WSJT-X piping into both or do you just pick one and deal with it during contest weekends. also wondering if anyone has fully switched to Log4OM for contesting or if thats kind of a dead end, i know it has contest modes but i've heard mixed things

yeah the UDP thing is the classic headache with this setup. WSJT-X can only send to one UDP port at a time natively but theres a workaround using a UDP repeater/forwarder utility — i forget the exact name, there's a few floating around but one called WSJT-X Log Fwd or something similar, basically it listens on the WSJT-X port and rebroadcasts to multiple destinations. that way both N1MM and Log4OM can each get their own copy of the data

i ran something like this during last years ARRL DX CW and it mostly worked although i had one instance where N1MM missed a couple QSOs and i had to manually reconcile after. wasnt a huge deal but annoying. for serious contest operating id probably still just kill Log4OM entirely and run N1MM standalone, then import the ADIF into Log4OM after the contest wraps up. way less moving parts to go wrong on a Saturday night when youre tired and trying to run a pileup

i tried Log4OM for contesting for about three weekends and gave up honestly. its a solid program and the interface is nicer looking than N1MM thats for sure, but N1MM is just so dialed in for contest operating that switching felt like trying to drive with the wrong hand. the function key macros, the way it handles dupes, S&P vs run mode switching — its all muscle memory at this point and Log4OM just doesnt feel the same even after you get it configured

keep Log4OM for your everyday logging and DX chasing, thats where it shines. just export from N1MM after each contest and import it over, takes maybe five minutes and then your master log stays clean in Log4OM. thats what i do anyway