Re: [wsjt-devel] Update after v2.7.0-rc6

Hi John, If you have an M1 or M2, I recommend the 240730 version of my i+ version of WSJT- X

Re: [wsjt-devel] Update-2: JTSDK-Win CLI Branch Available For Testing

Hello All, I've had a several questions asking about svn checkouts for the various WSJT-X branches and what has changed in the ^/cli-test branch. For the benefit of all, I'm posting to the list rather than individually. For anyone using using the ^/cli-test branch, checkout- is no longer used

Re: [wsjt-devel] Update-2: JTSDK-Win CLI Branch Available For Testing

Hello All, I've had a several questions asking about svn checkouts for the various WSJT-X branches and what has changed in the cli-test branch. For he benefit of all, I'm posting to the list rather than individually. For anyone using using the ^/cli-test branch checkout- is no longer used for

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

On 20/11/2015 15:17, Joe Taylor wrote: Hi Joe, ... > >> https://dl.dropboxusercontent.com/u/4192709/wsjtx-main.html > With default settings my browsers display your html file very nicely. > I'd say the 90% setting is an improvement. OK, I will commit that change. > > To my eyes, the pdf file you

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

Hi Bill, See below. On 11/20/2015 05:55 AM, Bill Somerville wrote: > On 19/11/2015 22:07, Greg Beam wrote: >> If we're not going to ship a PDF with the package, Asccidoctor has a >> module that can be installed via gem to generate PDF's. It's >> implementation is not 100% yet, but it's working fo

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

Hi Bill and Greg, Thanks for looking into the font-rendering issue I raised. > https://dl.dropboxusercontent.com/u/4192709/wsjtx-main.html With default settings my browsers display your html file very nicely. I'd say the 90% setting is an improvement. To my eyes, the pdf file you posted here >

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

On 19/11/2015 22:07, Greg Beam wrote: > If we're not going to ship a PDF with the package, Asccidoctor has a > module that can be installed via gem to generate PDF's. It's > implementation is not 100% yet, but it's working for v1.7.0. This > "should" also work for the v1.6.0-RC version. > > To inst

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

I forgot to add, if you want a nice TOC that hyperlinks, add the attribute -a toc: asciidoctor-pdf -a toc ./user_guide/wsjtx-main.adoc -o wsjtx-devel-v1.7.0.pdf The document is 55 pages, but could use some additional page breaks. 73's Greg, KI7MT On 11/19/2015 15:07, Greg Beam wrote: > Hi Bil

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

Hi Bill, Joe If we're not going to ship a PDF with the package, Asccidoctor has a module that can be installed via gem to generate PDF's. It's implementation is not 100% yet, but it's working for v1.7.0. This "should" also work for the v1.6.0-RC version. To install / test: * open JTSDK-QT gem

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

On 19/11/2015 14:24, Joe Taylor wrote: > The default font size is considerably larger than the one used in our > previous Asciidoc builds. I think it's too big. > > One measure: as formatted for printing, the User guide is now 71 pages > compared with 42 pages with Asciidoc. Some of this may be a

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

Hi Bill, Thanks for doing the switch-over to Asciidoctor. Works OK here. > If any of the slight formatting changes are problematic I can probably > fix them quickly in the style sheet. The default font size is considerably larger than the one used in our previous Asciidoc builds. I think it's

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

Hello All, After the last update I posted this evening for JTSDK Nix, WSJT-X v1.7.0 is now building OK using AsciiDoctor, either a full build or just the user guide itself. WSJT-X v1.6.0-RCx is still using AsciiDoc ( Python27 version ). Both the full build or just the user guide is OK here as

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

Just a quick follow up. On Linux, with AsciiDoctor installed as below, I was able to build v1.7.0 r6131 using JTSDK Nix 2.0.17. Docs and Manpages seem OK to me. 73's Greg, KI7MT On 11/18/2015 08:55 PM, KI7MT wrote: > Hello All, > > For JTSDK Win32, everything should be ready to go now. > > U

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

Hello All, For JTSDK Win32, everything should be ready to go now. Ubuntu, 14.04, you need to install AsciiDoctor via the Ruby Gem system, due to a version conflict. sudo apt-get install ruby sudo gem install asciidoctor That should do it. After version 14.04, just install asciidoctor and you s

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

On 10/11/2015 21:44, KI7MT wrote: > Joe has approved the Ascdictor migration. The plan as it stands: > > * WSJT-X v1.6.1: Migrate to Asciidoctor Hi All, I have committed the changes to switch to asciidoctor for User Guide generation in the development branch for WSJT-X. Instructions for what too

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

