Hi Mike,I wonder if they are running their receive audio level too hot? On your suggestion my receive level never exceeds 40 dB and I decode flawlessly with the exception of very weak -20 signals. The other things we found that can seriously effect decodes are AGC level and any receiver digital processing. I run my AGC at fast. You and I discovered that many moons ago using Audacity to look at the data and found it badly clipped on the leading edge with any other AGC level.73,Rory Bowers, K5CKS Sent via the Samsung Galaxy S20 FE 5G, an AT&T 5G smartphone -------- Original message --------From: Black Michael via wsjt-devel <wsjt-devel@lists.sourceforge.net> Date: 10/18/22 4:34 PM (GMT-06:00) To: WSJT Software Development <wsjt-devel@lists.sourceforge.net> Cc: Black Michael <mdblac...@yahoo.com> Subject: [wsjt-devel] Potential DXPedition Problems We were observing traffic on TY0RU and 3C3CA dxpeditions and they were both running 2.5.4 non-Fox mode and having problems where they had to repeat TX2/3/4 repeatedly with numerous QSOs. I got 3C3CA to send me some WAV files that demonstrate the problem where 3C3CA was not decoding the responding station sometimes.We're thinking there might be a problem with strong signal presence since dxpeditions will get a lot of DXCC hunters with beams and high power. So hopefully the example below helps. This one has a strong signal at 665 that WSJTX (neither 2.5.4 nor RC4) will decode. JTDX 2.2.160-rc1 does decode it at -8.3C3CA JA1IFP R-19https://www.dropbox.com/s/ve9po4y16eg6w7j/221016_205315.wav?dl=0Mike W9MDB
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel