Re: [wsjt-devel] WSJT-X version 1.60 devel by K1JT and Yeasu FT-991 (buffer underflow)

2015-09-21 Thread John N1ISA
Peter Frenning[ OZ1PIF]  writes:

> 
> 
> Den 21-09-2015 kl. 22:01 skrev Peter
>   Frenning [OZ1PIF]:
> 
> 
>   Den 21-09-2015 kl. 19:39 skrev KI7MT:
> 
>   
> Hello Haken,
> 
> I can't ( won't ) speak to Mint 17.x specifics, as it is *not* Ubuntu,
> however, I can state, all of my PPA's work properly on Ubuntu 14.04+ as
> that is my main distribution for building and testing WSJT-X on Linux.
> 
> It is well known that Mint has implemented unique sound system when
> compared to Ubuntu proper (Unity). These issues are not Ubuntu bugs
> (IMHO), clearly not WSJT-X bugs, and the issue(s) should be addressed
> with the Mint folks.
> 
> 
> 73's
> Greg, KI7MT
> 
> 
>   
>   I'm running 1.6.0 r5881 (32bit) from Greg's PPA on Mint 17.1 and 
17.2 - 
> no sound system modifications made, and no problems whatsoever. Running 
> WSPR-2 and JT65+JT9 modes. Many many JT9 & JT65 QSOs made, and hundreds 
> of hours running WSPR-2 with Tx enabled.
> 
> 
> 
> Forgot to say that I'm using a modified SignalinkUSB
>   connected to a Tentec Orion 2 (mostly) or a Yaesu FT-847-- 
> Vy 73 de OZ1PIF/5Q2M, Peter
> 
> **
> ** If it sounds too good to be true --  **
> ** it is!   **
> ** If it sounds about right -- make **
> ** sure you can afford to be wrong! **
> **  **
> **   -- Robert Heinlein:**
> **   "Time enough for love" **
> **
> email: peter(no-spam filler)  frenning.dk
> http://www.frenning.dk/oz1pif.htm
> Ph. +45 4619 3239/ +45 2332 9464
> Snailmail:
> Peter Frenning
> Ternevej 23
> DK-4130 Viby Sj.
> Denmark
> **
> 
> 
>   
> 
> -
-
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 

Greetings All,

I used to see this in a terminal running custom minimal Ubuntu install. It 
never caused me any operating issues, but I attempted to correct the 
reported underflow. I haven't been running WSJT-X all Summer, because I 
have been doing computer hardware upgrades, and my ham computers HDD's are 
wiped, but as I recall, using alsa-mixer to mute the 1 unnecessary audio 
channel corrected the problem, but... I experimented a lot with my OS 
setup, and in the end I got rid of Pulseaudio. WSJT-X works just fine on a 
ALSA only setup, that is, no pulseaudio. Again, this is all from recalling 
my OS installation setup. I am inclined to think that muting the unused 
audio channel will correct this issue, as Signalink only using 1 channel. I 
believe.

It is also possible that using the Ubuntu 15.04, and later might also 
correct this issue, I say that because I tend to use the latest and 
greatest Ubuntu release, currently 15.10, and that has all the latest QT 
updated software as well. I was using 15.10 this last Spring 2015 with 
WSJT-X, and I know for certain, I stopped seeing this "underflow" issue 
reported in the terminal, everything was working perfectly. The latest 
WSJT-X dev. releases of that time period.

I'll be up and running WSJT-X again real soon.

I hope this helps.

73, John, N1ISA



--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSPR-2 Segmentation Fault in Linux

2015-07-13 Thread John N1ISA
John N1ISA  writes:

> 
> Greetings All...
> 
> I am seeing a WSPR-2 segmentation fault running WSJT-X v1.6.0-devel r5717 
> in Linux. I am using a custom Ubuntu 15.04 install. I have run countless 
> WSJT-X v1.6.0 devel versions without any issues for many, many months 
now.
> 
> I am fairly confident that I ran WSPR-2 without any segmentation faults 
> with r5700, and earlier versions. I updated to r5716 this morning, and 
was 
> running JT65 without any issues, and then updated to r5717 this 
afternoon, 
> and attempt to run WSPR-2, but I get a Segmentation Fault at 59 second 
> mark, and also when just changing modes... from JT65 to WSPR-2.
> 
> I start WSJT-X in a terminal via the command line. All I see is 
> "Segmentation fault" in the terminal. There is no additional details, or 
> information provided.
> 
> I can also get a segmentation fault when just changing modes, from JT65 
to 
> WSPR-2. When I click WSPR-2 I get a immediate crash, with segmentation 
> fault displayed in the terminal. I have not see this issue in any other 
> WSJT-X devel release.
> 
> I do find it a bit odd, that when I do to re-start WSJT-X. The mode is 
> "JT65", and I see the "Red" frequency box with 14.095 600. I would expect 
> that when I restart, I would be in WSPR-2 mode.
> 
> I can start WSJT-X in WSPR-2 mode, and I will observe a segmentation 
fault 
> at second 59 (immediate crash).
> 
> So, to clarify my bug report:
> 
> #1 I see a WSPR-2 segmentation fault at second 59 (immediate crash at the 
> 59 second mark).
> #2 I see a WSPR-2 segmentation fault when just changing modes... from 
JT65 
> to WSPR-2 (immediate crash when I click WSPR-2 mode, when I was 
previously 
> running JT65 successfully decoding).
> 
> I can run JT65 mode in r5717 without any issues.
> 
> 73, John, N1ISA
> 
> -
-
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> 