Hi Bill, Tnx!. I was looking that possibility, just hadn't gotten that far. This makes the transition easier for sure. 73's Greg, KI7MT On 11/10/2015 02:56 PM, Bill Somerville wrote: > On 10/11/2015 21:44, KI7MT wrote: >> *STYLESHEETS* >> - There are a couple things that need be customized, lik

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

On 10/11/2015 21:44, KI7MT wrote: *STYLESHEETS* - There are a couple things that need be customized, like font sizes and possibly Section Header colours etc. That can be worked on for the WSJT-X v1.6.1 release. - We should create a master *.css file and stick it in the repository somewhere, then

Re: [wsjt-devel] update on sfrsd

On 13/09/2015 13:49, Steven Franke wrote: > I am also triggering a number of weird errors — for example: the fft wisdom > initialization started up in the middle of decoding all files in a directory Hi Steve, that message box is not smart, it simply comes up if a decode cycle takes longer than 1

Re: [wsjt-devel] update on sfrsd

t; > I would guess that the log file problems are due to abnormal exits from > sfrsd causing truncated log output. >> >> Mike W9MDB > 73 > Bill > G4WJS. >> >> -Original Message- >> From: Bill Somerville [mailto:g4...@classdesign.com] >> Sent: Sun

Re: [wsjt-devel] update on sfrsd

causing truncated log output. > > Mike W9MDB 73 Bill G4WJS. > > -Original Message- > From: Bill Somerville [mailto:g4...@classdesign.com] > Sent: Sunday, September 13, 2015 7:16 AM > To: wsjt-devel@lists.sourceforge.net > Subject: Re: [wsjt-devel] update on sfrsd >

Re: [wsjt-devel] update on sfrsd

etely different walk-through of the window or some system flushing problem like you suggested. Mike W9MDB -Original Message- From: Bill Somerville [mailto:g4...@classdesign.com] Sent: Sunday, September 13, 2015 7:16 AM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] update on

Re: [wsjt-devel] update on sfrsd

73 Bill G4WJS. >> -Original Message- >> From: Steven Franke [mailto:s.j.fra...@icloud.com] >> Sent: Saturday, September 12, 2015 11:59 PM >> To: WSJT software development >> Subject: Re: [wsjt-devel] update on sfrsd >> >> Joe and Bill, >> >>

Re: [wsjt-devel] update on sfrsd

Original Message- > From: Steven Franke [mailto:s.j.fra...@icloud.com] > Sent: Saturday, September 12, 2015 11:59 PM > To: WSJT software development > Subject: Re: [wsjt-devel] update on sfrsd > > Joe and Bill, > > I am running wsjt-x (wsjtx_exp branch) using my dec

Re: [wsjt-devel] update on sfrsd

development Subject: Re: [wsjt-devel] update on sfrsd Joe and Bill, I am running wsjt-x (wsjtx_exp branch) using my decoder program (sfrsd) renamed to kvasd. It seemed to work OK at first, although the decodes that wsjt-x displays are shown in a different order than they are when I use the “real

Re: [wsjt-devel] update on sfrsd

Joe and Bill, I am running wsjt-x (wsjtx_exp branch) using my decoder program (sfrsd) renamed to kvasd. It seemed to work OK at first, although the decodes that wsjt-x displays are shown in a different order than they are when I use the “real” kvasd. Now, in addition to the results coming ou

Re: [wsjt-devel] update on sfrsd

Joe, FYI, examining the results a bit more, I notice that sfrsd decoded cases containing as many as 38 bad symbols (out of 63). I haven’t done the same study for kvasd - it doesn’t return the total number of errors, unfortunately. More important, I also notice that the vast majority of the succ

Re: [wsjt-devel] UPDATE - Re: Building Hamlib3 question

Hi Bill, On 6/25/2015 3:58 AM, Bill Somerville wrote: > On 25/06/2015 10:51, KI7MT wrote: >> Hi Bill, > Hi Greg, > > ... > >>> I can fix that, there are a few other related changes needed. That will >>> at least allow autogen.sh to run but here are deeper issues with >>> configure itself. The conf

Re: [wsjt-devel] UPDATE - Re: Building Hamlib3 question

On 25/06/2015 10:51, KI7MT wrote: > Hi Bill, Hi Greg, ... >> I can fix that, there are a few other related changes needed. That will >> at least allow autogen.sh to run but here are deeper issues with >> configure itself. The configure script is going to barf if $SRCDIR or >> `pwd` have whitespac

Re: [wsjt-devel] UPDATE - Re: Building Hamlib3 question

