[wsjt-devel] Version 2.7.0-rc1

Have had running now for a while, despite operator errors seems good, BUT :), When I choose CQ: NONE, there is no effect, still first/strongest stn fires up qso... Fedora 38, rigctl Hamlib 4.6~git touko 13 15:49:08Z 2023 SHA=99baa8 64-bit, Kenwood TS-890S. Jarmo, oh1mrr

Re: [wsjt-devel] Version 2.5.4 crashing on FreeBSD.

So if it helps to shed any light, right after I performed the OS upgrade and before reinstalling all my ports I got back into the system and started up X and ran a few things to see if everything was good to proceed I did try wsjtx as well and to my surprise it worked fine and didn't crash between

Re: [wsjt-devel] Version 2.5.4 crashing on FreeBSD.

Sorry let me be a bit more specific: The message field size that the runtime is complaining about has a length of 22. The message passed in has a size of -4294967274. -4294967274 is 0x0016 in hexadecimal. And if you ignore the top part of that 64 bit value, you get 0x16 which in de

Re: [wsjt-devel] Version 2.5.4 crashing on FreeBSD.

Yes that is helpful- I ran into this same problem but I don’t remember exactly what I did to solve it and my source code is not showing a diff in that file. I believe what I had to do was to make sure that the caller to that routine was passing the right length string. However the “-42949672

Re: [wsjt-devel] Version 2.5.4 crashing on FreeBSD.

is this what you were refering to? At line 1 of file /usr/ports/comms/wsjtx/work/.build/wsjtx-prefix/src/wsjtx/lib/gen65.f90 Fortran runtime error: Actual string length is shorter than the declared one for dummy argument 'msgsent' (-4294967274/22) Thanks again On 4/11/22 17:28, Jason Selwitz

Re: [wsjt-devel] Version 2.5.4 crashing on FreeBSD.

Hi Alex, Yes this is the exact same issue nothing has changed.. And I would be happy to provide the backtrace, is there a particular way you need it generated, sorry I don't do it much. Thanks again for the assistance. Jason On 4/11/22 17:09, Alex Lelievre wrote: Hi Jason, Can you provide

Re: [wsjt-devel] Version 2.5.4 crashing on FreeBSD.

Hi Jason, Can you provide a backtrace from the crash you are seeing? Is this the same problem you reported back in January with a Fortran runtime error? alex K6LOT > On Apr 11, 2022, at 1:41 PM, Jason Selwitz via wsjt-devel > wrote: > > Just following up again on this issue, I went ahead and

Re: [wsjt-devel] Version 2.5.4 crashing on FreeBSD.

Just following up again on this issue, I went ahead and finally upgraded to 13.0 and reinstalled all my ports yet the crash still persists with the same error, I have tried recompiling with both GCC 10 and 8 to see if it would make a difference and no appreciable improvements have resulted .. I

Re: [wsjt-devel] Version 2.5.2 crashing on FreeBSD.

Awesome, thanks again for the tips Jeff, I went ahead and de-installed WSJT-X updated my ports tree and rebuilt it on my current 12 install, it does build fine and runs ok, even lets me click on a few station calls to initiate contact then maybe the third or fourth try I seem to always end up

Re: [wsjt-devel] Version 2.5.2 crashing on FreeBSD.

One of the beautiful things about FreeBSD is building out of the ports collection.  Everything is built from source, so it should not matter if you are on 11, 12 or 13.  I would encourage an update to 13 if you have a non-production machine, simply because that is where people seem to be doing

Re: [wsjt-devel] Version 2.5.2 crashing on FreeBSD.

Thanks Jeff. I'm running 12.X currently but 2.5.4 seems to build fine for me at least I could try to re-run the build and watch for any warnings or errors.. is it a matter of needing to jump to the 13.X version train? or should it still work under 12.X? Thanks again Jason On 1/7/22 09:50

Re: [wsjt-devel] Version 2.5.2 crashing on FreeBSD.