Hi Bill, Steve...

Today, I came on the list to review the debugging procedures that Bill 
outlines in response to my bug report, and found the posting from Steve 
about the commit to address issues relate to the segmentation fault that I 
was observing.

WSJT-X v1.6.0-devel r5719 corrects my reported problem with WSPR-2 
segmentation faults in Linux.

>>>> Steve... to answer you question. Yes, I was operating WSPR-2 with "Tx 
Pct" set to 0%. When I updated to r5719, I tested the operation of WSPR-2 
with Tx Pct still set to 0%.

I have not seen any segmentation faults while using WSPR-2 in Linux using 
release 5719.

All interest and feedback I received related to the issues I was having, 
and the resulting fix is greatly appreciated.

Thank you Gentleman.

73, John, N1ISA



--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSPR-2 Segmentation Fault in Linux

2015-07-12 Thread John N1ISA
Bill Somerville  writes:

> 
> On 12/07/2015 20:18, John N1ISA wrote:
> > Greetings All...
> Hi John,
> >
> > I am seeing a WSPR-2 segmentation fault running WSJT-X v1.6.0-devel 
r5717
> > in Linux. I am using a custom Ubuntu 15.04 install. I have run 
countless
> > WSJT-X v1.6.0 devel versions without any issues for many, many months 
now.
> >
> > I am fairly confident that I ran WSPR-2 without any segmentation faults
> > with r5700, and earlier versions. I updated to r5716 this morning, and 
was
> > running JT65 without any issues, and then updated to r5717 this 
afternoon,
> > and attempt to run WSPR-2, but I get a Segmentation Fault at 59 second
> > mark, and also when just changing modes... from JT65 to WSPR-2.
> >
> > I start WSJT-X in a terminal via the command line. All I see is
> > "Segmentation fault" in the terminal. There is no additional details, 
or
> > information provided.
> >
> > I can also get a segmentation fault when just changing modes, from JT65 
to
> > WSPR-2. When I click WSPR-2 I get a immediate crash, with segmentation
> > fault displayed in the terminal. I have not see this issue in any other
> > WSJT-X devel release
> >
> > I do find it a bit odd, that when I do to re-start WSJT-X. The mode is
> > "JT65", and I see the "Red" frequency box with 14.095 600. I would 
expect
> > that when I restart, I would be in WSPR-2 mode.
> >
> > I can start WSJT-X in WSPR-2 mode, and I will observe a segmentation 
fault
> > at second 59 (immediate crash).
> >
> > So, to clarify my bug report:
> >
> > #1 I see a WSPR-2 segmentation fault at second 59 (immediate crash at 
the
> > 59 second mark).
> > #2 I see a WSPR-2 segmentation fault when just changing modes... from 
JT65
> > to WSPR-2 (immediate crash when I click WSPR-2 mode, when I was 
previously
> > running JT65 successfully decoding).
> >
> > I can run JT65 mode in r5717 without any issues.
> I can't reproduce this so you may need to help me a little with 
> diagnosing this issue. First a couple of questions:
> 
> How are you building WSJT-X?
> Do you know how to build a debug configuration?
> Do you have any experience of using the gdb debugger?
> >
> > 73, John, N1ISA
> 73
> Bill
> G4WJS.
> 
> -
-
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> 

Hi Bill,

>>>>>>>> You said..."How are you building WSJT-X?"

I use the build procedure you posted a very long time ago...

I install these packages: cmake subversion pkg-config clang gfortran 
libfftw3-dev git libgfortran3 libusb-dev autoconf libtool texinfo qt5-
default qtmultimedia5-dev libqt5multimedia5-plugins libqt5serialport5-dev 
libc6 libgcc1 libquadmath0

and use this procedure:

mkdir ~/src

cd ~/src/

git clone git://git.code.sf.net/u/bsomervi/hamlib u-bsomervi-hamlib

cd u-bsomervi-hamlib/

git checkout integration

mkdir -p ~/build/hamlib

cd ~/build/hamlib/

~/src/u-bsomervi-hamlib/autogen.sh --prefix=$HOME/local/hamlib --disable-
shared --enable-static --disable-winradio

make && make install

cd ~/src/

svn checkout svn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx wsjtx

mkdir -p ~/build/wsjtx/Release

cd ~/build/wsjtx/Release/

