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 s
> 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 run
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 applic
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 now
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:
#0
