Date
1 - 6 of 6
Locked Something is wrong with the decoder! Skipping badly!!! #decode
|
JP Tucson, AZ
This is getting worse!
Running v.2.6.1 on Win10. I am seeing a couple of major issues with decoding. ...and or the sequencer. First, it is NOT a timing issue! I have a GPS disciplined clock and most stations have a DT at zero or +/- .1 or .2... I am noticing more and more that stations ON the RX GREEN BRACKET simply refuse to decode! Doesn't matter what their signal strength is, but a signal is there on the waterfall, but it won't decode! I discovered this while finding bad operators transmitting on top of myself and other stations. Next, similar to above - you start a QSO, the other station responds with a decent signal but on the next cycle(s), his signal remains on the waterfall, but nothing decoded there! Or... sometimes another, weaker station will start tx over the guy you're working with an offset of 5 to 20 Hz, and blocks your QSO partner from being decoded and finishing the QSO even though his signal may be about 10dB stronger as seen on the waterfall. Now, this didn't used to be! A few years ago, I was able to complete QSOs with a station just 2 or 3 Hz off frequency from another. Or... The other guy has a good, strong signal on the first cycle, but absolutely no signal on the waterfall during the next response cycle (skipping), then picks back up on the third go around! This is going to drive everyone nuts in the June contest & Field Day events if we don't get that fixed right away, so we can test it! In all of these cases, fading is not an issue, and they have good waterfall presence. Except the skipping above. Further, you can see it happening with other stations - where both are very readable and are reporting strong signal reports to each other, and yet... either and/or both are having to resend over and over... |
|
|
|
Mike Black
Are you running a Dell computer?
toggle quoted message
Show quoted text
https://wsjtx.groups.io/g/main/topic/wsjtx_config_dell_windows/96611808?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,96611808,previd%3D9223372036854775807,nextid%3D1679580418203430588&previd=9223372036854775807&nextid=1679580418203430588 Mike W9MDB On Friday, March 24, 2023 at 02:32:31 AM CDT, JP Tucson, AZ <samcat88az@...> wrote:
This is getting worse! Running v.2.6.1 on Win10. I am seeing a couple of major issues with decoding. ...and or the sequencer. First, it is NOT a timing issue! I have a GPS disciplined clock and most stations have a DT at zero or +/- .1 or .2... I am noticing more and more that stations ON the RX GREEN BRACKET simply refuse to decode! Doesn't matter what their signal strength is, but a signal is there on the waterfall, but it won't decode! I discovered this while finding bad operators transmitting on top of myself and other stations. Next, similar to above - you start a QSO, the other station responds with a decent signal but on the next cycle(s), his signal remains on the waterfall, but nothing decoded there! Or... sometimes another, weaker station will start tx over the guy you're working with an offset of 5 to 20 Hz, and blocks your QSO partner from being decoded and finishing the QSO even though his signal may be about 10dB stronger as seen on the waterfall. Now, this didn't used to be! A few years ago, I was able to complete QSOs with a station just 2 or 3 Hz off frequency from another. Or... The other guy has a good, strong signal on the first cycle, but absolutely no signal on the waterfall during the next response cycle (skipping), then picks back up on the third go around! This is going to drive everyone nuts in the June contest & Field Day events if we don't get that fixed right away, so we can test it! In all of these cases, fading is not an issue, and they have good waterfall presence. Except the skipping above. Further, you can see it happening with other stations - where both are very readable and are reporting strong signal reports to each other, and yet... either and/or both are having to resend over and over... |
|
|
|
JP Tucson, AZ
I am...
It's a Dell E7500, ca. 2007 Win10, 1703 V2.6.1 wsjtx Mike, the only thing that's changed is the wsjtx ver. Computer & OS the same. The CPU is not running over about 45% of the time. The GPU is around 28%. Plenty of RAM avail. It seems like wsjtx needs a toolbox to record these missed cycles and other issues that appear intermittently. Though they are certainly more repetitive than before. Even if you folks built a RX only station and a monitoring system, you'd see the skipping nature between stations on even very good signals. On Fri, Mar 24, 2023, 8:08 AM Michael Black via groups.io <mdblack98= yahoo.com@groups.io> wrote: Are you running a Dell computer? |
|
|
|
Mike Black
2.6.1 takes more CPU power than previous versions.
toggle quoted message
Show quoted text
What decode level are you running? Lower the decode level and see if things get better. Mike W9MDB On Friday, March 24, 2023 at 10:36:29 AM CDT, JP Tucson, AZ <samcat88az@...> wrote:
I am... It's a Dell E7500, ca. 2007 Win10, 1703 V2.6.1 wsjtx Mike, the only thing that's changed is the wsjtx ver. Computer & OS the same. The CPU is not running over about 45% of the time. The GPU is around 28%. Plenty of RAM avail. It seems like wsjtx needs a toolbox to record these missed cycles and other issues that appear intermittently. Though they are certainly more repetitive than before. Even if you folks built a RX only station and a monitoring system, you'd see the skipping nature between stations on even very good signals. On Fri, Mar 24, 2023, 8:08 AM Michael Black via groups.io <mdblack98= yahoo.com@groups.io> wrote: Are you running a Dell computer? |
|
|
|
JP Tucson, AZ
On "normal" decode mode.
On Fri, Mar 24, 2023, 6:06 PM Michael Black via groups.io <mdblack98= yahoo.com@groups.io> wrote: 2.6.1 takes more CPU power than previous versions. |
|
|
|
David Owen
Using WSJT-X 2.6.1 with IC-R8600 radio and Dell Optiplex PC:
Hi I had a very similar problem. It turned out that another USB device (an innocent-looking weather station) on the same hub was affecting the received audio. The corrupted audio was not being detected by WSJT-X as missing samples but it would not decode anything. You could try removing other USB devices on the same USB controller and see if it makes any difference. Regards David Owen GM1OXB |
|
|