cmake -D WSJT_GENERATE_DOCS=OFF -D WSJT_INCLUDE_KVASD=ON -D 
WSJT_SKIP_MANPAGES=ON -D CMAKE_PREFIX_PATH:PATH=~/local/hamlib -D 
CMAKE_INSTALL_PREFIX=~/local/wsjtx/Release ~/src/wsjtx

cmake --build . --target install -- -kj

Test:

~/local/wsjtx/Release/bin/wsjtx

>>>>>>>> You said... "Do you know how to build a debug configuration?" No, 
Bill. I've never done that. Building WSJT-X was the first software I've 
ever built, and I've only done that using the method you described in a 
posting.


>>>>>>>> You said... "Do you have any experience of using the gdb 
debugger?" No. I have no experience with any debugging tools, but I am 
willing to try, if you think it's worth your time, and effort.

73, John, N1ISA


--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] WSPR-2 Segmentation Fault in Linux

2015-07-12 Thread John N1ISA
Greetings All...

I am seeing a WSPR-2 segmentation fault running WSJT-X v1.6.0-devel r5717 
in Linux. I am using a custom Ubuntu 15.04 install. I have run countless 
WSJT-X v1.6.0 devel versions without any issues for many, many months now.

I am fairly confident that I ran WSPR-2 without any segmentation faults 
with r5700, and earlier versions. I updated to r5716 this morning, and was 
running JT65 without any issues, and then updated to r5717 this afternoon, 
and attempt to run WSPR-2, but I get a Segmentation Fault at 59 second 
mark, and also when just changing modes... from JT65 to WSPR-2.

I start WSJT-X in a terminal via the command line. All I see is 
"Segmentation fault" in the terminal. There is no additional details, or 
information provided.

I can also get a segmentation fault when just changing modes, from JT65 to 
WSPR-2. When I click WSPR-2 I get a immediate crash, with segmentation 
fault displayed in the terminal. I have not see this issue in any other 
WSJT-X devel release.

I do find it a bit odd, that when I do to re-start WSJT-X. The mode is 
"JT65", and I see the "Red" frequency box with 14.095 600. I would expect 
that when I restart, I would be in WSPR-2 mode.

I can start WSJT-X in WSPR-2 mode, and I will observe a segmentation fault 
at second 59 (immediate crash).

So, to clarify my bug report:

#1 I see a WSPR-2 segmentation fault at second 59 (immediate crash at the 
59 second mark).
#2 I see a WSPR-2 segmentation fault when just changing modes... from JT65 
to WSPR-2 (immediate crash when I click WSPR-2 mode, when I was previously 
running JT65 successfully decoding).

I can run JT65 mode in r5717 without any issues.

73, John, N1ISA



--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] FFT Wisdom Calculation/Calibration Quality During Setup

2015-02-25 Thread John N1ISA
Joe/Bill/Developer's,

Yesterday, I did a clean install of my OS, and then did a new build of 1.5.0-
devel. When I start WSJTX for the very first time, I immediately go to the 
"Settings" tab to select, and input my user parameters. I then adjust the 
Wide Graph parameters, and almost always adjust the audio input slider last. 
As a result, my Wide Graph is always bright red, reflecting the over driven 
state coming from my audio input.

Yesterday, the new FFT Wisdom calculation/calibration was invoked 
automatically during my WSJTX user parameters setup routine.

Does the over driven stated of my audio into the decoder, effect the quality 
of FFT Wisdom calculation/calibration?

Does the decoder ignore the audio input stream, and just do mathematical 
calculations, and my misadjustment of the audio has no impact on the quality 
of the automatic calibration procedure?

>From my layman perspective, it does not seem to. Yesterday, I got excellent 
decode's. All of varying signal strengths. I even got a -27 dB JT65 decode. 
Still, I am wondering if my FFT Wisdom calculation is the best if could, or 
should be.

73, John, N1ISA 


--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] sysdefault:CARD=CODEC equals freedom from Pulseaudio

2015-02-23 Thread John N1ISA
Bill,

Lately, I've been hacking my Linux audio configuration. To see if I could 
improve the audio being fed to WSJTX via Pulseaudio. Trying different 
resample methods used by Pulseaudio. 

It was my understanding that in the Linux environment, WSJTX required 
Pulseaudio to run. If I used the Pulseaudio --kill command in a terminal, 
WSJTX would close.

Recently, when I did a svn update, I noticed changes related to the WSJTX 
"Settings" Audio Soundcard Input/Output selections. That got me thinking 
that I might be able to break free of Pulseaudio, and send the audio stream 
from ALSA directly to WSJTX.

I have posted on SourceForge that I run WSJTX in a very basic X11 
environment. I just need 14 packages in a Ubuntu command line environment 
to get WSJT up and running.

Today, I did a clean install, and left out the Pulseaudio package... and 
everything works great!!!

I did get a message in the terminal:  PulseAudioService: 
pa_context_connect() failed , but it in no way effects the operation of 
WSJTX.

I am glad to be free of Pulseaudio!

I think the software engineering of WSJTX is exceptional. I recently broke 
my 12 decode record. I have made a few 14 decodes (JT65 - single mode 
only). The decodes pop up really fast!

