so ive been using WSJT-X for FT8 stuff for a while now and it logs to its own ADIF file which i then import into Log4OM and that workflow is fine, not perfect but fine. the problem is contest season is coming up and everyone keeps telling me N1MM is basically the only real option for serious contesting and im starting to think maybe they're right

but here's my thing - i really dont want to maintain two separate logbooks. Log4OM is nice for general station logging, the interface makes sense to me, i have like 3 years of QSOs in there. if i run N1MM during a contest does anyone have a decent workflow for getting those logs back into Log4OM without a ton of duplicate headaches or messed up timestamps. the ADIF export from N1MM seems straightforward but last time i tried importing a contest log into Log4OM it kind of made a mess of the dupe checking

also side question - does WSJT-X UDP logging play nice if you have N1MM open at the same time? i sometimes run FT8 during slow periods in a contest (yeah i know, casual operator here) and i wasnt sure if theyd fight over the UDP port or something

yeah the UDP port thing will absolutely cause problems if you have both open and both trying to listen on 2333 or whatever port WSJT is set to broadcast on. N1MM can actually receive from WSJT-X but you have to configure it specifically for that and even then its a bit fiddly. I had N1MM just silently dropping the FT8 contacts for a while before i realized what was happening, checked the log at the end and had a bunch of gaps. not ideal.

for the log merging question honestly i just gave up trying to keep one master log and run N1MM strictly for contests, export the ADIF after, do a quick cleanup in a text editor to fix any weirdness, then import into Log4OM with duplicate checking turned on. it usually catches most of the overlaps. you'll get some false dupes sometimes if the timestamps are off by a few seconds but you can just manually delete those. its annoying but only happens twice a year during contest weekends so i live with it

tbh i went the other direction and just went all in on N1MM for everything including daily logging and i dont really regret it. the interface is ugly as sin and the learning curve is real but once you get used to it the telnet cluster integration and the way it handles dupe checking across bands is really solid. Log4OM is prettier for sure.

the WSJT-X thing - there's a setting in WSJT-X under reporting where you can point the UDP packets at N1MM's port instead of the default and then N1MM logs the FT8 QSOs automatically. works ok most of the time. occasionally i get wierd mode entries that dont match what N1MM expects but nothing that cant be fixed with a find and replace in the ADIF before you upload to LoTW or whatever