so ive been running Log4OM for general logging for a couple years now and honestly really like it for day to day stuff, the interface took some getting used to but the cloudlog sync and the way it handles QSL tracking is pretty solid. my issue is contest season. every time a big contest rolls around i end up fighting with it or just defaulting back to N1MM which i keep installed but barely touch outside of contests.

recently started doing more FT8 and JS8Call and now WSJT-X is in the mix too and its getting complicated. WSJT-X talks to Log4OM okay through UDP but ive had some duplicate logging weirdness where ill work a station on FT8, it logs in WSJT-X, pushes to Log4OM, and then somehow ends up doubled in the ADIF. not every time, just often enough to be annoying.

so the question is really — does anyone run all three? like N1MM for contests, WSJT-X for digital, and Log4OM as the master log? and if so how do you handle the deduplication without going crazy. or is there a cleaner workflow im missing. i feel like theres probably a better way to set this up that im just not seeing

yeah i ran basically that exact setup for about a year and the duplicate thing drove me nuts too. what eventually worked for me was just letting WSJT-X log to its own ADIF file and NOT having it push UDP to Log4OM in real time. then after a session i import the ADIF manually into Log4OM with the duplicate check set to strict — callsign, band, mode, and date all have to match before it skips it. a little more manual but i stopped getting the phantom dupes.

for N1MM during contests i just keep it totally separate and then do a one-time import into Log4OM after the contest is over. N1MM exports clean ADIF so thats never been a problem. the only thing you lose is real-time dupe checking across all your logs during a contest but honestly during a contest youre only really worried about dupes within that contest anyway so N1MM handles that internally just fine.

the three app thing sounds messy but once you get the workflow dialed in it kind of just works. just dont try to run them all piped together at the same time, something always steps on something else

I switched to just using N1MM for everything including FT8 contests like the FT Roundup and it handles WSJT-X integration pretty well for that purpose, but I'll be honest outside of contest context N1MM is kind of overkill and the general logging stuff is barebones compared to Log4OM. so i get why you'd want both.

one thing worth checking — in Log4OM there's a setting somewhere in the UDP listener config where you can set it to ignore dupes within a certain time window. I think its under settings > log integration or something like that. been a while since i dug into it but i remember there being an option that helped with exactly the double-logging issue you're describing. might be worth poking around in there before you change your whole workflow