73, John, N1ISA



--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSJT-X 1.5-Dev r4966 Font Issues ( Linux)

2015-02-17 Thread John N1ISA
ki7mt  writes:

> 
> Hello All,
> 
> I'm seeing some line height issues in the the decode boxes in Linux.
> 
> 1. The CQ's are being converted (displayed as) CO.
> 2. JT9 "  " sign is being truncated on the bottom (abt ~3% to 5% 
being
> removed).
> 
> Basically, it looks like the tails of the "Q's" are being taken off.
> I've tried several fonts & heights, doesn't seem to help much.
> 
> Just wondering if anyone else is seeing this or if it may be my setup
> somehow?
> 
> 73's
> Greg, KI7MT
> 
> -
-
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?
id=190641631&iu=/4140/ostg.clktrk
> 

Greg,

I'm running the latest devel release 4969 on Ubuntu 15.04. I do a custom 
command line install, and use LWM as my window manager. I pull in 2 font 
packages ttf-ubuntu-font-family, and fonts-droid. I also install the 
fontconfig package, and use a basic .font.conf.

The fonts render perfect on my machine. In fact, the fonts that are being 
displayed within WSJTX, are the fonts that, I think, the QT GUI pulls in. 
That being:

San Serif Normal 9
Courier 10 Pitch Bold 10

This is my .fonts.conf:

tconfig>


rgb




true




hintslight




true




lcddefault





As far as I know/remember, I have never seen any font rendering issues, on 
any WSJTX devel release, that I have used within the Ubuntu environment.

The WSJTX GUI looks great on my Ubuntu machine. The fonts are clean, bold, 
and very sharp. In my experience, better than Windows.

I hope this feedback offers some insight to your font issues.

73, John, N1ISA


--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Bug Report: Wrong Cursor Type in Band Activity and Rx Frequency Text Windows

2015-02-13 Thread John N1ISA
Greetings All,

Bug Report: Wrong cursor type in Band Activity and RX Frequency Text Windows.

Expected Action = Arrow cursor
Observed Action = I Beam cursor

WSJTX Version = 1.5.0-devel r4957
Operating System = Ubuntu Linux with dmz-cursor-theme

Additional Information:

All other field locations within the Main Window, and the Wide Graph, the 
expected action of using the Arrow cursor, and/or the I Beam cursor is 
correct.

The I Beam cursor does not effect the ability to double click on a CQ Call 
and to populate the "Generate Std Msgs" fields, or in any way effect the 
normal RX/TX function of WSJTX, so in that regard fixing the cursor might be 
just a cosmetic fix, but when using very small fonts, it might be difficult 
for some operators to accurately select the correct CQ call in a multiple 
"stacked" CQ's situation in the Band Activity text window. I have also notice 
that when "half" of the I Beam cursor is use to select a CQ call, the 
Generate Std Msgs will be populated with the data from the Band Activity 
above, or below the CQ call, depending on the I Beam cursor position, i.e., 
above, or below the intended CQ call that is double clicked. If the operator 
is not completely vigilant, that would result in very poor operating.

73, John, N1ISA 


--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] jt9_opm not seen when using the terminal top command

2015-02-10 Thread John N1ISA
Hi Joe/Bill/Developers,

Last week, when I installed Bill's wsjtx_omp.patch, and ran the Linux command 
top in a terminal, I would see the PID jt9_omp at the 50 second mark at 
decode.

To keep this post short, and to the point, I recently built WSJTX with Ubuntu 
15.04 "Vivid" alpha 2. There are lot's of package updates that seem to me to 
be very pertinent to building WSJTX in Linux. Even QT5 has been updated. 
WSJTX builds, and functions perfectly in Ubuntu 15.04.

Anyway, I've just installed Bill's r4950 Commit. I do not see jt9_omp anymore 
when running the top command.

It is my understanding that when using a gcc compiler, that OpenMP is built 
in.

Do I still need to apply Bill's patch? Does Commit r4950 turn on OpenMp in 
WSJTX, except on non-Mac platforms? Or, is this just Bill's effort to setup 
the future use of OpenMP at a later date?

Am I running WSJTX correctly?

I would like to run WSJTX-devel, in a Linux environment, in such a way that 
would expose any useful reportable bugs to the developers.

73, John, N1ISA


--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Not using when building WSJTX --without-cxx-binding

2015-02-07 Thread John N1ISA
Bill,

You recently answered a post of mine about applying the wsjtx_omp.patch. I 
used the generic method of using "patch" as you said, successfully.

You also commented about me having to use "--without-cxx-binding" to build 
wsjtx without error. You said that you do not have too, and that you build 
successfully on all platforms. That got me thinking as to why. What I was 
able to figure out is that I needed the package "pkg-config". Today, I was 
looking around the git hamlib repository, to look at your work/commits, to 
see if I could glean any information to support my determination about 
needing the package "pkg-config". I found some comments from N0NB that seem 
to support the requirement of the pkg-config package.

