[wsjt-devel] WSJT-X 2.2.0-rc1 - WSPRnet manual upload issue

I am using wsjtx-2.2.0-rc1-win64.exe, WINDOW 10 WSPRnet is accept manualy upload of ALL_WSPR.TXT here. http://wsprnet.org/olddb But, 2.2.0-rc1's ALL_WSPR.TXT is not allow. The reason is probably deleted the S level from ALL_WSPR.TXT. When I added S level and tried uploading, it worked well.

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Waterfall Palette

Hi Jim and Ari, Ari is correct, the only button on the Fast Graph window is the "Adjust" one which automatically becomes the default button; that in turn responds to the ENTER key. I have removed that automatic default for the next release, which should make it less likely to accidentally

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Waterfall Palette

Hi Jim, I've noticed the same thing and it happens when the focus is in the WSJT-X waterfall window and you press enter twice while thinking the focus is in some other window. 73 de Ari OH2ECG On 17.5.2020 22:14, Jim Brown wrote: > I use the ZL1FZ palette. Running FT8, the setting

[wsjt-devel] WSJT-X 2.2.0-rc1 - Waterfall Palette

I use the ZL1FZ palette. Running FT8, the setting occasionally changes to User Defined with no "trigger" that I've been able to identify as the cause. I know it's happened because the traces change to white from the multi-color ZL1FZ palette. This has happened several times in the 6 days I've

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Blank line between decoding periods

Hi Erik and Michael, the problems with the "Settings->Reporting->Start new period at top" option in WSJT-X v2.2.0 RC1 are known, and fixed for the next release. 73 Bill G4WJS. On 15/05/2020 15:33, 5p1kzx Michael wrote: Hi Erik I had the same problem the first time I marked the Blank line

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Blank line between decoding periods

Hi Erik I had the same problem the first time I marked the Blank line between decoding periods". A restart off wsjt-x solved the problem. When one have the "Start new period decodes at top" only the decoded from the last step will remain in the Band Activity Window. So every dekoder step

[wsjt-devel] WSJT-X 2.2.0-rc1 - WSPR decoding stops when multiple WSJT-X instances are running

Dear developers, Please allow me to report a situation where WSPR decoding halts when multiple WSJT-X instances are running. My setup is as follows : Two Hermes Lite II SDR's connected to a single instance of SparkSDR (yes ! my Hamlib Net rigctl is now working). Two WSJTX instances (WSJT-X and

[wsjt-devel] WSJT-X 2.2.0-rc1 - Blank line between decoding periods

Dear WSJTX developers, When ticking "Blank line between decoding periods" (and "Start new period decodes at top" is unticked), there is no separation line anymore in the Band Activity window (when decoding FT8 for example). My apologies if this is a dupe report .. Stay safe and 73's,

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Hello Bill, > Here is a little more data on this. > > Here's a screenshot showing the issue. KG8DH is transmitting in > even periods. Red arrows show where his signal is decoded but grouped with > the previous odd period. This I guess might just be an issue of the "80m" > separator not being

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works as before

If you're running an older rigctld backwards compatibility was broken and has been fixed. For now you should be able to use rigctld-wsjtx in WSJT-X which should always work together. de Mike W9MDB On Wednesday, May 13, 2020, 11:59:32 PM CDT, Saku wrote: Saku kirjoitti 14.5.2020

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

HI Paul, thanks for that clarification, we too are finding this issue hard to reproduce so be patient, we will sort it out eventually. 73 Bill G4WJS. On 14/05/2020 4:09, Paul Kube wrote: Hi Bill, Yes this is with v2.2.0-rc1, Win 10 64 bit. As I recall, it only occurred when there was just

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works as before

Black Michael via wsjt-devel kirjoitti 14.5.2020 klo 7.42: There is a bug in setting the frequency with rigctld which has been fixed and should be in the next release. Either today's hamlib snapshot or tomorrow's will also have the fix.  I'm not sure if the patch made it in to today's

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works as before

Saku kirjoitti 14.5.2020 klo 7.25: Hi! Just compiled 2.2.0-rc1 and started it. (Fedora 31, 64-bit  no prebuild package) Another test: If i set rig as icom7300, device /dev/icom7300 (that is my symlinked serial port) and serial settings ok wsjtx 2.2.0rc1 works. But if I connect to

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works as before

There is a bug in setting the frequency with rigctld which has been fixed and should be in the next release. Either today's hamlib snapshot or tomorrow's will also have the fix.  I'm not sure if the patch made it in to today's snapshot. http://n0nb.users.sourceforge.net/ de Mike W9MDB

[wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works as before

Hi! Just compiled 2.2.0-rc1 and started it. (Fedora 31, 64-bit  no prebuild package) Found out that after a short while I get error message: Rig Failure Hamlib error: Feature not available while getting current vfo. If I start wsjt-x 2.1.2 again it works ok, no Hamlib errors. 2.1.2 and

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Hi Bill, Yes this is with v2.2.0-rc1, Win 10 64 bit. As I recall, it only occurred when there was just one late decode, and no decodes in the following period. It happened several times in quick succession, but I failed to get a screenshot or any more clues; and I haven't seen it again. I

[wsjt-devel] WSJT-X 2.2.0 RC1 bug report

Hi all All this is using FT4, NA VHF - I haven't tried it in other modes. If you are in a contest mode, you can change "TEST" to be something else - I've been using HQP for the RSGB Hope QSO parties. In previous versions this "stuck" until a reload. In RC1 double clicking to reply, or hitting

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

Mike, sending VFOA after the frequency makes it work, I'll do some testing with fldigi etc and then include it in my next release. I'm not currently setup to build hamlib and wsjtx but will get that going. Thanks very much for that. 73 Alan M0NNB On Wed, May 13, 2020 at 6:51 PM Black Michael via

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

Oops...make that code this instead...still have to parse the frequency.     CHKSCN1ARG(num_sscanf(buf, "%"SCNfreq, freq)); #if 0     ret = read_string(>state.rigport, buf, BUF_MAX, "\n", 1);     if (ret <= 0)    {        return (ret < 0) ? ret : -RIG_EPROTO;    }     *vfotmp =

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

As a test try changing dummy/netrigctl.c line 622 and block out the code that expects another argument from "f". With the new code all you should need to do in spark is also provide the VFO along with the frequency.So f is now is expected to answer like this to say which VFO the frequency came

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

Hi Bill, this is how spark currently works with a connection per virtual transceiver, eliminating the need for virtual audio cables would be the next level of simple. If I were to create a Hamlib module it would probably just use the rigctl protocol which does not make much sense :), I'd prefer to

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

Hi Alan, there are already network capabilities that Hamlib back ends can access, it is not tied to serial port connections by design, reference the Flex 6xxx one for example. Using individual connections per Rx must be the way to go, then a client can open as many rig connections using the

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

Mike, thanks very much, If there is anything I can do to help/test or change in my software please let me know. I've been looking through the dump_state source and that part is a bit of a reverse engineering job:) but if that is the cause of the problem I'll dive in if it will fix it in the short

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

I'm going to see about fixing the backwards compatibility.  Hopefully today... Mike On Wednesday, May 13, 2020, 09:27:48 AM CDT, Alan Hopper wrote: Hi Bill and Michaelthanks very much for your reply. I added the response to 'q' but as expected no magic fix. The error message from 

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

Hi Bill and Michael thanks very much for your reply. I added the response to 'q' but as expected no magic fix. The error message from wsjtx is 'Hamlib error: Communicatons timed out while getting current VFO frequency'. If the protocol has not been published then it has been at least well

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

you are using rigctld for connecting to a network server, I will check with M0NNB if we can debug this offline (and put you in email copy). - Lets maybe keep in mind that this was working in release 2.1.2. 73's and thanks again, Erik ON4PB --- Message: 2 Date: Tue, 12 Ma

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

On 13/05/2020 11:43, Alan Hopper wrote: Hi Bill, I'm the developer of SparkSDR, spark does indeed pretend to be rigctld and is not the only one, QUISK also does the same thing. To my mind It makes good sense to use a published proven network protocol rather than invent yet another and then

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

cting to a network server, I will check with > M0NNB if we can debug this offline (and put you in email copy). > - Lets maybe keep in mind that this was working in release 2.1.2. > > 73's and thanks again, > Erik > ON4PB > > --- > Message: 2 > Date: Tue

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Hi Bill, 10.12 issue: Thanks for pointing me to the project web-site — John G4KLA smime.p7s Description: S/MIME cryptographic signature ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

On 13/05/2020 10:11, John Nelson via wsjt-devel wrote: Hi Bill, I can confirm that rigctld embedded in 2.2.0-rc1 works as expected. The only slight glitch is that rig numbers have changed. Whereas Kenwood TS-870s and TS-790 used to be rigs: 210 and 207 respectively, riglist has been

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

On 13/05/2020 10:06, John Nelson via wsjt-devel wrote: Hi Bill, A problem reported to me that 2.2.0-rc1 will not load on MacOS 10.12.6. I confirm that there is a problem with QtGui which was built for Mac OS X 10.13. This error is from my version of 10.12 — John G4KLA Process:

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

Hi Bill, I can confirm that rigctld embedded in 2.2.0-rc1 works as expected. The only slight glitch is that rig numbers have changed. Whereas Kenwood TS-870s and TS-790 used to be rigs: 210 and 207 respectively, riglist has been changed so that these are rigs 2010 and 2007 respectively.

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Hi Bill, A problem reported to me that 2.2.0-rc1 will not load on MacOS 10.12.6. I confirm that there is a problem with QtGui which was built for Mac OS X 10.13. This error is from my version of 10.12 — John G4KLA Process: wsjtx [42790] Path:

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

