Post by wa4mit on Jul 28, 2022 21:56:24 GMT
With the release of the last two WSJTX version they seem to caught up with JTDX ability to decode weaker signals somewhat.
and I have been using it more often. I am curious why JTDX has this tendency to drop RX segments and this seems to happen at critical times like when your going to
receive your report. It seems JTDX transmission are slightly into RX sequence time.
I had JTDX and WSJTX up at same time using WSJTX just to monitor and see what if any thing I might observe to cause these dropped cycles. What I did see is that WSJTX
starts to decode 1.5 seconds before JTDX puts anything on the screen. Would this mean JTDX would start TX cycle later? that could account for what I am seeing?.
I tried to speed up JTDX by setting everything I could find to less sensitivity and for more speed, no filters but this really did not affect the decode start or screen
print time of JTDX. I have a fairly powerful computer with AMD Ryzen 5 3600 6 core 12 thread processor and 16GB of ram I do not run any other software other than HRD for rig control and logging.
I also turned off JTAlert to see if that would help it did not.
As a long time user and support of JTDX I wonder if anyone else has observed similar. Maybe someone has a solution or idea?
Thanks 73 Morris WA4MIT
and I have been using it more often. I am curious why JTDX has this tendency to drop RX segments and this seems to happen at critical times like when your going to
receive your report. It seems JTDX transmission are slightly into RX sequence time.
I had JTDX and WSJTX up at same time using WSJTX just to monitor and see what if any thing I might observe to cause these dropped cycles. What I did see is that WSJTX
starts to decode 1.5 seconds before JTDX puts anything on the screen. Would this mean JTDX would start TX cycle later? that could account for what I am seeing?.
I tried to speed up JTDX by setting everything I could find to less sensitivity and for more speed, no filters but this really did not affect the decode start or screen
print time of JTDX. I have a fairly powerful computer with AMD Ryzen 5 3600 6 core 12 thread processor and 16GB of ram I do not run any other software other than HRD for rig control and logging.
I also turned off JTAlert to see if that would help it did not.
As a long time user and support of JTDX I wonder if anyone else has observed similar. Maybe someone has a solution or idea?
Thanks 73 Morris WA4MIT
