so ive been using N1MM for probably 8 years now and honestly its great for contests, no complaints there, but outside of contest operating its kind of a pain to use as a general logger. the interface is obviously built around contest workflows and when im just sitting there doing casual ragchews or working some DX it feels like overkill and half the fields dont make sense for what im doing.

someone at the club mentioned Log4OM and i downloaded it and poked around for like an hour but couldnt really figure out how the WSJT-X integration works with it. like does it just read the ADIF log that WSJT-X writes out or is there actual live UDP logging happening? i set up the UDP stuff with N1MM and WSJT-X a while back and that works pretty seamlessly but i dont know if Log4OM handles it the same way.

also curious if anyone uses Log4OM for contests at all or if thats just not really what its for. i dont want to maintain two separate logging setups if i can help it but i also dont want to give up how well N1MM works during like a CQ WW weekend.

Log4OM does have UDP integration with WSJT-X, it works pretty well actually. you go into the settings and point WSJT-X at the Log4OM UDP port instead of the default one, or you can run them in parallel if you also want N1MM to see the spots. i ran it that way for a while where WSJT-X was broadcasting to both and Log4OM would grab the QSO data the moment WSJT-X logged it. not perfect but it worked without too much fussing around.

that said i dont think Log4OM is really a contest logger, like it has some contest features but nothing close to what N1MM does. the rate display alone in N1MM is worth keeping it around for. i ended up just keeping both installed, N1MM for any serious contest operating and Log4OM as my daily driver for everything else. they both export ADIF fine so merging logs afterward isnt terrible, just a little tedious.

yeah i cant really help with the Log4OM side of things but just wanted to say the WSJT-X and N1MM UDP setup tripped me up for a long time too. the thing that got me was WSJT-X needs to have the logged QSO destination set to both the UDP server AND the ADIF file otherwise one of them doesnt update. took me forever to figure out why N1MM wasnt seeing everything. anyway probably not what you asked but maybe relevant if youre troubleshooting the other logger too.