Re: [wsjt-devel] wsjtx 1.9.0-rc4.rpm for Fedora 28

2018-05-20 Thread Claude Frantz
On 05/21/2018 07:46 AM, Saku wrote: Hi Saku, Mike, Bill & All, > I recommend: Do not upgrade to F28. At least not yet. The need to upgrade the operating system is often guided by the necessity to get updates of the components. Such an upgrade is a long running process and there are addition post

Re: [wsjt-devel] wsjtx 1.9.0-rc4.rpm for Fedora 28

2018-05-20 Thread Claude Frantz
On 05/21/2018 04:12 AM, Michael Pittaro wrote: Hi Michael & All, > Pulse remembers the setting for individual applications - the version > change may have caused it to treat wsjt as a 'new' application, and > forget all you're carefully tweaked settings. In my understanding pulseaudio doesn't re

Re: [wsjt-devel] wsjtx 1.9.0-rc4.rpm for Fedora 28

2018-05-20 Thread Saku
Hi MIke ! I recommend: Do not upgrade to F28. At least not yet. F27 works as should. Even with 1.9.0-rc4. According to my previous post I have now tested with that laptop's own sound card and it results same as with external USB sound device. Settings/Audio: "pulse" does not give TX audio, us

Re: [wsjt-devel] wsjtx 1.9.0-rc4.rpm for Fedora 28

2018-05-20 Thread Michael Pittaro
I'm not running this config, but I have Fedora 27 with 1.8. I recommend ​ poking around in the pule audio mixer (pavucontrol) Pulse remembers the setting for individual applications - the version change may have caused it to treat wsjt as a 'new' application, and forget all you're carefully tweak

Re: [wsjt-devel] Delete wav files patch

2018-05-20 Thread Black Michael via wsjt-devel
So this adds a new menu item which does erase on exit and is the default choice now for first run.  Turns on tooltips for this menu too to explain the items. https://www.dropbox.com/s/o1qago0lcvdctj5/delwav2.patch?dl=1 de Mike W9MDB---

Re: [wsjt-devel] Delete wav files patch

2018-05-20 Thread Bobby Chandler
Mike, how are these patches applied? Thanks, Bobby/N4AU From: Black Michael via wsjt-devel Sent: Sunday, May 20, 2018 10:05 AM To: WSJT Software Development Cc: Black Michael Subject: [wsjt-devel] Delete wav files patch In many instances left over wav files can accumulate even if save "None"

Re: [wsjt-devel] wsjtx 1.9.0-rc4.rpm for Fedora 28

2018-05-20 Thread Claude Frantz
On 05/20/2018 06:12 PM, Saku wrote: Hi Saku & All, > RX was ok, but no sound for TX. (I > have similar interface in use with shack PC, F27. It works both TX & RX > set as "pulse". The same apply here. > 2nd: was that every time program was closed it did not wipe lock file > (and the wsjtx folde

Re: [wsjt-devel] wsjtx & the pulseaudio streams

2018-05-20 Thread Saku
HI Claude! With Fedora 26 and 27 this works ok. Pulse is remembering  setting for wsjt-x. How ever there I have done /etc/pulse/daemon.conf    flat-volumes = no With F28 I'm not sure yet. There is at least "no TX-audio" issue if "pulse" is selected. with "alsa-" selection TX seems to work and

[wsjt-devel] wsjtx 1.9.0-rc4.rpm for Fedora 28

2018-05-20 Thread Saku
Hi ! During weekend I tested latest rpm with laptop that I do not normally use at ham shack (that has F27 and self compiled wsjtx). F28 was upgraded during last week, so everything should be nearly then last packages. Wsjtx was:  wsjtx-1.9.0-0.3.rc4.fc28 / jskarvad / 2018-05-02 10:02:01 from

Re: [wsjt-devel] wsjtx & the pulseaudio streams

2018-05-20 Thread Bill Somerville
On 20/05/2018 17:03, Claude Frantz wrote: Hi All, If running in an environment using pulseaudio, wsjtx creates streams having a name containing the PID. Therefore the name of the stream is different in every program run. pulseaudio is not able to save the volume of such streams. If I use the ava

[wsjt-devel] wsjtx & the pulseaudio streams

2018-05-20 Thread Claude Frantz
Hi All, If running in an environment using pulseaudio, wsjtx creates streams having a name containing the PID. Therefore the name of the stream is different in every program run. pulseaudio is not able to save the volume of such streams. If I use the available option named "pulse" in the Audio Con

Re: [wsjt-devel] Delete wav files patch

2018-05-20 Thread Black Michael via wsjt-devel
How about a separate menu entry "None at all" or "None+Erase"? de Mike W9MDB On Sunday, May 20, 2018, 10:54:24 AM CDT, Bill Somerville wrote: On 20/05/2018 16:05, Black Michael via wsjt-devel wrote: In many instances left over wav files can accumulate even if save "None" is

Re: [wsjt-devel] for_us patch

2018-05-20 Thread Bill Somerville
On 20/05/2018 15:33, Black Michael via wsjt-devel wrote: On non-FT8 modes (i.e. JT65) receiving a message with your callsign is not being displayed on the Rx Frequency panel unless within 10Hz. e.g.  This will show up in Band Activity but not Rx Frequency window. W9MDB W1ABC RRR Here's a patc

Re: [wsjt-devel] Delete wav files patch

2018-05-20 Thread Bill Somerville
On 20/05/2018 16:05, Black Michael via wsjt-devel wrote: In many instances left over wav files can accumulate even if save "None" is selected. This patch will remove all wave files on program exit if "None" is selected. https://www.dropbox.com/s/fq8hb43toopy6mp/delwav.patch?dl=1 de Mike W9

[wsjt-devel] Delete wav files patch

2018-05-20 Thread Black Michael via wsjt-devel
In many instances left over wav files can accumulate even if save "None" is selected. This patch will remove all wave files on program exit if "None" is selected. https://www.dropbox.com/s/fq8hb43toopy6mp/delwav.patch?dl=1 de Mike W9MDB

[wsjt-devel] for_us patch

2018-05-20 Thread Black Michael via wsjt-devel
On non-FT8 modes (i.e. JT65) receiving a message with your callsign is not being displayed on the Rx Frequency panel unless within 10Hz. e.g.  This will show up in Band Activity but not Rx Frequency window.  W9MDB W1ABC RRR Here's a patch to fix it so that any msg directed at your callsign shows

[wsjt-devel] Latest Manual with Rev v1.8.0 r8193 (On-Line)

2018-05-20 Thread Tom Morton via wsjt-devel
The latest on-line manual is really good! It is extensive and covers just about every aspect of the software system. I spent several hours going through it and discovered many things now covered that I had to discover on my own or were brought up in the user group. Kudos for a job well done.