That has been fixed and WSJT-X 2.5.4 builds out of the ports collection on FreeBSD 13. portsnap fetch update make install clean WSJT-X 2.5.4 builds and installs without error. Oh, and thanks for the reminder to send Diane the request to add the binary to the package collection. On 1/6/2

Re: [wsjt-devel] Version 2.5.2 crashing on FreeBSD.

Hi Jason, I believe that the WSJT-X team said they were going to look at issues like this as part of a larger clean-up to deal with ever-stricter fortran compilers. You might need to wait until the next release for this to be fixed. alex K6LOT > On Jan 6, 2022, at 5:16 PM, Jason Selwitz via wsj

Re: [wsjt-devel] Version 2.5.2 crashing on FreeBSD.

OK so after jumping through hoops to get the FreeBSD ports system to take a modified version of the WSJT-X source I was able to try to edit the line.. character*22 msgsent to.. character(len=*) :: msgsent and tried to recompile, the program seems to have built fine but then when you start i

Re: [wsjt-devel] Version 2.5.2 crashing on FreeBSD.

Thanks Alex! I tool a look at where it was failing and it appears to be coming from .. /usr/ports/comms/wsjtx/work/.build/wsjtx-prefix/src/wsjtx/lib/gen65.f90 which looks like it contains the following.. Line 1: subroutine gen65(msg0,ichk,msgsent,itone,itype) I did find something similar to w

Re: [wsjt-devel] Version 2.5.2 crashing on FreeBSD.

Hi Jason, I’ve seen this error with the Apple M1 port. It’s because the version of the fortran compiler you are using is newer and treats this as an error instead of a warning like the older fortran compiler. I’m not sure what the recommended version is for WSJT-X but for Intel Macs it was 6.

[wsjt-devel] Version 2.5.2 crashing on FreeBSD.

  Hi there, I was wondering if anyone had seen the following error it usually happens when I try to double click on another callsign to start attempting to make a contact Ive tried removing and rebuilding the configuration and tried changing a few settings in the software to try to find a wor

Re: [wsjt-devel] Version 2.5 not linking to my IC-7800

On 30/09/2021 23:14, Fred Hurd via wsjt-devel wrote: I just updated my WSJT-X SW to version 2.5 but I can no longer communicate with my IC-7800 radio. Has something changed in the SW radio setup settings? Fred W4PKU Hi Fred, I assume you are getting an error message, what does that say, incl

[wsjt-devel] Version 2.5 not linking to my IC-7800

I just updated my WSJT-X SW to version 2.5 but I can no longer communicate with my IC-7800 radio. Has something changed in the SW radio setup settings? Fred W4PKU Sent from my iPad ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://

Re: [wsjt-devel] Version rc6 - Logging from JTALERT to QRZ.COM stopped working.

Hi Mike, the information you provided is not clear to me. Your attached document above mentions that the JTAlert pop up is prior to logging the contact in whichever logging program JTAlert is directed to convey log entries to. That is a misunderstanding on your part, the pop up message is post

Re: [wsjt-devel] Version rc6 - Logging from JTALERT to QRZ.COM stopped working.

Here's the setting that was used in rc6. [image: image.png] On Fri, Sep 10, 2021 at 2:43 PM Bill Somerville via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > On 10/09/2021 15:31, Michael Lizzio via wsjt-devel wrote: > > Logging from JTALERT to QRZ.COM stopped working with rc6. Return t

Re: [wsjt-devel] Version rc6 - Logging from JTALERT to QRZ.COM stopped working.

Did you see the attachment? When rc6 was used, I hit OK in the confirmation window and the contact was not logged. Thanks Mike WA2TOP On Fri, Sep 10, 2021 at 9:43 AM Bill Somerville via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > On 10/09/2021 15:31, Michael Lizzio via wsjt-devel

Re: [wsjt-devel] Version rc6 - Logging from JTALERT to QRZ.COM stopped working.

