so ive been using WSJT-X for most of my operating lately, mostly FT8 on 40 and 20m, and it logs fine to its own ADIF but i keep ending up with this fragmented mess where half my contacts are in the WSJT log and then if i do a contest i fire up N1MM and those go somewhere else, and then i tried Log4OM for a while because someone at the club said it handles the WSJT-X UDP feed really cleanly and does all the realtime logging automatically which honestly worked pretty well but the contest module in Log4OM never really clicked for me the way N1MM does

like for serious contesting N1MM is just hard to argue with, the bandmap integration and the way it handles dupes and multipliers is just dialed in, ive been using it for field day and a few state QSO parties and it just works the way your brain works when youre running a pileup

but for day to day stuff the UI is kind of a pain and Log4OM feels nicer to just sit and ragchew log into, so now im wondering if anyone has a workflow where theyre running Log4OM as the main shack logger and then exporting or syncing to N1MM just for contest weekends, or do you just keep them totally separate and deal with the ADIF importing afterward

also slightly unrelated but does anyone know if N1MM handles the WSJT-X UDP stream or do i have to rely on WSJT-X logging its own file and then importing - i feel like ive seen people mention N1MM can receive that UDP data but i could never get it configured right

yeah i run basically this exact setup, Log4OM as my daily driver and N1MM for contests only, and honestly just doing an ADIF import after the contest is less painful than it sounds. you export from N1MM when youre done, import into Log4OM, it dupes check against what you already have and its pretty clean. i was overthinking it for months before i just tried it and it took maybe 10 minutes the first time.

the UDP thing with N1MM and WSJT-X - i dont think N1MM listens to that feed the same way Log4OM does. N1MM is more set up to BE the logger and have WSJT-X controlled by it through the normal interface, not really the other way around. if youre doing FT8 in a contest context the N1MM + WSJT-X integration works okay but its a whole different config situation than just having Log4OM silently hoovering up the UDP packets in the background. for casual FT8 operating Log4OM wins that one hands down in my experience.

i went through this same rabbit hole last winter. ended up just keeping everything separate - WSJT-X logs to its own ADIF, N1MM for any contest i care about scoring, and then every few months i dump everything into Log4OM to have one master log. its not elegant but it works and i stopped stressing about real-time sync.

one thing i will say is that if you havent looked at the Log4OM contest module in a while they have updated it, it handles some of the smaller regional contests reasonably well now, still not touching N1MM for anything serious though. for field day especially just use N1MM, theres really no debate there.