Post by Nigel VK6CPU on Dec 20, 2022 3:29:45 GMT
Currently running V2.2.160-rc2
I normally run several instances (3+) of JTDX each with its own shortcut/path ie C:\JTDX64\bin\jtdx.exe --rig-name=SUB
Each JTDX gets a different audio feed . some via VAC, others USB (Icom) or a Remote Rig using VAC
When using FT8 everything works as expected.
However, when using WSPR - WSPR spots are posted into all instances running WSPR.
IE A valid 6m spot is also spotted in the 2m instance (different radio & different audio feed).
0238 -13 0.2 50.294492 0 VK6TB OF77 40 109 ------------ Valid spot
0238 -13 0.2 144.490492 0 VK6TB OF77 40 109 ----------- invalid spot - posted to other instance of JTDX
I havent noticed this previously and for the last few years I have occaisionally been running a couple of instances of WSPR on different bands/radios.
As yet, I havent rolled back to an earlier release version.
I normally run several instances (3+) of JTDX each with its own shortcut/path ie C:\JTDX64\bin\jtdx.exe --rig-name=SUB
Each JTDX gets a different audio feed . some via VAC, others USB (Icom) or a Remote Rig using VAC
When using FT8 everything works as expected.
However, when using WSPR - WSPR spots are posted into all instances running WSPR.
IE A valid 6m spot is also spotted in the 2m instance (different radio & different audio feed).
0238 -13 0.2 50.294492 0 VK6TB OF77 40 109 ------------ Valid spot
0238 -13 0.2 144.490492 0 VK6TB OF77 40 109 ----------- invalid spot - posted to other instance of JTDX
I havent noticed this previously and for the last few years I have occaisionally been running a couple of instances of WSPR on different bands/radios.
As yet, I havent rolled back to an earlier release version.