On 10/09/2021 15:31, Michael Lizzio via wsjt-devel wrote: Logging from JTALERT to QRZ.COM stopped working with rc6. Return to rc5 resolved issue. * Updated to RC6 this evening. * Using JTALERT to log contacts to QRZ.com * Logging to QRZ.Com stopped working. * Rebooted t

Re: [wsjt-devel] Version 2.4.0-rc1

Yes, Neil, it's still a problem. It was there before RC1 and is still there. I have multiple configs and changing fonts/resetting, etc...does not solve the problem No biggie, but eventually it should be fixed 73, N0AN Hasan On Sun, Feb 7, 2021 at 2:12 PM Neil Zampella wrote: > Did you reset the

Re: [wsjt-devel] Version 2.4.0-rc1

Did you reset the frequency list when you installed the RC? Neil, KN3ILZ On 2/7/2021 1:56 PM, Harry E. Hoffman wrote: I found an issues with the band pull down menu in V2.4.0-rc1. The list will have the frequencies truncated. This stared happening intermittently one moment it would be OK, I w

Re: [wsjt-devel] Version

Hunger [mailto:fhun...@onlinehome.de] Sent: 7. helmikuuta 2021 10:11 To: WSJT software development Subject: [wsjt-devel] Version Hi, I downloaded the new versions 2.3.0 and 2.4.0 rc1. Is it possible, that users of version 2.2.2 and 2.3.0 can’t work together as users with the same version. I have

[wsjt-devel] Version

Hi, I downloaded the new versions 2.3.0 and 2.4.0 rc1. Is it possible, that users of version 2.2.2 and 2.3.0 can’t work together as users with the same version. I have tested with version 2.3.0 - only few QSO’s and back to version 2.2.2 more QSO’s. Thank you for help. 73 de Frank DM5KK ___

Re: [wsjt-devel] Version 2.3.0 and Fedora 32

Sat, 6 Feb 2021 08:11:24 +0200 Saku kirjoitti: > Yep! > > I have also boost-1.69.0-18.fc32.x86_64. Builds fine, but I think > Jarmo means package install. Yes Allways read also the last message in the chain :) Jarmo ___ wsjt-devel mailing list wsjt

Re: [wsjt-devel] Version 2.3.0 and Fedora 32

Yep! I have also boost-1.69.0-18.fc32.x86_64. Builds fine, but I think Jarmo means package install. Jeff Stillinger via wsjt-devel kirjoitti 6.2.2021 klo 4.12: Using Boost 1.66 on SuSE Enterprise.   Works just fine, builds without error. On 2/5/21 5:36 AM, jarmo wrote: Has anyone managed i

Re: [wsjt-devel] Version 2.3.0 and Fedora 32

Using Boost 1.66 on SuSE Enterprise.   Works just fine, builds without error. On 2/5/21 5:36 AM, jarmo wrote: Has anyone managed install version 2.3.0 into F32? 2.3.0 has depencies to BOOST 1.73 and in F32 there is BOOST 1.69. So anyone solved this? Jarmo, oh1mrr

Re: [wsjt-devel] version 2.3.0 x64 GA strange country display

...@fastwebnet.it] *Sent:* 5. helmikuuta 2021 19:51 *To:* wsjt-devel@lists.sourceforge.net *Subject:* Re: [wsjt-devel] version 2.3.0 x64 GA strange country display This is showed when the app displays the second decode try. It is not always but random. Il 05/02/2021 18:46, Maurizio Brameri ha scritto

Re: [wsjt-devel] version 2.3.0 x64 GA strange country display

https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.3.0_en.html#_ap_decoding 73, -Jim NU0C On Fri, 5 Feb 2021 18:58:46 +0100 Maurizio Brameri wrote: > Hi, > > after some more investigation, I noted that it happens always when a > station is calling CQ and it is decoded as last

Re: [wsjt-devel] version 2.3.0 x64 GA strange country display

Hi Maurizio See User Guide section 12.2. Location of this AP info seems to be in a new position. 73, Reino OH3mA From: Maurizio Brameri [mailto:maurizio.bram...@fastwebnet.it] Sent: 5. helmikuuta 2021 19:51 To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] version 2.3.0 x64 GA