When I installed pkg-config, I got a build feedback statement that "hamlib" 
was found.

I have been able to figure out (with your posted information) how to build 
WSJTX in a very minimal Ubuntu command line setup. The following packages 
are required:

cmake subversion pkg-config svn clang-3.5 gfortran libfftw3-dev git 
libgfortran3 libusb-dev autoconf libtool texinfo qt5-default qtmultimedia5-
dev libqt5multimedia5-plugins libhamlib-dev asciidoc

When I do a clean install, I build WSJTX first, and then add the following 
packages for a window manager environment:

xorg xserver-xorg-video-intel xserver-xorg-input-evdev xserver-xorg-input-
mouse xterm dmz-cursor-theme ttf-ubuntu-font-family xfonts-terminus fonts-
droid lwm alsa-base alsa-utils pulseaudio fontconfig

As you can see, I use Intel hardware for graphics. WSJTX 1.5.0-devel runs 
great in such a environment. I am going to try my WSJTX build, and window 
manager environment techniques using Ubuntu 15.04 Vivid Alpha 2 very soon. 
I am going to try the cmake option "-D WSJT_SKIP_MANPAGES=ON", so I do not 
have to install the asciidoc package, due to it's very large size.

I thought I would post this information, as it might be helpful to someone 
building WSJTX also. I have been using Linux for just over 10 years, and in 
all that time I have never had to post a question about Linux, because 
someone, some where, has always asked it first, and all you had to do was 
use Google and search for the answer. WSJTX is different in that regard, in 
that it is such unique software. So, maybe posting this information here, 
will be helpful, and in some small way I can give back to this project.

Anyway, thanks for answering my post. Your comments have helped me obtain a 
greater understanding about Linux, and building WSJTX.

73, John, N1ISA


--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] git-apply -v /src/wsjtx/wsjtx_omp.patch

2015-02-04 Thread John N1ISA
WSJTX Developers...

I use the build process posted here a while ago. Recently, I had to add "--
without-cxx-binding", to obtain a error free build. It has worked well for 
me.

Question about applying Bill's wsjtx_omp.patch.

I build out of my ~/HOME directory. My WSJTX source code is located at 
~/src/wsjtx. If I move Bill's patch into the ~/src/wsjtx directory, and:

cd ~/src/wsjtx/

git-apply -v ~/src/wsjtx/wsjtx_omp.patch

Bill's patch will be applied to: mainwindow.cpp...

and then just build as I normally would, and follow Bill's directions related 
to the first decode process of WSJTX.

Will this work, and apply the patch correctly?

73, John, N1ISA



--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Ubuntu Package libgomp1 - GCC OpenMP

2015-02-03 Thread John N1ISA
Greetings All,

In Dr. Taylor's recent posting stating his improvements to the decoder 
performance in the WSJTX Development Branch release r4926, he stated that, 
"further improvements can probably be made by using more than one core 
concurrently, e.g., by using OpenMP".

I am using the the Development Branch release 4926 in a Ubuntu Linux 
environment, using the compiling techniques developed by Bill, G4WJS.

In Ubuntu Package Repository there is a libgomp1 package... a GCC OpenMP 
(GOMP) support library.

Would the performance improvements stated by Joe, K1JT, in his posting 
about using "OpenMP", be as simple as installing the Ubuntu libgomp1 
package?

I do use a i7-4770 CPU Machine, and even from my layman's perspective this 
might be overkill, by I do enjoy tweaking performance. I have been able to 
decode 12 signals frequently, and very fast, when all the required 
variables are in place. My radio's audio passband, and my WSJTX settings do 
limit my decode performance, but I always wondered if I could decode more 
signals if present in my passband/waterfall. In my setup, 12 decodes has 
like a "fixed" threshold that I can not get past.

Thanks to all the developer's/contributor's to the excellent WSJTX 
software. WSJTX has given me countless hours of radio/computer/QSO 
enjoyment. I recently taught myself how to compile in Linux, and following 
the WSJTX development branch is much fun also.

Truly, Sincerely, Thanks!

73, John, N1ISA


--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] KVASD version 1.12 --Decode test *** PASSED ***

2015-01-09 Thread john N1ISA
Greetings All,

I've been running WSJTX in Fedora FC21. There are .rpm's in the Fedora Copr 
Repository.

I've had to install KVASD manually via the command line, with the required 
dependencies.

Recently, I've noticed a Sourceforge branch that has a Linux KVASD 64bit 
folder.

This morning, I did a clean install of Fedora FC20. I plan on installing 
WSJTX and WSPR. I am hoping that reverting back to Fedora FC20, I will not 
have the segmentation fault when running WSPR... as a observational 
experiment.

Anyway... I installed the 64 bit version of the required KVASD 
dependencies.

glibc
libquadmath
libgfortran
libgcc

I then copied KVASD, as root via the command line to /usr/bin and then ran 
chmod 755 /usr/bin

I tested the KVASD installation with kvasd and got the copyright, and 
license statement. I also tested KVASD with kvasd -v and got:

