so ive been using N1MM for contests pretty much exclusively for the last few years and it's great for that, no complaints really, but for everyday logging it feels like overkill and honestly kind of clunky when im just working a few DX stations or doing some casual FT8 via WSJT-X. i tried setting up Log4OM a while back and it looked promising but i never fully committed to it and ended up going back to N1MM out of habit.

the thing that bugs me is the WSJT-X integration. N1MM handles it okay but i feel like im always fighting with the UDP port settings and sometimes logged contacts just dont show up right, especially during a contest when WSJT-X is also trying to log its own ADIF file and things get duplicated or out of order. anyone else deal with this? im wondering if Log4OM handles the WSJT-X side of things any cleaner or if its just a different set of headaches.

also curious if people run both at the same time somehow or just pick one and commit. feels like theres no perfect solution here and im probably missing something obvious.

yeah the UDP thing with WSJT-X and N1MM is annoying, been there. what i do for contests is just disable the WSJT-X auto-logging to its own ADIF and let N1MM handle everything through the multicast UDP setup, port 2333 if i remember right. once i stopped letting both programs try to log simultaneously it got a lot more stable. still get the occasional dupe but way less than before.

Log4OM is honestly a nicer program for day to day stuff, the QSO lookup and eQSL/LoTW integration is smoother in my opinion. but when a contest starts i switch back to N1MM without even thinking about it, theres just no real competition there for contest ops. so yeah i basically run both depending on what im doing, just not at the same time. takes about two minutes to swap over and make sure the rig control is pointed at the right program.

i had the same duplicate logging problem with wsjt-x and it drove me nuts for months. turned out i had the adif logging enabled in wsjt-x AND log4om was picking up the udp broadcasts so everything was hitting the log twice. once i figured that out it was fine but the documentation on this stuff is all over the place and you kind of have to just stumble through it.

havent really used n1mm much, only fired it up once for a club contest and found it pretty intimidating honestly. log4om feels more approachable to me but i get why serious contesters stick with n1mm, it's clearly built for that from the ground up.