Re: [wsjt-devel] version 2.3.0 x64 GA strange country display

Hi, after some more investigation, I noted that it happens always when a station is calling CQ and it is decoded as last station at last decode try. In my configuration the decode button is lighting 3 times. I hope I can explain clearly wht is happening. 73, Maurizio I2NOY Il 05/02/2021

Re: [wsjt-devel] version 2.3.0 x64 GA strange country display

This is showed when the app displays the second decode try. It is not always but random. Il 05/02/2021 18:46, Maurizio Brameri ha scritto: Hi, this evening I noted that sometimes an "al" is anteposed to country name. Please see pasted image: Is seems it happens on last station received. I

[wsjt-devel] version 2.3.0 x64 GA strange country display

Hi, this evening I noted that sometimes an "al" is anteposed to country name. Please see pasted image: Is seems it happens on last station received. Is it a bug or it indicates something? 73, Maurizio I2NOY ___ wsjt-devel mailing list wsjt-dev

Re: [wsjt-devel] Version 2.3.0 and Fedora 32

Fri, 5 Feb 2021 14:24:27 + g3vnc kirjoitti: > On Linux Mint 19.3 I did $ sudo apt install libboost-all-dev as per > the 2.3.0 User Guide and built 2.3.0 from source with no issues. > > The libboost-all-dev version that was installed from the repo is > 1.65.1.0ubuntu1. > > Am I missing som

Re: [wsjt-devel] Version 2.3.0 and Fedora 32

On 05/02/2021 11:36, jarmo wrote: Has anyone managed install version 2.3.0 into F32? 2.3.0 has depencies to BOOST 1.73 and in F32 there is BOOST 1.69. So anyone solved this? Jarmo, oh1mrr On Linux Mint 19.3 I did $ sudo apt install libboost-all-dev as per the 2.3.0 User Guide and built 2.3.0

Re: [wsjt-devel] Version 2.3.0 and Fedora 32

Fri, 5 Feb 2021 07:19:40 -0600 Richard Shaw kirjoitti: > https://koji.fedoraproject.org/koji/taskinfo?taskID=61383470 > > Thanks, > Richard > KF5OIM Tnx Richard Jarmo ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourc

Re: [wsjt-devel] Version 2.3.0 and Fedora 32

On Fri, Feb 5, 2021 at 5:43 AM jarmo wrote: > Has anyone managed install version 2.3.0 into F32? > 2.3.0 has depencies to BOOST 1.73 and in F32 > there is BOOST 1.69. > So anyone solved this? > I just kicked off the official Fedora build. I was working on the hamlib 4.1 release earlier. https:/

[wsjt-devel] Version 2.3.0 and Fedora 32

Has anyone managed install version 2.3.0 into F32? 2.3.0 has depencies to BOOST 1.73 and in F32 there is BOOST 1.69. So anyone solved this? Jarmo, oh1mrr ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/l

Re: [wsjt-devel] Version 2.2.0-rc1 is not running

On 13/05/2020 23:02, Jesús Gutiérrez Rodríguez wrote: I have downloaded and updated the new version of WSJT-X 2.2.0-rc1, but note that it does not open the program. I have created a new directory on an external disk and I still cannot run the program nor show any possible error windows. I have

[wsjt-devel] Version 2.2.0-rc1 is not running

I have downloaded and updated the new version of WSJT-X 2.2.0-rc1, but note that it does not open the program. I have created a new directory on an external disk and I still cannot run the program nor show any possible error windows. I have gone back to the previous version, 2.1.2 and it works corr

[wsjt-devel] version as seen by pskreporter

Hi Bill & all, While pointing my mouse to my own station on the pskreporter window, I observe that the "Using:" has the "-dirty" suffix. Please explain me why and explain us how the version string is build. Thanks ! Best wishes, Claude (DJ0OT) __

Re: [wsjt-devel] Version 1 to Version 2 Conversion Paper

