Fri, 28 Sep 2018 16:41:18 -0500
Steven Franke via wsjt-devel
kirjoitti:
> Thanks Jarmo. The wav file that you provided was a great help. I’ve
> found and fixed that bug. I expect the fix to be incorporated into
> the next release candidate.
>
> Steve k9an
Great! Let's move on and ride towards
Had a great time Wednesday night 17 contacts in 60 minutes. Rig Yaesu FTdx3000
40 meter dipole in attic approx. 26ft above ground in a crowed neighborhood in
New Orleans, Louisiana.
There was an issue when in process with a QSO and a new call would arrive, I
was unable to select the new call
> On Sep 28, 2018, at 9:33 AM, jarmo wrote:
>
> Fri, 28 Sep 2018 12:07:40 +0100
> Bill Somerville kirjoitti:
>
>> you should be able to replay the .WAV files and determine which
>> period causes he issue. Set the application up as it was for original
>>
> Hi Bill
>
> Think found file, did
FYI...doesn't crash on RC2 on WIndows 10.
de Mike W9MDB
On Friday, September 28, 2018, 9:39:48 AM CDT, jarmo wrote:
Fri, 28 Sep 2018 12:07:40 +0100
Bill Somerville kirjoitti:
> you should be able to replay the .WAV files and determine which
> period causes he issue. Set the
Oops! I just realized that there were no exchanges listed in the report!
Since it was not a contest, I didn't do the job properly. Sorry for the
erroneous report.
I did not encounter any unusual call signs.
Also I mis-reported the number as 23 and it was only 20, with a few a little
before the
On 28/09/2018 07:38, jarmo wrote:
Now I know, that this has happened
between 0400Z --- 0615Z and I have .wav files.
When I pressed OK, wsjtx crashed. I have looked those .wav files from
that two hours time and see file after every fifteen seconds, so kind of
hard to find exact one ?
Maybe I'm
Aha, Could it be that I used ONS in exchange instead of just ON? I
figured as we were mocking and ARRL contest I should use my proper
section, but not so in RU.
Jeff VE3CV
On 27 Sep 2018 18:07, Joe Taylor
wrote:
> Dave --
>
> Please use the original (or at least an
informative) subject line
Followup from last night’s RU and logging issues. The Cabrillo log generated
by WSJT-X is accurate, but as others have also noted is what N1MM+ logged and
produced is incorrect and unscorable since it can only take what the UDP
broadcast from WSJT-X has offered it. The native WSJT-X ADIF file
Without reading too much info of the new version
Due to my eyes, I need clear contrasts in software,
and I tried to find the option of changing font color,
but without any luck.
The reason is that with all the new options of new things received
in the band activity pane, I would like to
Hi Jim and Steve
Got again this:
Running: /usr/bin/jt9 -s WSJT-X -w 1 -m 3 -e /usr/bin -a
/home/oh1mrr/.local/share/WSJT-X -t /tmp/WSJT-X
At line 41 of file /home/bill/wsjtx-prefix/src/lib/ft8/encode174_91.f90
Fortran runtime error: Bad value during integer read
Error termination. Backtrace:
10 matches
Mail list logo