KVASD version 1.12 --Decode test *** PASSED ***

So there is a 64 bit version of KVASD now???

What is the difference between version 1.11 and 1.12???

Lastly, as a FYI, the WSJTX 1.4 builds from the Fedora Copr Repository 
worked perfectly in Fedora FC21 with the 32 bit version of KVASD, and the 
required WSJTX 1.4 dependencies installed.

73, John, N1ISA 


--
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] WSJTX .deb and kvasd-installer Packages in Official Repositories

2014-12-16 Thread John N1ISA
WSJTX functions perfectly in a very minimal Ubuntu environment. I can 
install a 64 bit Command Line Ubuntu installation, and add just 7 packages 
to get a minimalist display manager going.

Ubuntu Command Line Base install plus:

xorg
twm
alsa-base
alsa-utils
pulseaudio
xfonts-100dpi
libgfortran3:i386

I use wget to download the WSJTX .deb package, and the kvasd-installer.

I use "dpkg -i" and "apt-get install -f" to install WSJT and kvasd, and all 
the required dependencies are pulled in.

I do a little bit of configuring. Add myself to the "audio" and "dailout" 
groups. Edit my /etc/modprobe.d/alsa-base.conf file to force my USB sound 
card to use slot 0.

I edit my .xinitrc file to open 3 xterm's in twm. One terminal to start 
WSJTX, another terminal to run ntpdate to adjust the RTC, and another 
terminal to run alsamixer.

When I start WSJTX in a terminal, no errors are reported. WSJTX works 
perfectly in this environment. You would be wrong to think that the GUI 
would look plain in such a minimalist display manager environment. The 
fonts are sharp, and WSJTX looks and functions great!

The WSJTX .deb package, and the kvasd-installer package function perfectly 
in Linux, but from my layman's perspective, I find it very impressive that 
WSJTX/kvasd-installer installs and functions so well in such a minimalist 
Ubuntu setup.

I did this minimal installation exercise to test and keep up my Linux 
configuration skills, and and for the fun in doing so, but it did give me a 
great sense of satisfaction to see the whole process work out so well, and 
for that I tip my hat, and say "Thank You" to all the developers who have 
created such a excellent piece of software under the leadership of Dr. 
Taylor K1JT.

I hope this feedback about how well the WSJTX .deb package installs and 
functions, and that with the creation of the kvasd-installer, that a time-
line will be developed to push the WSJTX package upstream in the the 
official Debian/Ubuntu repositories, because I have always felt that our 
hobby has been given a "honor" to have distinct, and separate "Ham Radio" 
listing in the Official repositories of the main stream Linux 
Distributions. 

73, John, N1ISA


--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSJT-X and pulse audio volume level

2014-11-30 Thread John N1ISA
Hi Richard,

You asked, "Is there a way to make sure a consistent name is presented to
PulseAudio?"

I think I might have a solution that has worked for me. It has even
corrected a few minor USB Sound Card issues with WSPR.

I have my motherboard sound card disabled in BIOS. I use a USB Sound Card as
my default Sound Card.

In the alsa-base.conf file I force my USB Sound Card to use slot O.

If you open, and edit up /etc/modprobe.d/alsa-base.conf you will see the
line(s):

#prevent abnormal driver from grabbing index 0

options snd-usb-audio index=-2

I edit the number -2 to 0 (zero).

My line looks like this:
options snd-usb-audio index=0

Also... notice the line at the bottom in alsa-base.conf:

#keep snd-usb-audio from be(e)ing loaded as the first sound card

options snd-usb-audio index=-2

I edit mine to look like this:
#options snd-usb-audio index=-2

I comment out the line with a #

then... Reboot.

Oh... do not forget to edit as "root", or "sudo".

In Ubuntu... sudo nano /etc/modprobe.d/alsa-base.conf

This might help you. These edits have helped me with pulseaudio in wsjtx and
wspr. If these edits do not work for you, you can revert back to the
original alsa-base.conf with your text editor.

Give it a try.

73, John, N1ISA




--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] WSPR KI7MT .deb Package Segmentation Fault

2014-11-20 Thread John N1ISA

Greetings,

First, I would like to say Thank You for everyone's efforts in making the
WSJTX Linux .deb package available. I've run it in custom Debian and Ubuntu
environments with zero issues. It gives me great pleasure to use WSJTX in
Linux. Thank You!

I've have run KI7MT's .deb package for WSPR in Ubuntu successfully also,
until this recent version update.

With WSPR version 4.0.1-1, I get a program crash with the following error:

/usr/bin/wspr: line 42: 1347 Segmentation fault  /usr/bin/python3 -0 wspr.py

I have also seen line 42: 1438 and line 42: 1472 Segmentation faults.

I am using a custom minimal install of Ubuntu 14.10 (Utopic) with a minimal
Mate Desktop environment.

I install the wspr .deb package with dpkg -i and then pulled in the required
dependencies with apt-get install -f.

WSPR runs fine until "second 55 decode", and then WSPR closes. I see the
errors reported in a terminal window.

Does WSPR use KVASD? Is this a issue with KVASD, and/or the dependencies
required for KVASD to run?

I am running a 64 Bit OS, do I need to load libgfortran3:i386?

Can I do anything to fix this?

Thanks in advance.

73, John, N1ISA






--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Ubuntu Build Error(s) : gzip: man/man1/jt9.1: No such file or directory

2014-09-07 Thread John N1ISA
Greetings WSJTX Developers,

I have used the G4WJS build procedures posted by KI7MT on 24 Aug. 2014
successfully for 2 recent revision updates on my Ubuntu 14.04.1 machine.

The WSJTX software worked excellent in Ubuntu! All the previous bugs I had
in the Linux environment are gone.

The last successful attempt, I just deleted the /build, /local, /src folders
in my home folder, and used the ~/.bash_history to build the new revision of
WSJTX.

Doing the same procedure with the r4257 branch will not work for me.

As far as I can tell this is the only error output I get on the terminal
command line:


gzip: man/man1/jt9.1: No such file or directory
gzip: man/man1/jt9code.1: No such file or directory
make[2]: *** [manpages/man/man1/wsjtx.1.gz] Error 1
make[2]: Target `manpages/CMakeFiles/manpages.dir/build' not remade because
of errors.
make[1]: *** [manpages/CMakeFiles/manpages.dir/all] Error 2
Generating Configuration.moc
Generating moc_Configuration.cpp
Generating moc_Detector.cpp
Generating moc_Modulator.cpp
Generating moc_about.cpp
Generating moc_astro.cpp
Generating moc_displaytext.cpp
Generating moc_logqso.cpp
Generating moc_mainwindow.cpp
Generating moc_meterwidget.cpp
Generating moc_plotter.cpp
Generating moc_psk_reporter.cpp
Generating moc_signalmeter.cpp
Generating moc_soundin.cpp
Generating moc_soundout.cpp
Generating moc_widegraph.cpp
[ 83%] Built target wsjtx_automoc
Linking CXX static library libwsjt_qt.a
[ 83%] Built target wsjt_qt
make[1]: Target `all' not remade because of errors.
make: *** [all] Error 2
make: Target `install' not remade because of errors.

Would manually creating the folder /man/man1 in my home folder correct this
error, or are new Linux/Ubuntu build procedures required?

Thanks,

73, John, N1ISA



--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Ubuntu Linux WSJTX Build Error Messages

2014-08-26 Thread John N1ISA

Nick,

Your suggestion to install the asciidoc package is exactly what I needed to do.

I have successfully built WSJTX 1.4 r4231 in Ubuntu using G4WJS's build
procedures. The software is up and running.

This is the first software I have ever "built".

I am very surprised to see the excellent improvements to the feature set of
WSJTX.

Thanks again Nick for your help.

73, John, N1ISA





--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Ubuntu Linux WSJTX Build Error Messages

2014-08-25 Thread John N1ISA

WSJTX Developers,

I followed the wsjtx build instructions that were recently posted. I made
good progress until the last 2 procedures.

I typed this syntax...


cmake -D CMAKE_PREFIX_PATH:PATH=/home/n1isa/local/hamlib -D
CMAKE_INSTALL_PREFIX=/home/n1isa/local/wsjtx/Release /home/n1isa/src/wsjtx


I got this error output:


CMake Error at manpages/CMakeLists.txt:8 (message):
  Failed to find a2x which is an optional requirement for non-debug

  builds on *nix platforms.
  

  You can choose to skip manpage generation and this error by setting

  the CMake option WSJT_SKIP_MANPAGES to ON.  This option is designed for

  those that are building for their own use, package builders should not

  opt to skip manpage generation since package building requires the

  manpages.


-- Configuring incomplete, errors occurred!


I ignored this error and continued typing the syntax to progress with the
build...


cmake --build . --target install -- -kj

I got this error output:

make: *** No rule to make target `install'.

I believe the "." is part of the error message, but I am not sure.

Could someone please tell me how to correct these errors.

This is a copy of the build procedure that was recently posted. All went
well for me until the last 2 parts of the build procedure that I typed out.
I did have to figure out the correct paths for my Ubuntu installation.

mkdir ~/src
cd ~/src/
git clone git://git.code.sf.net/u/bsomervi/hamlib u-bsomervi-hamlib
cd u-bsomervi-hamlib/
git checkout integration
mkdir -p ~/build/hamlib
cd ~/build/hamlib/
~/src/u-bsomervi-hamlib/autogen.sh --prefix=$HOME/local/hamlib
--disable-shared
make && make install
cd ~/src/
svn checkout svn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx wsjtx
mkdir -p ~/build/wsjtx/Release
cd ~/build/wsjtx/Release/
cmake -D CMAKE_PREFIX_PATH:PATH=~/local/hamlib \
-D CMAKE_INSTALL_PREFIX=~/local/wsjtx/Release \
~/src/wsjtx
cmake --build . --target install -- -kj

