so ive been running FT8 during the slow parts of a contest and then jumping back to SSB when the band opens up, which means constantly flipping between WSJT-X and N1MM and honestly its kind of a mess. the UDP logging link works most of the time but i swear every other contest i end up with dupes in N1MM that WSJT-X already logged or the other way around. had it happen again last weekend during the state QSO party and probably cost me a few legit contacts because i wasnt sure if something had actually made it into the log or not.

im running them on the same machine, windows 10, N1MM is set to accept WSJT-X UDP broadcasts on the default port. it mostly works but there's definitely some timing thing going on where if i switch modes too fast the first few contacts dont get picked up. anyone else doing this hybrid FT8 slash phone operating during contests and figured out a reliable workflow? or is there a better way to set this up that im missing. ive seen people mention Log4OM as kind of a central logging hub but i never really looked into that deeply.

yeah the UDP timing issue is real, i ran into the exact same thing. what fixed it for me was going into WSJT-X settings and making sure the UDP server is pointed at 127.0.0.1 and the port matches exactly what N1MM has open under the WSJT-X port field in the config. obvious stuff but i had them mismatched for like three contests before i noticed. also i added a small delay before i start working new contacts after switching modes, like literally just wait 5-10 seconds and let whatever handshake is happening actually finish. not elegant but it works.

the Log4OM as hub idea is interesting but i never got it stable enough for real-time contest use. it's great for general logging but the latency when you're running a pileup is just too much for me. might be fine for slower operating though.

i dont do much contesting but i use Log4OM as my main log with WSJT-X feeding into it for FT8 and it works pretty well for casual stuff. the cloudlog integration is nice too if you care about that. but like the other guy said, for actual fast-paced contesting i think N1MM is just the right tool and trying to add another layer in the middle is asking for trouble. the dupe checking alone in N1MM during a contest is worth just committing to it fully and not trying to hybrid log across two programs. maybe just accept that the FT8 contacts go into a separate log and merge them after? some contests accept that if you document it right, though i'd double check the rules for whatever specific contest youre doing.