so ive been using N1MM for a while now mostly because thats what everyone told me to use when i started doing contests, and honestly for contests its great, no complaints there. but outside of contest season im finding it a bit clunky for just day to day logging, like if i work a DX station on 17m and want to add some notes or track a DXCC entity it feels like more work than it should be.

been looking at Log4OM and it seems way more geared toward general station logging with the award tracking and all that. my question is really about WSJT-X integration because i run FT8 probably 4 or 5 nights a week and i dont want to be juggling two logs or having dupes showing up everywhere. does Log4OM handle the WSJT-X UDP feed as cleanly as N1MM does, or is there still weirdness with it. read some stuff online but half of it seems to be from like 2019 and im not sure how much has changed since then.

also wondering if anyone just runs both and keeps them synced somehow, seems like a nightmare but maybe im overthinking it

Log4OM v2 actually handles the WSJT-X integration pretty well these days, way better than it used to be. you set up the UDP port in WSJT-X to point at Log4OM and it picks up the logged contacts automatically, decodes come in, award tracking updates, all of it. i switched from N1MM as my main logger about a year and a half ago and havent looked back for general operating.

that said i still fire up N1MM when a big contest weekend comes around because honestly nothing touches it for that, the bandmap and the rate meter and all the contest specific stuff is just in another league. what i do is run both but only one at a time, and after a contest i export the ADIF from N1MM and import it into Log4OM. little annoying but it takes maybe five minutes and then everything is in one place. the DXCC tracking in Log4OM is genuinely really good once you get your existing log imported and confirmed statuses sorted out.

the one thing id warn you about is the initial setup of Log4OM can feel overwhelming, theres a lot of config screens and if you poke around in the wrong order you can end up with duplicate lookups or the cluster feed going weird. just take it slow and follow the wiki for the WSJT-X setup specifically

ran into this exact thing last winter. ended up just keeping N1MM as my contest logger and Log4OM for everything else, the import after the contest is mildly annoying but its not that bad. the UDP stuff with WSJT-X and Log4OM works fine for me on windows 10, just had to make sure the port wasnt being blocked and that i wasnt accidentally still pointing WSJT-X at N1MM from a contest the weekend before lol. caught that one after wondering why nothing was logging for like 20 minutes