Hi Bill, Thanks for sharing your draft: an interesting analysis of the changeover to the "v2.0" message formats for FT8. Here are a few more comments, in addition to the ones already posted here by Bill Somerville, G4WJS. 1. We published a schedule, three months in advance, specifying target

Re: [wsjt-devel] Version 1 to Version 2 Conversion Paper

On 16/01/2019 00:04, Bill Frantz wrote: I have written a short paper about the conversion from from release 1 to release of the FT8 protocol and invite people to review the initial draft. It is mainly oriented toward software engineers.

[wsjt-devel] Version 1 to Version 2 Conversion Paper

I have written a short paper about the conversion from from release 1 to release of the FT8 protocol and invite people to review the initial draft. It is mainly oriented toward software engineers. Flag Day with FT8 Bill Fran

Re: [wsjt-devel] Version 2.0 issues with JT65

reported this before, but when the bogus decodes (while averaging) show up, there is nothing at all shown in the averaging window (F7). Thanks for your help. 73, Russ K2TXB -Original Message- From: Joe Taylor Sent: Saturday, December 15, 2018 1:31 PM To: WSJT software development Subje

Re: [wsjt-devel] Version 2.0 issues with JT65

ny kind is received by the logging program, so it is not just a case of a different format. Thanks for any help. 73, Russ K2TXB > -Original Message- > From: Joe Taylor > Sent: Saturday, December 15, 2018 1:31 PM > To: WSJT software development > Subject: Re: [wsjt-devel] Ver

Re: [wsjt-devel] Version 2.0 issues with JT65

en the bogus decodes (while averaging) show up, there is nothing at all shown in the averaging window (F7). Thanks for your help. 73, Russ K2TXB > -Original Message- > From: Joe Taylor > Sent: Saturday, December 15, 2018 1:31 PM > To: WSJT software development > Subject:

Re: [wsjt-devel] Version 2.0 issues with JT65

Russ -- You're calling some displays "bogus decodes", and evidently they are bogus. But you appear to have all the knobs turned up to maximum aggressiveness. Most if the displayed messages are flagged with "?", which you may interpret as "caveat emptor", or some such. Probably you saved "K

Re: [wsjt-devel] Version 2.0 issues with JT65

Hi Joe Russ's report noted the reappearance of a callsign that had previously been decoded ( probably recently) which was then seen as the content average decode *even after the program was closed and restarted*, and clear average pressed. I was therefore wondering whether the decoder was using a

Re: [wsjt-devel] Version 2.0 issues with JT65

Bill, Joe, Charlie, whoever is interested; here is a new wrinkle to the problem. I was operating MSK144 on 2 meters. Got done and decided to switch to JT65 to see if the false decodes would start to happen. It didn't right away, so went away for a while leaving it running. When I got back I had

Re: [wsjt-devel] Version 2.0 issues with JT65

Hi Charlie, On 12/15/2018 12:38, G3WDG wrote: If deep search is engaged, does it look through call3.txt randomly, or start for example at the most recent entry? Deep Search uses whatever is saved in CALL3.TXT. There's nothing 'random' about it, and order in the file does not matter. If you

Re: [wsjt-devel] Version 2.0 issues with JT65

Bill If deep search is engaged, does it look through call3.txt randomly, or start for example at the most recent entry? Charlie > Hi Russ, > > some comments in line. BTW I don't operate EME so these are based on > looking at the source code alone. > > On 15/12/2018 00:33, Russ wrote: >> I'm havi

Re: [wsjt-devel] Version 2.0 issues with JT65

Bill, here is the matching portion from the all.txt file: 2118 -26 2.5 1391 #* W4TAA AA4FF EM50 f 2119 -23 2.9 1453 #* CQ W4TAA EL87 f 181214_212000 Transmitting 144.12 MHz JT65: W4TAA K2TXB FN20 2119 -23 2.9 1453 #* CQ W4TAA EL87

Re: [wsjt-devel] Version 2.0 issues with JT65

