so ive been using WSJT-X for FT8 stuff for about two years now and it logs to its own internal log which i then export to ADIF and import into Log4OM and that whole workflow is kind of a mess honestly. every time i forget to export before closing WSJT-X i end up with duplicate entries or missing contacts when i finally sync everything up.

a buddy of mine runs N1MM for all his contesting and he says just use N1MM for everything, but from what i can tell N1MM is really built around contests and the everyday logging side feels like an afterthought? like i do some contesting, mainly sweepstakes and the occasional VHF contest, but most of my operating is just ragchewing and chasing DX on 40m so i need something that handles both reasonably well without me having to juggle three different logs.

Log4OM has been pretty solid for the day to day stuff, the bandmap integration is decent and i like how it handles the award tracking for DXCC but ive heard people say it gets bloated or slow over time. mine has maybe 8000 QSOs in it now and it does seem a bit sluggish when i open the statistics page.

anyone run N1MM alongside Log4OM or do you just pick one and stick with it. and does anyone have a clean way to get WSJT-X talking to both at the same time without losing your mind

yeah the WSJT-X logging situation is annoying, what i do is set WSJT-X to log to UDP and have it send to both N1MM and Log4OM simultaneously. both programs can accept UDP log packets so you dont have to do the export/import dance at all. takes a bit of fiddling with the ports in WSJT-X settings but once its dialed in it just works. N1MM gets port 2237 by default and Log4OM has its own listener, you just point WSJT-X at both IPs if theyre on different machines or use a UDP splitter if its all one box.

as for running both longterm, i personally keep N1MM strictly for contests and Log4OM as my master log. after a contest i export the N1MM log to ADIF and import it into Log4OM, check for dupes, done. its an extra step but it means my award tracking in Log4OM stays accurate and i'm not trying to get N1MM to do things it wasnt designed for.

8000 QSOs shouldnt be making Log4OM sluggish, i've got like 35k in mine and its fine on a halfway decent machine. might be worth checking if your database needs a compact/repair, theres an option somewhere in the tools menu i think. could also be your lookup settings hitting QRZ too hard on startup.

i'll be honest i tried N1MM once for a sweepstakes and never really went back to it for everyday use, the interface just feels like it was designed by someone who only ever operates contests which i guess is kind of true. perfectly good at what it does though, during the contest itself its rock solid.