so ive been using Log4OM for general logging for about two years now and honestly i like it fine, good interface, integrates with clublog and lotw without too much fuss. but every time contest season rolls around i feel like im fighting it. the contest modules just dont feel as snappy as they should and ive had it drop a few dupes that i swear i worked before.

a buddy of mine keeps telling me to just switch everything over to N1MM for contests but then i'd be running two separate logs and trying to merge them back together after the event which sounds like its own nightmare. does anyone actually do this workflow, like Log4OM for the daily stuff and N1MM when a contest weekend comes around, and if so how are you handling the ADIF imports afterward without making a mess of your main log.

also i run WSJT-X for FT8 and FT4 and right now i have that pointed at Log4OM which works okay, the UDP logging usually works but sometimes it just silently drops a qso and i dont notice until im checking against pskreporter. wondering if N1MM handles the WSJT-X integration any better or if thats just a wsjtx thing regardless of what logger youre feeding.

yeah i do exactly this and have for a couple years. N1MM for any serious contesting, Log4OM sits as my main log the rest of the time. the merge isnt as bad as you'd think honestly. after a contest i just export the N1MM log as ADIF and import into Log4OM, and as long as you check the duplicate handling settings before you import it doesnt usually blow anything up. had one incident early on where i ended up with like 200 duplicate entries because i forgot to tick the right box but that was my fault.

the WSJT-X thing — i actually dont route wsjtx through N1MM during contests, i let it log independently and then reconcile after. N1MM and wsjtx can talk to each other but ive had weird behavior with the band map getting confused when both are running. might just be my setup but it was easier to keep them separate. for everyday ft8 stuff i do use the Log4OM udp path and yeah it drops the occasional qso, i just got in the habit of doing a quick check in wsjtx's own log file every week or so and comparing.

the dupe checking in Log4OM contest mode has always felt a bit half baked to me too, not sure if theyve improved it in the newer versions but i stopped relying on it a while back. N1MM is kind of the gold standard for contesting theres not really much debate there, the callsign entry speed and the super check partial alone make it worth using when youre in a real pile or trying to run a frequency.

one thing i'll mention on the wsjtx side — make sure you have the UDP server set to only send to one application at a time or you can get weird behavior. i think wsjtx only supports one udp listener properly and if you have both N1MM and Log4OM trying to grab the packets at the same time thats probably where your silent drops are coming from. not 100% sure thats your situation but worth checking.