Thanks.

John, N1ISA




--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Use Device "pcm.p148k" in .asoundrc file

2014-08-19 Thread John N1ISA

Nick,

Thank you for providing me with a explanation about the virtual device
driver name, and the links to opens.org., that provide additional information.

As to the "problem" I am having... With the Debian/Ubuntu WSJTX package, I
have problem with abnormal pulsing/clicking of the TX audio stream during
the moment of PTT for about 1 second of TX. I can see these pulses in the VU
meter graph that is part of the pavucontrol package.

I thought that this TX problem I am having was unique to my various WSJTX
hardware setups, but I have heard this abnormal TX "clicking/pulsing" being
transmitted by another Amateur too, who I guess was using the Debian/Ubuntu
package of WSJTX, while listening to transmissions on 14.076 MHz.

I first heard this abnormal clicking TX noise while monitoring my own signal
with a nearby Shortwave receiver. Early on in the development of WSJTX, Dr.
Taylor suggested that WSJTX users should "listen" to their TX signal
utilizing the various suggestions he made at the time. K1JT described them
in his change log when a WSJTX upgrade was released.  I always had a great
signal sound when using the Windows version of WSJTX, but when I tried the
Linux version, I notice these "pulses". For a long time, I thought is was
just my software/hardware setup, but I have heard another Amateur TX with
this clicking/pulsing noise. I only heard it once, from this other Amateur,
he must have been using the Linux version of WSJTX.

I have tried various radio interface setups, but the only way to stop the TX
of this abnormal noise, is to use delay of the PTT for the first second of a
WSJTX TX sequence.

I also noticed a problem of some sort with the new PPA of WSPR 4.0, and
Linux WSJTX. Generally speaking, WSPR 4.0 has functioned perfectly for me,
but I installed the Debian/Ubuntu package of WSJTX on the same computer, and
this installation broke the ability of WSPR 4.0 (Linux) to connect with
pulseaudio.

I thought that maybe this "pcm.p148k" .asoundrc file might help to resolve
this issue, by telling both WSPR 4.0 and WSJTX what soundcard to use.

Anyway, thanks Nick for explaining the technical details of pcm.p148k. I
really do appreciate you taking the time to type out a reply to my post.

I will investigate those links to opensrc.org with great interest.

73, John, N1ISA




--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Use Device "pcm.p148k" in .asoundrc file

2014-08-17 Thread John N1ISA
In a bug report on launchpad for the linux version of WSJT-X, version 1.1
(does not use QT-Audio), AC6SL offer the following advice to correct a sound
card issue.

AC6SL offered this advice...

I was able to make this device work by creating ~/.asoundrc with
this entry in it, and then telling wsjtx to use device "p148k":

  pcm.p148k {
  type plug
  slave {
   pcm "hw:1,0"
   format S16_LE
   channels 1
   rate 48000
   }
  }


My question is.. what is pcm.p148k?

Is it a unique hardware device? Would I have to determine that "number" for
my setup? Or, is it just general generic software coding statement and I can
use the .asoundrc "as is", other than the pcm "hw:1,0". I do understand that
"hw:1,0" is required to be specific for my setup/hardware/device?

If I do have to find the correct "pcm.p148k" type number... how do I do
that? Use dmesg, or something similar?

One last question(s)... I know I can just copy and paste the above .asoundrc
file to my home folder, but if I was to type it out in a Text Editor, how
important is it to get the curly brackets in the right postions? I am fairly
sure I can type the .asoundrc file to look exactly as shown above, but if I
was off a space, or two, would the .asoundrc file fail to run?

Thanks.

73, John, N1ISA




--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSPR v4.0 r4215 PPA Updated / Released

2014-08-13 Thread John N1ISA


I had to add the following additional packages to my Ubuntu installation to
be able to start WSPR v4.0 ppa...

python-imaging-tk

python-pil.imagetk

python3-pil.imagetk

I do not have any rig audio, or rig control cabled yet, but the software
loads nice, and all seems well.

Thanks for making this software available to me. Much appreciation for
everyone's coding efforts.

Thanks again...

73, John, N1ISA


--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSPR v4.0 r4215 PPA Updated / Released

2014-08-13 Thread John N1ISA

I've installed the wspr v4.0 ppa on my Ubuntu 14.10 machine, but get a error
message when I attempt to start the program.

On the command line I get the follow error message...

Traceback (most recent call last):
  File "wspr.py" line 56, in 
   from PIL import Image, ImageTk, ImageDraw
ImportError: cannot import name 'ImageTk'


I did a Google search for the error message, and read that installing the
python-imaging-tk package might help, but it did not work for me.

I do a sort of custom install of Ubuntu, nothing special, just install a
command line installation with the Network install method, and then install
a  --no-install-recommends ubuntu-desktop, and then add a few additional
packages to get the installation the way I like it.

Anyway... is the error message a coding issue, or is my Ubuntu installation
missing some required dependencies? 

Thanks, 73, John, N1ISA


--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel