so ive been using Log4OM for general logging for about two years now and i really like it for day to day stuff, the cloudlog sync works great and the DX cluster integration is solid. but every time contest season rolls around i end up switching back to N1MM and it feels like i lose half my brain trying to remember where everything is again.

the thing is i tried setting up WSJT-X to feed into Log4OM during the ARRL DX contest last month and it was a mess. like the QSOs were coming in fine through the UDP broadcast but dupe checking was just not keeping up, or at least i dont think it was — maybe i had something misconfigured. ended up missing a few obvious dupes and then had to clean up the log afterward which is not fun.

N1MM handles the WSJT-X stuff fine obviously, FT8 QSOs just pop in and the dupe checking is instant, but the interface outside of contest mode feels so clunky for anything else. does anyone run Log4OM through serious contests and actually trust it or is N1MM just the answer here and i should stop fighting it

N1MM is basically the answer for contesting, i dont think theres much debate there honestly. ive tried to make other loggers work during serious contest ops and you always run into some edge case that bites you. the dupe checking speed in N1MM is just in a different league, especially when youre running a pile and cant afford to think about it.

that said the WSJT-X UDP integration in Log4OM has gotten better, i think there was a version around 2.9 or so where they fixed some latency issues with the dupe check callback. if youre on an older version that might be part of your problem. but even then for anything like the big DX contests or the sprints id just use N1MM and import the ADIF into Log4OM afterward for your permanent log. thats what i do and it takes like two minutes.

yeah the post-contest ADIF import workflow is pretty much standard for most people i think. N1MM for the contest, then dump it into whatever your main logger is after. Log4OM handles the import cleanly in my experience, havent had any field mapping issues with it.

one thing worth checking if you want to keep trying with Log4OM during contests — make sure the UDP listener port in Log4OM matches exactly what WSJT-X is broadcasting on and that nothign else on your machine is grabbing those packets first. had a weird situation where an old JTDX install i forgot about was sitting there listening on the same port and causing all kinds of weird behavior. took me embarrassingly long to figure that out