Hi Russ, some comments in line. BTW I don't operate EME so these are based on looking at the source code alone. On 15/12/2018 00:33, Russ wrote: I'm having a lot of problems using JT65 for EME. The right hand pane, Average Decodes, seems to have a mind of it's own. For instance, earlier I w

[wsjt-devel] Version 2.0 issues with JT65

I'm having a lot of problems using JT65 for EME. The right hand pane, Average Decodes, seems to have a mind of it's own. For instance, earlier I was trying to work N5TM and I did copy two of his sequences. Now, an hour later I am just sitting here watching the screen and suddenly in the average

Re: [wsjt-devel] Version 2.0 rc5

On 25/11/2018 02:50, David Fisher wrote: This raises the interesting question: Do you expect to create a 2.0.1 version after the dust settles and small number of bugs appear that need swatting?  This would be bug fixes only, not new features.  Just wondering about your point of view on this.

Re: [wsjt-devel] Version 2.0 rc5

From: Ed Muns Sent: Saturday, November 24, 2018 6:34:32 PM To: 'WSJT software development' Subject: Re: [wsjt-devel] Version 2.0 rc5 Disappointed, but understand, Bill. Thanks for the quick reply (and, all the great effort on these releases!). Ed W0YK -Original Message

Re: [wsjt-devel] Version 2.0 rc5

Disappointed, but understand, Bill. Thanks for the quick reply (and, all the great effort on these releases!). Ed W0YK -Original Message- From: Bill Somerville [mailto:g4...@classdesign.com] Sent: 24 November, 2018 18:22 To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel

Re: [wsjt-devel] Version 2.0 rc5

On 25/11/2018 02:12, Ed Muns wrote: Will rc5 restore the "nextcall" contesting feature? Ed W0YK Hi Ed, no it will not, sorry about that. The first attempt at implementation proved to be quite buggy and we feel that it is too near GA date to implement the scale of changes required to make it

Re: [wsjt-devel] Version 2.0 rc5

Will rc5 restore the "nextcall" contesting feature? Ed W0YK ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Version 2.0

On 24/11/2018 20:16, Microsoft Outlook wrote: How do I get Verizon 2.0 until all the bugs are out of revision 4.? I put 1.9 back on but want 2.0! OM, you will have to use your time machine. You did purchase one on Black Friday? WSJT-X v2.0.0 is scheduled for release on December 10th 2018.

[wsjt-devel] Version 2.0

How do I get Verizon 2.0 until all the bugs are out of revision 4.? I put 1.9 back on but want 2.0! ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Version 2.0

How do I get Verizon 2.0 until all the bugs are out of revision 4.? I put 1.9 back on but want 2.0! ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] version 2.0.0-rc1 experience

This has been the case for FT8 since the first v1.9 beta back in 2017.   The developers do NOT want to create an automated QSO machine, so human intervention to initiate another CQ call is required. Neil, KN3ILZ On 9/22/2018 1:42 AM, DeYoung James wrote: 1) The transmitter always goes off aft

Re: [wsjt-devel] version 2.0.0-rc1 experience

Hi Jim, On 9/22/2018 1:42 AM, DeYoung James N8OQ via wsjt-devel wrote: 1) The transmitter always goes off after a QSO.  Under "settings-general" the box is unchecked. This behavior is by design, and has always been true for FT8. It is to prevent WSJT-X from making robotic QSOs. 2) There ar

[wsjt-devel] version 2.0.0-rc1 experience

Greetings, On-air testing today 2018 September 21st. 1) The transmitter always goes off after a QSO.  Under "settings-general" the box is unchecked.  2) There are now too many font/background color combinations for my little brain to process on the fly.  Consider perhaps logic blocking the col

Re: [wsjt-devel] version control

On 14/01/2017 12:09, Wolfgang wrote: if I compile, it updates and I will have a r7486 - but on the source-forge page, it says the latest is r7495 ? Can someone help me / explain please ? Hi Wolfgang, we have had a few queries about this recently. All should review the first few chapters of t

[wsjt-devel] version control