On 13/05/2020 02:01, Paul Kube wrote: On Tue, May 12, 2020 at 1:29 PM Bill Somerville > wrote:   Most users will see ... more decodes overall with the last few maybe only printing some time into the following period. On this point: When a signal is sent

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

On Tue, May 12, 2020 at 1:29 PM Bill Somerville wrote: > Most users will see ... more decodes overall with the last few maybe > only printing some time into the following period. > > On this point: When a signal is sent in a period, but decoded in the next period, I have seen the transmission

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

in mind that this was working in release 2.1.2. 73's and thanks again, Erik ON4PB --- Message: 2 Date: Tue, 12 May 2020 22:34:02 +0100 From: Bill Somerville To:wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no lon

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

02 +0100 From: Bill Somerville To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works Message-ID: <6bc371e6-9e40-e938-c597-98af91d1d...@classdesign.com> Content-Type: text/plain; charset=utf-8; format=flowed On 12/05

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

option’, disabled by default?]   73 Gary  ZL2iFB   From: Bill Somerville Sent: 13 May 2020 07:29 To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] WSJT-X 2.2.0-rc1   On 12/05/2020 20:22, Christoph Berg wrote: Re: Bill Somerville this change is deliberate. Prior versions favour

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Joe, >From a Windows 64-bit capability on JTSDK 3.1 what I am seeing is absolutely >brilliant. Your coding throws no deprecation warnings and the Fortran >components have no integer division warnings (that can always be of concern) >with the "JTSDK 3.1 experiment" patches that I have provided.

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

?] 73 Gary ZL2iFB From: Bill Somerville Sent: 13 May 2020 07:29 To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] WSJT-X 2.2.0-rc1 On 12/05/2020 20:22, Christoph Berg wrote: Re: Bill Somerville this change is deliberate. Prior versions favour strong stations calling

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Hi Ray, Thanks for your feedback. Happy to hear that v2.2.0 is working well for you! We are well aware that many WSPR users devote a rather elderly computer to a WSPR setup. Nevertheless, we don't put strict requirements on speed of the WSPR decoder; the nature of WSPR is that there's no

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Bill, Some early observations of 2.2.0-rc1 decoding: I parsed through my ALL.TXT (375+ MB) counting number of decodes per cycle. Prior to yesterday, my highest number of unique FT8 decodes in one cycle was 63. After installing 2.2.0-rc1, I monitored 14.074 for a couple of hours yesterday

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

On 12/05/2020 22:16, runninge...@gmail.com wrote: Hi, thanks one more time for all the dedicated work with yet another big step forward in decoding weal signals . ! Let me report that I am no longer able to CAT control my SparkSDR with the "Hamlib NET rigctl" network server. My settings are :

[wsjt-devel] WSJT-X 2.2.0-rc1 - Hamlib NET rigctl no longer works

Hi, thanks one more time for all the dedicated work with yet another big step forward in decoding weal signals . ! Let me report that I am no longer able to CAT control my SparkSDR with the "Hamlib NET rigctl" network server. My settings are : "localhost:5" for Network server, which should

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Excellent. Thank you. From: Bill Somerville Sent: Tuesday, May 12, 2020 4:25 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] WSJT-X 2.2.0-rc1 On 12/05/2020 20:45, j...@comcast.net <mailto:j...@comcast.net> wrote: >one feature of the latest decoder is there

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

On 12/05/2020 20:45, j...@comcast.net wrote: >one feature of the latest decoder is there to yield decodes before all transmissions are completed. Bill, Was this a user request, or just a result of the new decoding algorithm?   (My curiosity has been piqued.) Ed N4II. Hi Ed, because

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Hi Christoph, On 5/12/2020 15:22, Christoph Berg DFG7CB wrote: Well that still favors the stronger stations. Was "calling at lower offset" something people were really rushing for, or did that have any bias towards them in contests or crowded bands? Of course stronger signals are easier to

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

0 3:29 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] WSJT-X 2.2.0-rc1 On 12/05/2020 20:22, Christoph Berg wrote: Re: Bill Somerville this change is deliberate. Prior versions favour strong stations calling at the lowest audio offset, we think it is better to ran

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

On 12/05/2020 20:22, Christoph Berg wrote: Re: Bill Somerville this change is deliberate. Prior versions favour strong stations calling at the lowest audio offset, we think it is better to randomize the frequency order to give all stations more equal weighting. This is particularly in respect

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Re: Bill Somerville > this change is deliberate. Prior versions favour strong stations calling at > the lowest audio offset, we think it is better to randomize the frequency > order to give all stations more equal weighting. This is particularly in > respect of the "Call 1st" feature. There is

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

On 12/05/2020 11:56, Christoph Berg wrote: Re: Joe Taylor WSJT-X 2.2.0 will be a significant program upgrade offering many new features. The new "show most decodes earlier" feature is awesome, thanks! Probably related: I noticed that the list of decodes is now pretty much unsorted. Would it

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Re: Joe Taylor > WSJT-X 2.2.0 will be a significant program upgrade offering many new > features. The new "show most decodes earlier" feature is awesome, thanks! Probably related: I noticed that the list of decodes is now pretty much unsorted. Would it be possible to at least sort each batch by

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

On 12/05/2020 08:25, John Nelson via wsjt-devel wrote: Hi Bill, I could not duplicate the Font problem reported by Chuck WV8A. Also tested Decode Text Font and this responded as expected. When upgrading to a new version of WSJT-X I always remove WSJT-X.ini and start from fresh. MacBook

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

Hi Bill, I could not duplicate the Font problem reported by Chuck WV8A. Also tested Decode Text Font and this responded as expected. When upgrading to a new version of WSJT-X I always remove WSJT-X.ini and start from fresh. MacBook Pro: 10.14.6 Left running overnight: decoding on 20m

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Joe, thanks I found the 2.2.0 rc1 version. I'm going to work. Kind regards. ON4CKT Rudy - Oorspronkelijk bericht - Van: "Joe Taylor" Aan: "wsjt-devel" Verzonden: Maandag 11 mei 2020 16:44:33 Onderwerp: [wsjt-devel] WSJT-X 2.2.0-rc1 WSJT-X 2.2.0 will be a signifi

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

FYI I can change the displayed fonts by editing the typeface or size info in the .ini file, and can also switch to configurations that have different font settings. Getting the crash only when clicking the Font button(s) in the Preferences>General pane. Chuck WV8A > On May 11, 2020, at 5:38

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

Unable to duplicate on 10.15.5 (beta). Fonts changed as expected. George J Molnar, KF2T Arlington, Virginia, USA > On May 11, 2020, at 5:08 PM, Chuck Reti WV8A via wsjt-devel > wrote: > >  > Bill, > > Deleted Font and DecodedTextFont lines from the .ini file for my “default” > FT8

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

Bill, Deleted Font and DecodedTextFont lines from the .ini file for my “default” FT8 Config, (though noticing that every one of the configs has its own Font settings lines) Still crashing when ticking the font buttons in settings. pasted below is additional info from Terminal. Sent this

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

On 11/05/2020 20:32, Chuck Reti WV8A via wsjt-devel wrote: macOS Mojave 10.14.6 MacBook Pro 13,3 15” 2016. Installed rc1, TX,OK, RX decodes OK. Preferences>General- simply clicking either the Font or Decoded Text Font buttons causes an immediate crash. Repeated a number of times with same

[wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

macOS Mojave 10.14.6 MacBook Pro 13,3 15” 2016. Installed rc1, TX,OK, RX decodes OK. Preferences>General- simply clicking either the Font or Decoded Text Font buttons causes an immediate crash. Repeated a number of times with same result. Report attached. Chuck WV8A Process: wsjtx

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

ion. 73, Jim, W7XZ From: Black Michael via wsjt-devel Sent: Monday, May 11, 2020 10:51 To: WSJT software development Cc: Black Michael Subject: Re: [wsjt-devel] WSJT-X 2.2.0-rc1 Unless something changed failing to uninstall the old version leaves programs hanging around in the Windows uninst

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Unless something changed failing to uninstall the old version leaves programs hanging around in the Windows uninstall arena that can't be uninstalled. I also noticed that Communications is mispelled Communicaitions. de Mike W9MDB On Monday, May 11, 2020, 09:48:02 AM CDT, Joe Taylor

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Thanks Joe. You're great. 73 11.05.2020 17:44, Joe Taylor пишет: WSJT-X 2.2.0 will be a significant program upgrade offering many new features. The first candidate release... ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net

[wsjt-devel] WSJT-X 2.2.0-rc1

WSJT-X 2.2.0 will be a significant program upgrade offering many new features. The first candidate release, WSJT-X 2.2.0-rc1, is now available for download and use by beta testers. This candidate release is your first chance to test the new features and provide feedback to the WSJT

[wsjt-devel] WSJT-X 2.2.0-rc1

Hello, is it Monday OR May 10? 73, Frank OE9KFV -Ursprüngliche Nachricht- Von: Joe Taylor Gesendet: Dienstag, 5. Mai 2020 18:18 An: WSJT software development Betreff: [wsjt-devel] Coming soon: WSJT-X 2.2.0-rc1 Hi all, This message is to let you know of some important WSJT-X