Hi Bill, On 06/25/2015 03:23 AM, Bill Somerville wrote: > On 25/06/2015 09:09, KI7MT wrote: >> Hello All, > Hi Greg, >> >> This should be resolved now. From the MinGW/MSYS folks ( >> http://www.mingw.org/wiki/Getting_Started ) they strongly recommend >> users *do not install / use Mingw/MSYS* with

Re: [wsjt-devel] UPDATE - Re: Building Hamlib3 question

On 25/06/2015 09:09, KI7MT wrote: > Hello All, Hi Greg, > > This should be resolved now. From the MinGW/MSYS folks ( > http://www.mingw.org/wiki/Getting_Started ) they strongly recommend > users *do not install / use Mingw/MSYS* with spaces in reference paths, > this would include User Names. JTSDK

Re: [wsjt-devel] UPDATE: Re: WSPR / WSJT python3-pil 2.6.1 issue update

Hi John, I can confirm your change works as expected on my Ubuntu 14.04 install. /src.linux-x86_64-3.4/Audio-f2pywrappers.o libjt.a -L/usr/lib/x86_64-linux-gnu \ -L/usr/local/lib -L/usr/lib/gcc/x86_64-linux-gnu/4.8/ \ -lpthread -lportaudio -lsamplerate -lfftw3f -lgfortran -o \ ./Audio.cpytho

Re: [wsjt-devel] UPDATE: Re: WSPR / WSJT python3-pil 2.6.1 issue update

Hi John, See below. On 01/08/2015 01:46 AM, John Nelson wrote: > Hi Greg, > > I know you are concentrating on Debian/Ubuntu and other *nix issues. > However, for the record, the status for Mac OSX with Python 3.4, and latest > PIL is: > > OSX 10.7 and 10.9 (and probably 10.8 but not tested)

Re: [wsjt-devel] UPDATE: Re: WSPR / WSJT python3-pil 2.6.1 issue update

Hi Greg, I know you are concentrating on Debian/Ubuntu and other *nix issues. However, for the record, the status for Mac OSX with Python 3.4, and latest PIL is: OSX 10.7 and 10.9 (and probably 10.8 but not tested): WSJT and WSPR build and operate satisfactorily. OSX 10.10: WSJT and WSPR

Re: [wsjt-devel] update

Hi Bill, 2014-05-11 21:17 GMT+02:00 Bill Somerville : > > If you only have 2.8.10 or earlier from the 13.04 repositories then you > can try commenting out the 'add_subdirectory (debian)' line from the top > level CMakeLists.txt. This should still build the install target without > problems. > I

Re: [wsjt-devel] update

On 11/05/2014 19:29, Waldek SPdwaONG wrote: Hi, Hi Waldek, I have try update today my wsjt-x and after run my script I have following errors == CMake Error at debian/CMakeLists.txt:3 (string): string does not recognize sub-command TIMES

Re: [wsjt-devel] [Update] - WSPR Source Tree Updates - (builds, docs, hamlib, fmt, wspr0 etc)

Hi Bill, That may be a question for Joe, but with AC_CHECK I looked for the headers first, then .so -o -e then .a. So if the .so is available it should link against it. At least that is my understanding of how it's put together / should work. I'm in Windows at the moment, but If I recall, when I

Re: [wsjt-devel] [Update] - WSPR Source Tree Updates - (builds, docs, hamlib, fmt, wspr0 etc)

On 07/05/2014 22:48, ki7mt wrote: Hi Greg, > Hi Chuck, > > I did a bit of searching on RPM-FIND. for libfftwf3.a looks like you need: > > For Static > fftw-static I stand corrected on the availability of a static fftw library. I am still wondering why anyone would want to statically link a library

Re: [wsjt-devel] [Update] - WSPR Source Tree Updates - (builds, docs, hamlib, fmt, wspr0 etc)

On 07/05/2014 22:28, Chuck Forsberg WA7KGX wrote: Hi Chuck, > Turns out there is no libfftw3f.a on my system. > I downloaded the current fftw3 source from fftw.org, > compiled and installed it. Still no libfftw3f.a anywhere > on my system except for one in the wspr source > directory (??) libfftwf

Re: [wsjt-devel] [Update] - WSPR Source Tree Updates - (builds, docs, hamlib, fmt, wspr0 etc)

I added it in Makefile. On 05/07/2014 03:13 PM, ki7mt wrote: > Hi Chuck, > > Ok, well we know you can build it. I added some changes this morning. > Lets, and see what the results are. Should only take a minute or two. > > cd ./wspr > make clean > make distclean > svn update > ./autogen.sh <== ma

Re: [wsjt-devel] [Update] - WSPR Source Tree Updates - (builds, docs, hamlib, fmt, wspr0 etc)

Hi Chuck, Ok, well we know you can build it. I added some changes this morning. Lets, and see what the results are. Should only take a minute or two. cd ./wspr make clean make distclean svn update ./autogen.sh <== make need to chown $USER:$USER && chmod +x ./autogen.sh make python -O wspt.py T

Re: [wsjt-devel] [Update] - WSPR Source Tree Updates - (builds, docs, hamlib, fmt, wspr0 etc)

I installed fftw-static to get fftw3f.a Then I added -lfftw3f to the LIBS and compiled. These incantations have resulted in a wspr 4103 that On 05/07/2014 02:48 PM, ki7mt wrote: > Hi Chuck, > > I did a bit of searching on RPM-FIND. for libfftwf3.a looks like you need: > > For Static > fftw-stati

Re: [wsjt-devel] [Update] - WSPR Source Tree Updates - (builds, docs, hamlib, fmt, wspr0 etc)

Hi Chuck, I did a bit of searching on RPM-FIND. for libfftwf3.a looks like you need: For Static fftw-static For Dev Headers: fftw3-devel Share Libs fftw-libs-single-3.3.4-1 But I'm not an RPM expert. For me on Ubuntu 14.04, it was one package for all of them libfftw3-dev 73's Greg, KI7MT On

Re: [wsjt-devel] [Update] - WSPR Source Tree Updates - (builds, docs, hamlib, fmt, wspr0 etc)

Turns out there is no libfftw3f.a on my system. I downloaded the current fftw3 source from fftw.org, compiled and installed it. Still no libfftw3f.a anywhere on my system except for one in the wspr source directory (??) On 05/07/2014 01:16 PM, Joe Taylor wrote: > Chuck, Greg -- > >>> just now I i

Re: [wsjt-devel] [Update] - WSPR Source Tree Updates - (builds, docs, hamlib, fmt, wspr0 etc)

Hi Joe, Yes, understand. I added that check to configure.ac .. configure should fail if headers aren't found or the lib can't execute execute properly: AC_CHECK_LIB([fftw3f], [sfftw_destroy_plan_], [HAS_FFTW3_L=1], [HAS_FFTW3_L=0]) He should get an FFTW ... OK on a sucessful configure. It fi

Re: [wsjt-devel] [Update] - WSPR Source Tree Updates - (builds, docs, hamlib, fmt, wspr0 etc)

Chuck, Greg -- >> just now I installed python3-tkinter and now that compliant is gone. Yes. This is required, as stated before. >> Now "python3 wspr.py" stops complaining that >> >> [caf@omen3 wspr]$ python3 wspr.py >> Traceback (most recent call last): >> File "wspr.py", line 45, in >>

Re: [wsjt-devel] [Update] - WSPR Source Tree Updates - (builds, docs, hamlib, fmt, wspr0 etc)

Hi Chuck, see below On 05/07/2014 01:43 PM, Chuck Forsberg WA7KGX wrote: > On 05/07/2014 08:17 AM, ki7mt wrote: >> Hi Chuck, >> >> A few questions, see below. >> >> On 05/07/2014 03:01 AM, Chuck Forsberg WA7KGX wrote: >>> I tried the new wspr under both 64 bit Fedora 20 and 64 bit Fedora Rawhide

Re: [wsjt-devel] [Update] - WSPR Source Tree Updates - (builds, docs, hamlib, fmt, wspr0 etc)

On 05/07/2014 08:17 AM, ki7mt wrote: > Hi Chuck, > > A few questions, see below. > > On 05/07/2014 03:01 AM, Chuck Forsberg WA7KGX wrote: >> I tried the new wspr under both 64 bit Fedora 20 and 64 bit Fedora Rawhide. > When you say the new wspr, do you mean you checked out the latest from SVN? yes

Re: [wsjt-devel] [Update] - WSPR Source Tree Updates - (builds, docs, hamlib, fmt, wspr0 etc)

Hi Chuck, A few questions, see below. On 05/07/2014 03:01 AM, Chuck Forsberg WA7KGX wrote: > I tried the new wspr under both 64 bit Fedora 20 and 64 bit Fedora Rawhide. When you say the new wspr, do you mean you checked out the latest from SVN? > > I have been running wspr 3829 for some time, c

Re: [wsjt-devel] [Update] - WSPR Source Tree Updates - (builds, docs, hamlib, fmt, wspr0 etc)

I tried the new wspr under both 64 bit Fedora 20 and 64 bit Fedora Rawhide. I have been running wspr 3829 for some time, compiling it repeatedly with each new version of Rawhide without issues. I am stumped on the new version of wspr. Depending on how I call it, wspr fails because it can not find