Hi all, if I compile, it updates and I will have a r7486 - but on the source-forge page, it says the latest is r7495 ? Can someone help me / explain please ? 73 de Wolfgang OE1MWW -- Amateur radio is the most expensive type of free-of-charge communication! Amateurfunk ist die teuerste

Re: [wsjt-devel] Version 1.7 User Guide

Hi Joe Section 8.1 I think either the notes in Astro window or the user guide text could benefit from an explanation of how to enter sked frequency directly into band edit box. The frequency entered has to be in the form nnnk (eg 225k) which puts sked frequency at band edge + 225kHz. Maybe a s

Re: [wsjt-devel] Version 1.7 User Guide

Hi Joe Yes, fine now. In section 6.5, file path needs changing: "navigate to ...\save\samples\130610_2343.wav" I guess this result is with two pass decoding selected as specified earlier in the tutorial. I kept getting 18 decodes, but noticed my erasure patterns and aggressive decoding level w

Re: [wsjt-devel] Version 1.7 User Guide

On 27/10/2016 2:33 AM, Black Michael wrote: Perhaps more approriately JT-Alert-X, by VK3AMA, is currently only available for Windows. A re-write is underway for cross-platform support and planned for 2017. de Mike W9MDB Also, it hasn't been called JT-Alert-X for a very long time. The h

Re: [wsjt-devel] Version 1.7 User Guide

Many thanks to all those providing suggestions for improvements to the WSJT-X User Guide. Your comments are greatly appreciated! -- Joe, K1JT -- The Command Line: Reinvented for Modern Developers Did the resurge

Re: [wsjt-devel] Version 1.7 User Guide

Hi Charlie, > The two JT4 files are reported by Windows as 52s in length, compared to > others that are 59s. Also at a lower bitrate (maybe WSJT10 recordings?). Correct. This has now been taken care of. > Are you updating online user guide as you go (at the URL you gave out), or > are the edits

Re: [wsjt-devel] Version 1.7 User Guide

HI Joe > > Better still, find out why the files don't work with *Decode at 52s* > checked. This should not happen. I will fix... The two JT4 files are reported by Windows as 52s in length, compared to others that are 59s. Also at a lower bitrate (maybe WSJT10 recordings?). Are you updating onl

Re: [wsjt-devel] Version 1.7 User Guide

Hi Charlie, > Mystery solved re non decode of JT4 examples. > > They decode fine if decode at 52s is *not* checked. > > Given JT4 is intended for EME, it may be better to choose files that work > with decode at 52s checked. This anomaly is fixed in revision 7236. -- Joe

Re: [wsjt-devel] Version 1.7 User Guide

Subject: [wsjt-devel] Version 1.7 User Guide 12. Cooperating Programs JT-ALERT-X, by VK3AMA, is available only for Windows. - The hyperlink for "JT-ALERT-X" is not correct. The link should be "hamapps.com". In addition, the sentence should read JT

[wsjt-devel] Version 1.7 User Guide

12. Cooperating Programs JT-ALERT-X, by VK3AMA, is available only for Windows. - The hyperlink for "JT-ALERT-X" is not correct. The link should be "hamapps.com". In addition, the sentence should read JTAlert, by VK3AMA, is available only for Windows. --- Parker W5ADD --

Re: [wsjt-devel] Version 1.7 User Guide

Hi Charlie, Thanks for catching this. > Mystery solved re non decode of JT4 examples. > > They decode fine if decode at 52s is *not* checked. > > Given JT4 is intended for EME, it may be better to choose files that work > with decode at 52s checked. Better still, find out why the files don't wor

Re: [wsjt-devel] Version 1.7 User Guide

Hi Joe Mystery solved re non decode of JT4 examples. They decode fine if decode at 52s is *not* checked. Given JT4 is intended for EME, it may be better to choose files that work with decode at 52s checked. Charlie > Hi all, > > Slowly but surely, a respectable User Guide for WSJT-X v1.7 has b

Re: [wsjt-devel] Version 1.7 User Guide

Hi Joe I have now been able to decode the two JT4 sample files. I am not sure why I had difficulty before. Charlie > Hi all, > > Slowly but surely, a respectable User Guide for WSJT-X v1.7 has been > taking shape. Much material has been added over the past week or so -- > and quite a bit more,

Re: [wsjt-devel] Version 1.7 User Guide

Hi Rex and Bill, Thanks for the corrections to the User Guide text concerning *Allow Tx frequency changes while transmitting*. I should have caught that... and will fix it. -- Joe -- The Command Line: Reinvent

Re: [wsjt-devel] Version 1.7 User Guide

Hi Rex & Joe, comments in line below. On 26/10/2016 03:23, Rex Moncur wrote: Section 8.1 has the following statement: If you will use automatic Doppler tracking and your radio accepts frequency-setting commands while transmitting, check *Allow Tx frequency changes while transmitting*. *Tran

Re: [wsjt-devel] Version 1.7 User Guide

Hi Joe I've got up to Section 6.3. I think before this, perhaps at the beginning of that section, there needs to be an instruction to download the Samples, as otherwise the user won't have them, together with a stepwise method of how to do it (ie click the appropriate box to start the download).

Re: [wsjt-devel] Version 1.7 User Guide

Hi Joe, Some suggestions: 1.A note about possible false positives from antivirus programs as part of the installation instructions.Something along the lines of how many limited use programs are often tagged as having an 'issue' because the program is not widely used, and thus is not in

Re: [wsjt-devel] Version 1.7 User Guide

Hi Joe Section 8.1 has the following statement: If you will use automatic Doppler tracking and your radio accepts frequency-setting commands while transmitting, check Allow Tx frequency changes while transmitting. Transceivers known to permit such changes include the IC-735, IC-756 Pro II,

Re: [wsjt-devel] Version 1.7 User Guide

I offer the following (sorry I am not familiar with the system used to make it easier to correct): 1.1 New in Version 1.7 “New Franke-Taylor decoder toreplace” (should be ‘to replace’) 4.2. Radio "Set Poll Interval to the desired interval for WSJT-X to query your radio. For most radios a smal

Re: [wsjt-devel] Version 1.7 User Guide

Hi Joe Table 2 in 15.2.5 sets out the sensitivity for JT4 prior to the implementation of the variable bin-width procedure. The sensitivity now is that same for all sub-modes of JT4 when the spreading is low. The problem with this table is that some people build beacons with lower sub-modes in th

[wsjt-devel] Version 1.7 User Guide

Hi all, Slowly but surely, a respectable User Guide for WSJT-X v1.7 has been taking shape. Much material has been added over the past week or so -- and quite a bit more, even today. If you have not referred to the User Guide recently, please give it a careful look. A fresh copy is available

Re: [wsjt-devel] version 1.6 and 1.7

imanche 14 août 2016 19:40 À : wsjt-devel@lists.sourceforge.net Objet : Re: [wsjt-devel] version 1.6 and 1.7 On 14/08/2016 16:27, f5umy wrote: > Bonjour f5djl. Pourriez vous me faire parvenir le lien de chargement > de le version 1.7 car impossible de la trouver. Amicalement F5UMY >

Re: [wsjt-devel] version 1.6 and 1.7

On 14/08/2016 16:27, f5umy wrote: > Bonjour f5djl. Pourriez vous me faire parvenir le lien de chargement > de le version 1.7 car impossible de la trouver. Amicalement F5UMY > Philippe Bonjour Philippe, https://sourceforge.net/p/wsjt/mailman/message/35262891/ 73 Bill G4WJS.

[wsjt-devel] Version R 5637 up on Google Driver

Everyone, the latest release, R 5637 is up on Google Drive along with the text file. https://drive.google.com/folderview?id=0B42rF4Jby8-vfjZza0I3VUN6UXFEa2NDdGszajZlOGk0TEhTeTFhSUY3UF81WmV4THVaVE0&usp=sharing Note: If you were running with AFC checked (like me) please uncheck it.