locked General Availability (GA) Release of WSJT-X version 2.5.0 #GeneralGroupInfo
|
From K1JT:
We are pleased to announce the General Availability (GA) release of WSJT-X version 2.5.0. New features are described in the WSJT-X User Guide here:
and also Release Notes:
On Windows platforms, WSJT-X 2.5 includes MAP65 3.0.0, a wideband polarization-matching tool intended for EME.
Links to WSJT-X 2.5.0 installation packages for Windows, Linux, and Macintosh are available here:
You can also download the packages from our SourceForge site:
It may take a short time for the SourceForge site to be updated.
WSJT-X for Windows now ships with Hamlib built as a dynamic link library (DLL). This change will allow Hamlib bug fixes to be resolved by replacing the DLL with an updated version.
|
|
|
|
Roger
On 28/09/2021 03:03, Chuck Adams wrote:
Good morning ChuckFrom K1JT:We are pleased to announce the General Availability (GA) release of WSJT-X version 2.5.0. New features are described in the WSJT-X User Guide here: This came up for moderation this morning, probably because the hashtag was not on the existing list. There's already too many hashtags and I'd spend some time yesterday removing a few which have recently crept through. I made a rapid decision to change the hashtag to #GeneralGroupInfo on the basis the rest of the subject make the topic clear. I hope you understand and this is OK with you. This hashtag has the disadvantage that it's moderator only but the advantage that subsequent discussions will be split into discreet subjects rather than a large unwieldy one. My apologies if you are not happy with my choice. Kind regards Roger GW4HZA
|
|
|
|
The 32bit version is a 404. https://physics.princeton.edu/pulsar/K1JT/wsjtx_2.5.0_i386.deb
|
|
|
|
neil_zampella <neilz@...>
Don't know where you got that URL link, as its not listed on the
main WSJT-X page. All that's there are the 64 bit versions,
which may say something about support for 32 bit on Linux. On 9/28/2021 5:28 AM, Larry Crouch
wrote:
The 32bit version is a 404. https://physics.princeton.edu/pulsar/K1JT/wsjtx_2.5.0_i386.deb
|
|
|
|
From this page which is a link in the email listing new features
https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.5.0.html#NEW_FEATURES
|
|
|
|
On 28/09/2021 11:57, Larry Crouch wrote:
From this page which is a link in the email listing new featuresHi Larry, that's a defect in the WSJT-X User Guide. We stopped providing 32-bit Intel Linux binary packages some time ago as the distributions we target no longer provide operating system updates for 32-bit distributions (Ubuntu and Fedora). You can still build a 32-bit Intel Linux version from sources as far as I know, although I no longer test that capability. 73 Bill G4WJS.
|
|
|
|
neil_zampella <neilz@...>
I suspect the User Guide is a bit ahead of the dev team's posting
compiled packages. On 9/28/2021 5:57 AM, Larry Crouch
wrote:
>From this page which is a link in the email listing new features
|
|
|
|
Paul Turner
2.5.0 installed smoothly and easily – as ever. Thanks to all the developers.
73, Paul G4IJE.
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Chuck Adams
Sent: 28 September 2021 03:03 To: main@WSJTX.groups.io Subject: [WSJTX] General Availability (GA) Release of WSJT-X version 2.5.0 #GeneralGroupInfo
From K1JT: We are pleased to announce the General Availability (GA) release of WSJT-X version 2.5.0. New features are described in the WSJT-X User Guide here: and also Release Notes: On Windows platforms, WSJT-X 2.5 includes MAP65 3.0.0, a wideband polarization-matching tool intended for EME. Links to WSJT-X 2.5.0 installation packages for Windows, Linux, and Macintosh are available here: You can also download the packages from our SourceForge site: It may take a short time for the SourceForge site to be updated. WSJT-X for Windows now ships with Hamlib built as a dynamic link library (DLL). This change will allow Hamlib bug fixes to be resolved by replacing the DLL with an updated version.
|
|
|
|
Geoff G4FKA
Same here, v2.5.0 downloaded and installed perfectly. One thing I do notice is that there seem to be a much wider range of received signal strengths, with quite a few lower than they might have been with previous releases. Maybe WSJT-X, maybe recent Windows updates altering the CODEC settings. No problems operating, just rather disconcerting when I sent -01 to an N4 earlier and got +30 back!
|
|
|
|
Joe Dz
I noticed a similar thing on the evening of 10/02 on 10m FT8. There was a good opening from W1 land to LU and PY land, and I was getting -15 to +05 and I was giving out +20 and most around +10. Interesting. Joe, K1YOW
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io]
On Behalf Of Geoff,G4FKA via
groups.io
Same here, v2.5.0 downloaded and installed perfectly. One thing I do notice is that there seem to be a much wider range of received signal strengths, with quite a few lower than they might have been with previous releases. Maybe WSJT-X, maybe recent Windows updates altering the CODEC settings. No problems operating, just rather disconcerting when I sent -01 to an N4 earlier and got +30 back!
|
|
|
|
I don’t feel so bad…. I have been giving +10 to +20 but receiving -15 to -20 dB. Bill WB6JJJ
On Oct 2, 2021, at 9:09 AM, Joe Dz <joedzekevich@...> wrote:
|
|
|
|
Hi Bill,
excessively optimistic signal reports
are often due to restricted receiver bandwidth. The FT8 decoder
relies on a reasonably flat receiver bandwidth across the
displayed waterfall, and at least 2500 Hz wide. Narrower input
data bandwidth will cause underestimation of the noise level.
73
Bill G4WJS. On 02/10/2021 19:24, Bill, WB6JJJ
wrote:
|
|
|
|
Hmmm, my IC-7610 states more than 3500 Hz and does receive that entire bandwidth. I have never restricted the width. There are times that I receive similar TX and RX reports but they are rare. Maybe my location is extra quiet? I doubt it… Bill WB6JJJ
On Oct 2, 2021, at 11:29 AM, Bill Somerville <g4wjs@...> wrote:
|
|
|
|
Jim Brown
On 10/2/2021 1:23 PM, Bill, WB6JJJ wrote:
Maybe my location is extra quiet?Hi Bill, Signal reports in FT8 are signal to noise ratio, the differences you're seeing are usually the result of high noise levels on the other end. Another reason would be if the other station is using JTDX -- the current beta, which I'm using because it decodes some weak signals that WSJT-X misses (at least before the new 2.50 general release), is brain dead with respect to signal reports, giving very low ones. 73, Jim K9YC
|
|
|
