Re: [wsjt-devel] possible bugs

[Black Michael via wsjt-devel]

I've never heard of the reason why it was ever connected in the first 
place.Only thing I can think of is somebody wanted the meter to reflect what 
the waterfall was doing which is of dubious use now that the Flatten option is 
a much better solution.
And it really did not affect the "input dB reading".  When it was hooked up it 
affected the "waterfall Db level".
de Mike W9MDB


  From: Neil Zampella 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Tuesday, July 11, 2017 8:49 PM
 Subject: Re: [wsjt-devel] possible bugs
   
OK Bill .. but why did it affect the input dB reading ?  Just curious.

On 7/11/2017 5:32 PM, Bill Somerville wrote:
> On 11/07/2017 22:24, Neil Zampella wrote:
>> the slider is no longer a 'digital gain' that affects sound input, it 
>> only affect the graph.
>
> Hi Neil,
>
> it never has been a digital gain control for anything but the 
> waterfall and 2D spectrum graph. That is why it has been disconnected 
> from the input level indicator.
>
> 73
> Bill
> G4WJS.
>
>
>


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


   --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 Crashing on reopen MacOS X?

[Hisashi T Fujinaka]

I tried rebooting and it's still crashing on open.

On Tue, 11 Jul 2017, Hisashi T Fujinaka wrote:


I tried to close and reopen and now all my versions of wsjtx (1.8.0-rc1
and 1.7.0) are all crashing on open.




--
Hisashi T Fujinaka - ht...@twofifty.com
BSEE + BSChem + BAEnglish + MSCS + $2.50 = coffee

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Ross Primrose]

One feature I'd like to see is if you answer a CQ, and the station comes 
back to someone else, halt tx...


73, Ross N4RP

On 07/11/2017 07:23 PM, Ricky Scott W7PSK wrote:
As Jim said, its a nice AID to us old timers that cant click the red 
in 1 second


-- Original Message --
From: "Jim - N4ST" 
To: "'WSJT software development'" 
Sent: 7/11/2017 4:07:40 PM
Subject: Re: [wsjt-devel] FT8 and "Call 1st"


Please keep "Call 1st".  It is a great aid to us old timers.
If people don't like it, don't click the box.


73,
Jim - N4ST


-Original Message-
From: Erik - [mailto:erikcarl...@live.com]
Sent: Tuesday, July 11, 2017 12:02
To: WSJT software development 
Subject: Re: [wsjt-devel] FT8 and "Call 1st"


"We are interested in feedback from users on the question of partial QSO
automation.  Should "Call 1st" be changed or removed?"

I like it as it is. One thing though, it gets broken by callsigns 
such as
EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. 
Not a

big deal since reciprocal calls such as this one are not too common. My
over-riding request is to not remove "Call 1st".

Erik EI4KF.


 


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


-- 


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



-- 


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



--
FCC Section 97.313(a) “At all times, an amateur station must use the minimum 
transmitter power necessary to carry out the desired communications.”


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] possible bugs

[Neil Zampella]

OK Bill .. but why did it affect the input dB reading ?  Just curious.

On 7/11/2017 5:32 PM, Bill Somerville wrote:

On 11/07/2017 22:24, Neil Zampella wrote:
the slider is no longer a 'digital gain' that affects sound input, it 
only affect the graph.


Hi Neil,

it never has been a digital gain control for anything but the 
waterfall and 2D spectrum graph. That is why it has been disconnected 
from the input level indicator.


73
Bill
G4WJS.






--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] wsjt-x v1.8.0-rc1 Crashing on reopen MacOS X?

[Hisashi T Fujinaka]

I tried to close and reopen and now all my versions of wsjtx (1.8.0-rc1
and 1.7.0) are all crashing on open.

--
Hisashi T Fujinaka - ht...@twofifty.com

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] libgomp1 >=4.9

[Bill Somerville]

On 12/07/2017 01:58, Pino Zollo wrote:

Please,

where to find libgomp1 >=4.9


for Mint 17.3 alias  Ubuntu 14.04   32bit ?


Here is not available:https://packages.ubuntu.com/search?keywords=libgomp1

neither here:https://pkgs.org/download/libgomp1



TU 73

Pino ZP4KFX


Hi Pino,

it is part of the GNU compiler collection and should be installed when 
you install any of the compilers. As it is a run time library I guess it 
actually comes with libgcc if that is  separate package.


If you are using an Ubuntu 14.04 derivative then you will probably have 
to build WSJT-X (if that is the application you want) yourself. The 
source tarball we provide should work with the required dependencies 
installed.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] libgomp1 >=4.9

[Greg Beam]

Hi Pino,

I am not sure you can, as I "think" Mint 17.3 is based on Trusty (14.04), I
could be wrong, but. Trusty, even with the updates is showing gcc-4.8

https://packages.ubuntu.com/trusty/libx32gomp1
https://packages.ubuntu.com/trusty/i386/libx32gomp1/filelist

You could either upgrade, or enable additional repositories, but that gets
messy. I would say, you are better off upgrading to a newer version of Mint,
but that's up to you. 

Xenial (16.04) is using GCC 5.4.0.

73's
Greg, KI7M

-Original Message-
From: Pino Zollo [mailto:pinozo...@gmail.com] 
Sent: Tuesday, July 11, 2017 6:58 PM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] libgomp1 >=4.9

Please,

where to find libgomp1 >=4.9


for Mint 17.3 alias  Ubuntu 14.04   32bit ?


Here is not available: https://packages.ubuntu.com/search?keywords=libgomp1

neither here: https://pkgs.org/download/libgomp1



TU 73

Pino ZP4KFX


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Important : JTAlert needs upgrading (to 2.9.10) for those testing FT8 mode.

[Laurie, VK3AMA]

JTAlert users who are testing the new FT8 mode need to upgrade their 
JTAlert version to 2.9.10 to avoid sending spots to HamSpots.net as T10 
mode or JT9 mode (JTAlert earlier than 2.9.8)


Users using early versions of JTAlert who don't want to upgrade (HRD6 
log with JTAlert 2.8.7) need to turn off sending spots to HamSpots (use 
the [Alerts -> Send Spots to HamSpots.net] menu)


--
de Laurie, VK3AMA

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] libgomp1 >=4.9

[Pino Zollo]

Please,

where to find libgomp1 >=4.9


for Mint 17.3 alias  Ubuntu 14.04   32bit ?


Here is not available: https://packages.ubuntu.com/search?keywords=libgomp1

neither here: https://pkgs.org/download/libgomp1



TU 73

Pino ZP4KFX

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Distribution

[Ricky Scott W7PSK]

Laurie
have you considered adding other modes for WAS track? or was it always 
JT65/JT9?



-- Original Message --
From: "Laurie, VK3AMA" <_vk3a...@vkdxer.net>
To: wsjt-devel@lists.sourceforge.net
Sent: 7/11/2017 1:19:51 PM
Subject: Re: [wsjt-devel] Distribution




On 12/07/2017 4:10 AM, Bill Somerville wrote:
RR, Laurie. My mistake as mentioned in the other post. I will claim I 
did it so developers of other software get a head start.


BTW I did some basic tests with JTAlert using it to initiate MSK144 
and FT8 QSOs from alerts. This was necessary as I  fixed a few 
problems with the content of the UDP messages. Apart from the already 
discussed and deferred issues of dealing with shorter than 60s T/R 
periods both worked just fine, thanks.


73
Bill
G4WJS.


Hi Bill,

Thanks for the UDP test feedback.
I am still considering how best to handle the 15s T/R period of FT8. 
Regarding the broken JTAlert docking with WSJT-X when a configuration 
switch is made, that is now fixed for the next release. (I used the 
Close event to set a flag indicating that the hWnds needed to be 
refreshed which are then updated on the next Heartbeat).


de Laurie VK3AMA


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Ricky Scott W7PSK]

As Jim said, its a nice AID to us old timers that cant click the red in 
1 second


-- Original Message --
From: "Jim - N4ST" 
To: "'WSJT software development'" 
Sent: 7/11/2017 4:07:40 PM
Subject: Re: [wsjt-devel] FT8 and "Call 1st"


Please keep "Call 1st".  It is a great aid to us old timers.
If people don't like it, don't click the box.


73,
Jim - N4ST


-Original Message-
From: Erik - [mailto:erikcarl...@live.com]
Sent: Tuesday, July 11, 2017 12:02
To: WSJT software development 
Subject: Re: [wsjt-devel] FT8 and "Call 1st"


"We are interested in feedback from users on the question of partial 
QSO

automation.  Should "Call 1st" be changed or removed?"

I like it as it is. One thing though, it gets broken by callsigns such 
as
EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. Not 
a

big deal since reciprocal calls such as this one are not too common. My
over-riding request is to not remove "Call 1st".

Erik EI4KF.



--
Check out the vibrant tech community on one of the world's most 
engaging

tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Build Error

[Ricky Scott W7PSK]

that was it
I had closed it but apparently it didn’t close all the way


-- Original Message --
From: "Ricky Scott W7PSK" 
To: "Black Michael" ; "WSJT software development" 


Sent: 7/11/2017 4:04:37 PM
Subject: Re: [wsjt-devel] Build Error


Ill check Mike
thanks


-- Original Message --
From: "Black Michael" 
To: "Ricky Scott W7PSK" ; "WSJT software development" 


Sent: 7/11/2017 3:59:32 PM
Subject: Re: [wsjt-devel] Build Error

That error means WSJT-X was still running and in use.  You might have 
a hung task or just didn't exit it.


de Mike W9MDB



From: Ricky Scott W7PSK 
To: WSJT software development ; 
wsjt-devel@lists.sourceforge.net

Sent: Tuesday, July 11, 2017 5:53 PM
Subject: [wsjt-devel] Build Error

Been building for a few days with no errors, just tried today and for 
the first time Ive gotten an oops.


Thoughts, did a net search and couldnt come up with anything

Install the project...
-- Install configuration: "Release"
-- Installing: 
C:/JTSDK/wsjtx/devel/qt52/1.7.1/Release/install/bin/wsjtx.exe

CMake Error at cmake_install.cmake:31 (file):
 file INSTALL cannot copy file
 "C:/JTSDK/wsjtx/devel/qt52/1.7.1/Release/build/wsjtx.exe" to
 "C:/JTSDK/wsjtx/devel/qt52/1.7.1/Release/install/bin/wsjtx.exe".


makefile:65: recipe for target 'install' failed
mingw32-make.exe: *** [install] Error 1


CMAKE BUILD ERROR


There was a problem building ( wsjtx devel )

Check the screen for error messages, correct, then try to
re-build ( wsjtx  devel Release install )



(JTSDK-QT 5.2 ) C:\JTSDK)
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Jim - N4ST]

Please keep "Call 1st".  It is a great aid to us old timers.
If people don't like it, don't click the box.


73,
Jim - N4ST


-Original Message-
From: Erik - [mailto:erikcarl...@live.com] 
Sent: Tuesday, July 11, 2017 12:02
To: WSJT software development 
Subject: Re: [wsjt-devel] FT8 and "Call 1st"


"We are interested in feedback from users on the question of partial QSO
automation.  Should "Call 1st" be changed or removed?"

I like it as it is. One thing though, it gets broken by callsigns such as
EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. Not a
big deal since reciprocal calls such as this one are not too common. My
over-riding request is to not remove "Call 1st".

Erik EI4KF.



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Build Error

[Ricky Scott W7PSK]

Ill check Mike
thanks


-- Original Message --
From: "Black Michael" 
To: "Ricky Scott W7PSK" ; "WSJT software development" 


Sent: 7/11/2017 3:59:32 PM
Subject: Re: [wsjt-devel] Build Error

That error means WSJT-X was still running and in use.  You might have a 
hung task or just didn't exit it.


de Mike W9MDB



From: Ricky Scott W7PSK 
To: WSJT software development ; 
wsjt-devel@lists.sourceforge.net

Sent: Tuesday, July 11, 2017 5:53 PM
Subject: [wsjt-devel] Build Error

Been building for a few days with no errors, just tried today and for 
the first time Ive gotten an oops.


Thoughts, did a net search and couldnt come up with anything

Install the project...
-- Install configuration: "Release"
-- Installing: 
C:/JTSDK/wsjtx/devel/qt52/1.7.1/Release/install/bin/wsjtx.exe

CMake Error at cmake_install.cmake:31 (file):
 file INSTALL cannot copy file
 "C:/JTSDK/wsjtx/devel/qt52/1.7.1/Release/build/wsjtx.exe" to
 "C:/JTSDK/wsjtx/devel/qt52/1.7.1/Release/install/bin/wsjtx.exe".


makefile:65: recipe for target 'install' failed
mingw32-make.exe: *** [install] Error 1


CMAKE BUILD ERROR


There was a problem building ( wsjtx devel )

Check the screen for error messages, correct, then try to
re-build ( wsjtx  devel Release install )



(JTSDK-QT 5.2 ) C:\JTSDK)
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Build Error

[Black Michael via wsjt-devel]

That error means WSJT-X was still running and in use.  You might have a hung 
task or just didn't exit it.
de Mike W9MDB

  From: Ricky Scott W7PSK 
 To: WSJT software development ; 
wsjt-devel@lists.sourceforge.net 
 Sent: Tuesday, July 11, 2017 5:53 PM
 Subject: [wsjt-devel] Build Error
   
#yiv5817952705 #yiv5817952705 
--blockquote.yiv5817952705cite2{margin-left:5px;margin-right:0px;padding-left:10px;padding-right:0px;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,
 204, 204);margin-top:3px;padding-top:0px;}#yiv5817952705 
body{font-family:Tahoma;font-size:12pt;}#yiv5817952705 Been building for a few 
days with no errors, just tried today and for the first time Ive gotten an oops.
Thoughts, did a net search and couldnt come up with anything
Install the project...
-- Install configuration: "Release"
-- Installing: C:/JTSDK/wsjtx/devel/qt52/1.7.1/Release/install/bin/wsjtx.exe
CMake Error at cmake_install.cmake:31 (file):
  file INSTALL cannot copy file
  "C:/JTSDK/wsjtx/devel/qt52/1.7.1/Release/build/wsjtx.exe" to
  "C:/JTSDK/wsjtx/devel/qt52/1.7.1/Release/install/bin/wsjtx.exe".


makefile:65: recipe for target 'install' failed
mingw32-make.exe: *** [install] Error 1


 CMAKE BUILD ERROR


 There was a problem building ( wsjtx devel )

 Check the screen for error messages, correct, then try to
 re-build ( wsjtx  devel Release install )



(JTSDK-QT 5.2 ) 
C:\JTSDK)--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


   --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Possible bugs v2

[Jari A]

Hi again,

I see my error with the slider, it do say "digital gain graph windows"
I assume it was same as its been few years with wsjt-x 1.7. As it change
level display dB level, in the past.

I need to learn better of new features on 1.8.rc1. Too excited to get on
the band with it, so rtfm was obvious thing to being ignored.

I'll read the manual and my absence from here is the marker all is good ;o)

Thanks of the comments

Good night from cold rainy Helsinki.

: Jari / OH2FQV
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] possible bugs

[Bill Somerville]

On 11/07/2017 22:24, Neil Zampella wrote:
the slider is no longer a 'digital gain' that affects sound input, it 
only affect the graph.


Hi Neil,

it never has been a digital gain control for anything but the waterfall 
and 2D spectrum graph. That is why it has been disconnected from the 
input level indicator.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] JT65/JT9 Marker Setting - r7850

[Neil Zampella]

Um .. shouldn't the JT65/JT9 marker setting be grayed out for FT8??
v1.7.1.-r7850


Neil, KN3ILZ

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] possible bugs

[Neil Zampella]

Jari,

the slider is no longer a 'digital gain' that affects sound input, it 
only affect the graph.   Input adjustment is either through your OS 
sound mixer, or physically from your rig. If you put your mouse over 
the slider it will give the 'tool tip' about this.


I've got a KX3, and adjust the sound input using the AF knob.

Neil, KN3ILZ


On 7/11/2017 4:59 PM, Jari A wrote:

Hello, I'm new here, so apologies if I cause extra havoc.

WSJT-X 1.8.0-rc1
Windows 7 pro 64 bits

I think I seen few anomalies: Digital gain does not change input 
level, bar remain green and at 62dB level, even no input signal.


Second thing I note is TX5.
If I do CQ and wish to mark TX 5 after report, autoseq jumps to TX4, 
no matter what. After sequence has started, if I'm quick I can press 
send now button to get my 73 out.


If I manage to type ( opponent station who replied to me) call RRTU73 
to TX5 field, it changes to call call 73 format.


Dunno if these are worth for anything, but atleast I enbarrase myself 
at very first message to this list :o)


Very best regards,

: Jari / OH2FQV





--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] possible bugs

[Black Michael via wsjt-devel]

I just went through this with another user and he had to take out some very 
noisy cards from his desktop.With no input signal you should see pretty much no 
signal.
The input level has no control anymore from WSJT-X...it never did control the 
recording level...only the waterfall level.  It was very misleading to those 
setting audio like you.
You need to change your recording device to 0dB gain...then adjust your audio 
on the rig input in analog space to 30dB to maybe 50dB or so on the WSJT-X 
meter.

de Mike W9MDB

  From: Jari A 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Tuesday, July 11, 2017 4:01 PM
 Subject: [wsjt-devel] possible bugs
   
Hello, I'm new here, so apologies if I cause extra havoc.

WSJT-X 1.8.0-rc1
Windows 7 pro 64 bits

I think I seen few anomalies: Digital gain does not change input level, bar 
remain green and at 62dB level, even no input signal.

Second thing I note is TX5. 
If I do CQ and wish to mark TX 5 after report, autoseq jumps to TX4, no matter 
what. After sequence has started, if I'm quick I can press send now button to 
get my 73 out.

If I manage to type ( opponent station who replied to me) call RRTU73 to TX5 
field, it changes to call call 73 format. 

Dunno if these are worth for anything, but atleast I enbarrase myself at very 
first message to this list :o)

Very best regards,

: Jari / OH2FQV


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


   --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Bugs in command line tools in WSJTX 1.8.0-rc1

[Steven Franke]

Dani - 
We are aware of the fact that the command line tools are not stable at the 
moment. They will be cleaned up and tested before the GA release.
Steve, k9an

> On Jul 11, 2017, at 3:52 PM, Dani EA4GPZ  wrote:
> 
> Hi all,
> 
> I have compiled WSJTX 1.8.0-rc1 from source an I'm finding the following
> bugs in the command line tools.
> 
> jt9 will always segfault when run for JT9:
> 
> 
> $ jt9 -9 00_01.wav
> 
> Program received signal SIGSEGV: Segmentation fault - invalid memory
> reference.
> 
> Backtrace for this error:
> #0  0x7F9211B1DD98
> #1  0x7F9211B1CF30
> #2  0x7F92108100CF
> #3  0x4110F0 in symspec_
> #4  0x406D52 in MAIN__ at jt9.f90:?
> Segmentation fault
> -
> 
> ft8d will also segfault always:
> 
> ---
> $ ft8d 40 2 00_01.wav
> 
> Program received signal SIGSEGV: Segmentation fault - invalid memory
> reference.
> 
> Backtrace for this error:
> #0  0x7F4C03C8ED98
> #1  0x7F4C03C8DF30
> #2  0x7F4C029810CF
> #3  0x414C60 in bpdecode174_
> #4  0x403A5D in ft8b_
> #5  0x402693 in MAIN__ at ft8d.f90:?
> Segmentation fault
> -
> 
> ft8sim doesn't seem to work properly. When run as suggested in the example:
> 
> ft8sim "K1ABC W9XYZ EN37" 0.0 0.1 1.0   10   -18
> 
> all the samples of the generated wav file are 0.
> 
> 
> When run as
> 
> ft8sim "EA4GPZ M0HXM IO94" 0.0 0.0 0.0 1 0
> 
> there is noise and a signal in the generated wav file, but the signal is
> not valid FT8 (it covers more than 2kHz of spectrum).
> 
> 
> 73,
> 
> Dani.
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] possible bugs

[Jari A]

Hello, I'm new here, so apologies if I cause extra havoc.

WSJT-X 1.8.0-rc1
Windows 7 pro 64 bits

I think I seen few anomalies: Digital gain does not change input level, bar
remain green and at 62dB level, even no input signal.

Second thing I note is TX5.
If I do CQ and wish to mark TX 5 after report, autoseq jumps to TX4, no
matter what. After sequence has started, if I'm quick I can press send now
button to get my 73 out.

If I manage to type ( opponent station who replied to me) call RRTU73 to
TX5 field, it changes to call call 73 format.

Dunno if these are worth for anything, but atleast I enbarrase myself at
very first message to this list :o)

Very best regards,

: Jari / OH2FQV
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Bugs in command line tools in WSJTX 1.8.0-rc1

[Dani EA4GPZ]

Hi all,

I have compiled WSJTX 1.8.0-rc1 from source an I'm finding the following
bugs in the command line tools.

jt9 will always segfault when run for JT9:


$ jt9 -9 00_01.wav

Program received signal SIGSEGV: Segmentation fault - invalid memory
reference.

Backtrace for this error:
#0  0x7F9211B1DD98
#1  0x7F9211B1CF30
#2  0x7F92108100CF
#3  0x4110F0 in symspec_
#4  0x406D52 in MAIN__ at jt9.f90:?
Segmentation fault
-

ft8d will also segfault always:

---
$ ft8d 40 2 00_01.wav

Program received signal SIGSEGV: Segmentation fault - invalid memory
reference.

Backtrace for this error:
#0  0x7F4C03C8ED98
#1  0x7F4C03C8DF30
#2  0x7F4C029810CF
#3  0x414C60 in bpdecode174_
#4  0x403A5D in ft8b_
#5  0x402693 in MAIN__ at ft8d.f90:?
Segmentation fault
-

ft8sim doesn't seem to work properly. When run as suggested in the example:

ft8sim "K1ABC W9XYZ EN37" 0.0 0.1 1.0   10   -18

all the samples of the generated wav file are 0.


When run as

ft8sim "EA4GPZ M0HXM IO94" 0.0 0.0 0.0 1 0

there is noise and a signal in the generated wav file, but the signal is
not valid FT8 (it covers more than 2kHz of spectrum).


73,

Dani.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Apparent Distorted Signals

[Black Michael via wsjt-devel]

Also be aware that you're also seeing FFT effect where a strong signal looks 
"sloppy" due to the color coding as the FFT frequencies are not perfect.There's 
always FFT frequency spreading but you just don't see it as it's usually closer 
to the noise floor.
Here's an example of a loopback test on my system
A 17dB signal looks horrible but it's actually clean as a whistle (quite 
literally).  Remember this a log scale so high points get "smooshed" down.  If 
it was linear it would look a LOT cleaner.


Here's what the wave form above looks like...as you can see...a virtually 
perfect wave with no noise or artifacts.
But the FFT doesn't look so pretty...just one of the pitfalls of discrete 
Fourier Transforms.Your analog ear hears the perfect tones...the DFFT has a 
discrete ear so can't do that and has to add a bunch of frequencies together to 
represent the signal.



 --- 
Michael D. Black

  From: George J Molnar 
 To: WSJT software development  
 Sent: Tuesday, July 11, 2017 3:03 PM
 Subject: [wsjt-devel] Apparent Distorted Signals
   
Drifting a little from the “extra 3 bits” conversation, folks noticing “dirty” 
signals in the waterfall should not jump to the conclusion that it is the 
transmitter’s fault.
Between propagation conditions, multipath, and a zillion permutations of AGC, 
NB, and filter settings,  the fact is that the WSJTX waterfall is not a 
reliable display of transmitted waveforms. Most signals that appear dirty are 
really not. I’m lucky with my Flex panadapter - one can compare both 
waterfalls, one at the RF sampling level, and the other at audio. Most signals 
are quite good in quality. Browbeating other operators probably isn't a good 
use of our technology.


George J Molnar, KF2T Nevada, USA


On Jul 11, 2017, at 12:46 PM, Black Michael via wsjt-devel 
 wrote:


If you want to see what your signal looks like use hamspots.net to see who is 
receiving your signal.  This will indicate if they are using JTAlert.You can 
then search for their callsign on hamspots.net to see if they are 
transmitting...which would mean they are sitting at their rig.
Then use JTAlert's message capability via F5 to enter their callsign and send 
them a message.  You can also try emailing them but the JTAlert message is a 
touch faster.  Remember with the JTAlert message facility you can only send 
about 3 messages per minute as it only transmits at 5, 20, and 35 seconds into 
the minute and any new message will overwrite an older one still queued.
de Mike W9MDB



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

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

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


   --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Distribution

[Laurie, VK3AMA]

On 12/07/2017 4:10 AM, Bill Somerville wrote:
RR, Laurie. My mistake as mentioned in the other post. I will claim I 
did it so developers of other software get a head start.


BTW I did some basic tests with JTAlert using it to initiate MSK144 
and FT8 QSOs from alerts. This was necessary as I  fixed a few 
problems with the content of the UDP messages. Apart from the already 
discussed and deferred issues of dealing with shorter than 60s T/R 
periods both worked just fine, thanks.


73
Bill
G4WJS. 


Hi Bill,

Thanks for the UDP test feedback.
I am still considering how best to handle the 15s T/R period of FT8. 
Regarding the broken JTAlert docking with WSJT-X when a configuration 
switch is made, that is now fixed for the next release. (I used the 
Close event to set a flag indicating that the hWnds needed to be 
refreshed which are then updated on the next Heartbeat).


de Laurie VK3AMA


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Apparent Distorted Signals

[George J Molnar]

Drifting a little from the “extra 3 bits” conversation, folks noticing “dirty” 
signals in the waterfall should not jump to the conclusion that it is the 
transmitter’s fault.

Between propagation conditions, multipath, and a zillion permutations of AGC, 
NB, and filter settings,  the fact is that the WSJTX waterfall is not a 
reliable display of transmitted waveforms. Most signals that appear dirty are 
really not. I’m lucky with my Flex panadapter - one can compare both 
waterfalls, one at the RF sampling level, and the other at audio. Most signals 
are quite good in quality. Browbeating other operators probably isn't a good 
use of our technology.



George J Molnar, KF2T 
Nevada, USA


> On Jul 11, 2017, at 12:46 PM, Black Michael via wsjt-devel 
>  wrote:
> 
> If you want to see what your signal looks like use hamspots.net to see who is 
> receiving your signal.  This will indicate if they are using JTAlert.
> You can then search for their callsign on hamspots.net to see if they are 
> transmitting...which would mean they are sitting at their rig.
> 
> Then use JTAlert's message capability via F5 to enter their callsign and send 
> them a message.  You can also try emailing them but the JTAlert message is a 
> touch faster.  Remember with the JTAlert message facility you can only send 
> about 3 messages per minute as it only transmits at 5, 20, and 35 seconds 
> into the minute and any new message will overwrite an older one still queued.
> 
> de Mike W9MDB
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Suggestions for three extra bits in FT8

[James Shaver (N2ADV)]

If you throw attenuation at the signal and the issue goes away, the cause is 
most likely on the receive side.  It also helps to have a panadapter available 
(something that isn't tied into the AF chain).  The waterfall itself should not 
be used to determine signal quality.  

73,

Jim S. 
N2ADV

> On Jul 11, 2017, at 2:45 PM, Bill Somerville  wrote:
> 
>> On 11/07/2017 19:12, Tim Carlson wrote:
>> Would you consider that the first signal on the left is being overdriven 
>> somewhat?  Or is that just a consequence of a stronger signal?  Or is it 
>> some atmospheric condition causing the signal to spread?
>> 
> Hi Tim,
> 
> hard to tell but it is all too common for the Tx audio level fed to the rig 
> to be too high. This causes non-linearity and will almost certainly widen the 
> transmitted signal. The main product of clipping is harmonics but if the 
> sender is using the split operating facility that is largely innocuous due to 
> the harmonics being above 3000 Hz and attenuated by the rig's Tx SSB filter 
> low pass cut off. Still there is no excuse for over driving the audio input 
> to the rig and there is a secondary consequence. At each frequency shift of 
> the modulation there is a minimal phase discontinuity, we shift the phase 
> without a glitch but nevertheless it is a discontinuity. These small 
> discontinuities fractionally widen the signal when the audio is correctly 
> matched through to the transmitter but over drive widens them considerably. 
> This is what you are seeing, a horizontal spike on the waterfall at each tone 
> shift.
> 
> You must also be careful about attributing blame in these situations, all of 
> the above can happen on the receiving side too, so check your own house is in 
> order before accusing another of having a poor signal.
> 
> 73
> Bill
> G4WJS.
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Suggestions for three extra bits in FT8

[Black Michael via wsjt-devel]

If you want to see what your signal looks like use hamspots.net to see who is 
receiving your signal.  This will indicate if they are using JTAlert.You can 
then search for their callsign on hamspots.net to see if they are 
transmitting...which would mean they are sitting at their rig.
Then use JTAlert's message capability via F5 to enter their callsign and send 
them a message.  You can also try emailing them but the JTAlert message is a 
touch faster.  Remember with the JTAlert message facility you can only send 
about 3 messages per minute as it only transmits at 5, 20, and 35 seconds into 
the minute and any new message will overwrite an older one still queued.
de Mike W9MDB

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Suggestions for three extra bits in FT8

[Tim Carlson]

Thanks, Bill (and Gary in the previous reply)!

I’m pretty sure my receive is fine - IC-7300 into my mac using USB connection, 
AGC off, notch filter off, noise blanker off, noise reduction off, IP+ off, and 
RF Gain/USB AF Output level adjusted to 30 db with no signals present.  There 
is no adjustment on the USB audio driver.

On the transmit side, I think I’m doing everything correctly too.  But my point 
is that it is difficult to tell if you are doing it correctly when there’s not 
a good feedback mechanism from the remote side to inform you that your signal 
looks overdriven.  

I would appreciate a way for someone to tell me if my signal does look bad.  
Granted, it could be multipath or other effects beyond my control, but I would 
like to know, and there’s not a great way to communicate that in-band.

-Tim

> On Jul 11, 2017, at 12:45 PM, Bill Somerville  wrote:
> 
> On 11/07/2017 19:12, Tim Carlson wrote:
>> Would you consider that the first signal on the left is being overdriven 
>> somewhat?  Or is that just a consequence of a stronger signal?  Or is it 
>> some atmospheric condition causing the signal to spread?
>> 
> Hi Tim,
> 
> hard to tell but it is all too common for the Tx audio level fed to the rig 
> to be too high. This causes non-linearity and will almost certainly widen the 
> transmitted signal. The main product of clipping is harmonics but if the 
> sender is using the split operating facility that is largely innocuous due to 
> the harmonics being above 3000 Hz and attenuated by the rig's Tx SSB filter 
> low pass cut off. Still there is no excuse for over driving the audio input 
> to the rig and there is a secondary consequence. At each frequency shift of 
> the modulation there is a minimal phase discontinuity, we shift the phase 
> without a glitch but nevertheless it is a discontinuity. These small 
> discontinuities fractionally widen the signal when the audio is correctly 
> matched through to the transmitter but over drive widens them considerably. 
> This is what you are seeing, a horizontal spike on the waterfall at each tone 
> shift.
> 
> You must also be careful about attributing blame in these situations, all of 
> the above can happen on the receiving side too, so check your own house is in 
> order before accusing another of having a poor signal.
> 
> 73
> Bill
> G4WJS.
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Suggestions for three extra bits in FT8

[Pete]

On 2017-07-11 12:12 PM, Tim Carlson wrote:
Use one of the extra bits to indicate my desire for signal feedback. 
 Email address for my callsign could be looked up from ???
I am fairly sure that FT8 uses the same message encoding as JT65, in 
which case FT8 also has the ability to send an arbitrary 13-character 
text message using the characters in this string 
"0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ +-./?".
In the situation you described perhaps you could ask "UR PWR?" but as 
Bill points out the problem could be at your end.


@Philip Gladstone
Seems to me that the 13-character message also allows most kinds of 
contest exchange without using those extra bits.


Pete VE5VA


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Suggestions for three extra bits in FT8

[Bill Somerville]

On 11/07/2017 19:12, Tim Carlson wrote:
Would you consider that the first signal on the left is being 
overdriven somewhat?  Or is that just a consequence of a stronger 
signal?  Or is it some atmospheric condition causing the signal to spread?



Hi Tim,

hard to tell but it is all too common for the Tx audio level fed to the 
rig to be too high. This causes non-linearity and will almost certainly 
widen the transmitted signal. The main product of clipping is harmonics 
but if the sender is using the split operating facility that is largely 
innocuous due to the harmonics being above 3000 Hz and attenuated by the 
rig's Tx SSB filter low pass cut off. Still there is no excuse for over 
driving the audio input to the rig and there is a secondary consequence. 
At each frequency shift of the modulation there is a minimal phase 
discontinuity, we shift the phase without a glitch but nevertheless it 
is a discontinuity. These small discontinuities fractionally widen the 
signal when the audio is correctly matched through to the transmitter 
but over drive widens them considerably. This is what you are seeing, a 
horizontal spike on the waterfall at each tone shift.


You must also be careful about attributing blame in these situations, 
all of the above can happen on the receiving side too, so check your own 
house is in order before accusing another of having a poor signal.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Erik -]

I find that Shift+F11 or +F12 do indeed move my TX frequency but the RX 
frequency also moves a little as well.


Erik EI4KF.

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: 11 July 2017 18:19
To: WSJT software development 
Subject: Re: [wsjt-devel] FT8 and "Call 1st"

Hi all,

> For the auto 60Hz shift on answering CQs, I think this is a bad idea.  

We have never considered anything like an "auto shift" of Tx frequency.

What we *might* do is provide an easy way to move your Tx frequency up or down 
manually in increments of 60 Hz (or perhaps some other number) to choose an 
apparently free frequency.

WSJT-X v1.8.0-rc1 already has a trial version of such a facility, but its 
present logic may not be exactly what we'll want to make permanent.

As it is now, Shift+F11 and Shift+F12 move your Tx frequency up or down to the 
nearest integer multiple of 50 Hz.  Maybe this should be 60 Hz, instead, since 
(after the recent change in the FT8 symbol length) the bandwidth of an FT8 
signal is 50 Hz.

If everyone used the new FreqCal tool, we might even find that it makes sense 
to use quasi-channelized operation so that Tx frequency is always an integral 
multiple of 60 Hz.

-- Joe, K1JT

--
Check out the vibrant tech community on one of the world's most engaging tech 
sites, Slashdot.org! http://sdm.link/slashdot 
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Suggestions for three extra bits in FT8

[Gary McDuffie]

> On Jul 11, 2017, at 12:12 PM, Tim Carlson  wrote:
> 
> Would you consider that the first signal on the left is being overdriven 
> somewhat?  Or is that just a consequence of a stronger signal?  Or is it some 
> atmospheric condition causing the signal to spread?

This could also be caused by multipath.  I saw one this morning, whose QTH I’m 
quite familiar with.  He is over 100 miles from me, but behind him are the 
Rocky Mtns.  Now and then, I would even get a double decode on him.  I suspect 
he also had some hum on his signal, as I’v seen it before when conditions were 
really up between us.  When I turned my antenna, the whole picture changed.  It 
was better at some azimuths and worse at others.

Also be sure the noise blanker is turned OFF.  The NB will cause stronger 
stations to distort and spread out like that.

Gary - AG0N
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Morgen Benner]

Thanks for clarifying Joe, and thank you for the hard work you and the
development team pour into this awesome software and exciting new modes!

Sorry I misunderstood the suggestion.  I do like the idea of
quasi-channelizing FT8 since it's so dense that it has issues with decoding
overlapping signals.  I would even go so far as suggesting the software
force you to use the frequency calibration tool before it will transmit.
One extra step in the setup won't hurt anyone.

73,
KC9SWV - Morgen
President, TARA

On Tue, Jul 11, 2017 at 2:18 PM, Joe Taylor  wrote:

> Hi all,
>
> For the auto 60Hz shift on answering CQs, I think this is a bad idea.
>>
>
> We have never considered anything like an "auto shift" of Tx frequency.
>
> What we *might* do is provide an easy way to move your Tx frequency up or
> down manually in increments of 60 Hz (or perhaps some other number) to
> choose an apparently free frequency.
>
> WSJT-X v1.8.0-rc1 already has a trial version of such a facility, but its
> present logic may not be exactly what we'll want to make permanent.
>
> As it is now, Shift+F11 and Shift+F12 move your Tx frequency up or down to
> the nearest integer multiple of 50 Hz.  Maybe this should be 60 Hz,
> instead, since (after the recent change in the FT8 symbol length) the
> bandwidth of an FT8 signal is 50 Hz.
>
> If everyone used the new FreqCal tool, we might even find that it makes
> sense to use quasi-channelized operation so that Tx frequency is always an
> integral multiple of 60 Hz.
>
> -- Joe, K1JT
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Frequencies Missing in Configuration

[Bill Somerville]

On 11/07/2017 18:36, Tim Carlson wrote:

Sometime between building and running the latest update and installing 
v1.8.0-rc1 r7847 (on OS X), the frequencies for my only named configuration all 
disappeared.  The default configuration still has all the frequencies, so I 
cloned it and reset my preferences.

I’ve always let the IARU Region set to All.

I thought there was a way to reset the frequency list (I remember doing it 
after running the first FT8 build), but now I can’t find it.

Not sure what happened there.


Hi Tim,

the frequencies were supposed to automatically switch to the new 
proposed frequencies at the v1.8 upgade. It appears that has not 
happened for all for which I am sorry.


I would set the IARU region correctly for your location, it will reduce 
the frequencies offered in the band drop down to a suitable set for your 
location.


You can reset the working frequencies table to the default values by 
right-clicking the table and clicking "Reset". You will find some other 
maintenance options on the right-click context menu that you may find 
useful, for example to transfer part or all of a customized working 
frequencies table between configurations or even users.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Joe Taylor]

Hi all,

For the auto 60Hz shift on answering CQs, I think this is a bad idea.  


We have never considered anything like an "auto shift" of Tx frequency.

What we *might* do is provide an easy way to move your Tx frequency up 
or down manually in increments of 60 Hz (or perhaps some other number) 
to choose an apparently free frequency.


WSJT-X v1.8.0-rc1 already has a trial version of such a facility, but 
its present logic may not be exactly what we'll want to make permanent.


As it is now, Shift+F11 and Shift+F12 move your Tx frequency up or down 
to the nearest integer multiple of 50 Hz.  Maybe this should be 60 Hz, 
instead, since (after the recent change in the FT8 symbol length) the 
bandwidth of an FT8 signal is 50 Hz.


If everyone used the new FreqCal tool, we might even find that it makes 
sense to use quasi-channelized operation so that Tx frequency is always 
an integral multiple of 60 Hz.


-- Joe, K1JT

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Frequencies Missing in Configuration

[Tim Carlson]

Sometime between building and running the latest update and installing 
v1.8.0-rc1 r7847 (on OS X), the frequencies for my only named configuration all 
disappeared.  The default configuration still has all the frequencies, so I 
cloned it and reset my preferences.

I’ve always let the IARU Region set to All.

I thought there was a way to reset the frequency list (I remember doing it 
after running the first FT8 build), but now I can’t find it.

Not sure what happened there.

-Tim KD0GYG
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Distribution

[Bill Somerville]

On 11/07/2017 18:24, Laurie, VK3AMA wrote:
I bet, most people are running r7843 (as am I) because Sourceforge 
sent an announcement email (to subscribers) that the rc1 installer was 
available for download. 


RR, Laurie. My mistake as mentioned in the other post. I will claim I 
did it so developers of other software get a head start.


BTW I did some basic tests with JTAlert using it to initiate MSK144 and 
FT8 QSOs from alerts. This was necessary as I  fixed a few problems with 
the content of the UDP messages. Apart from the already discussed and 
deferred issues of dealing with shorter than 60s T/R periods both worked 
just fine, thanks.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Morgen Benner]

I'm new to the group, so I hope it's okay to share my opinion as I've used
JT9/65 for some time now and just started using FT8 last night.

Personally, I don't care for the Call 1st or Call Weak options.  Seems too
automated for me.  It's only a 15 second cycle, so no big deal if you don't
get them answered on the first try.  What I've been doing is:

1. Call CQ
2. Watch the Waterfall.
3. If I see someone replying to my CQ, Disable TX so I don't accidentally
CQ again.
4. As soon as possible, double-click the caller when decoded.

The JT modes all include redundancy in the transmission.  You probably have
at least 5 seconds after the start of the cycle, maybe more to start
transmitting and enough information will still make it through for a
successful decode.

That said, if others really want the auto-reply features, I won't be
heartbroken to see them included.  To each their own, as long as I could
still disable them.  Freedom of choice and all.

As for the auto-sequencing, this I like and have no problem with.  I didn't
realize it would do it at first and when I did, it was a much welcomed
help.  Don't see it as being necessary on JT9/65 since you have at least 10
seconds there.

For the auto 60Hz shift on answering CQs, I think this is a bad idea.  It
seems like it will cause a LOT of headaches when careless ops don't check
the shift direction and double over someone else's QSO instead of their
own.  Seems wrong to risk impacting others' QSOs for the sake of your own.

Just my 2 cents.

73,
KC9SWV - Morgen
President, TARA

On Tue, Jul 11, 2017 at 12:38 PM, George J Molnar  wrote:

> I like the feature. Suggestions for its “final”condition include -
>
> 1) May be enabled or disabled by operator
> 2) Apply equally to all modes
> 3) Work only with standard sequence messages
> 4) Require a minimum of one user intervention per contact (logging/reset
> sequence, after 73)
> 5) Support complex callsigns without additional steps
> 6) Define behaviors for multiple caller situations, preferably with user
> definable criteria (weak or strong sign, new DXCC, not worked before, etc.)
>
> Probably a big bite at first, but could be a great help overall.
>
> 73
>
>
> George J Molnar, KF2T
> Nevada, USA
>
>
> On Jul 11, 2017, at 9:26 AM, James Shaver (N2ADV) 
> wrote:
>
> I think the fact that it's user selectable is important and I agree it
> should be kept because the turnaround time to respond to an inbound message
> is very short (this is especially noticeable for those of us that do 99% of
> our operating remotely where internet connections may prevent successful
> replies in such a short amount of time).  Purists can certainly choose to
> not enable the feature but I think it's a nice feature.  I also agree with
> disabling the TX once the user hits the "73" in the cycle - user
> intervention is still required which is still important in my opinion.
>
> My 2 cents. :)
>
> 73,
>
> Jim S.
> N2ADV
>
> On Jul 11, 2017, at 12:07 PM, Black Michael via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> I did send the patch that fixes that...did you see it?
>
> de Mike W9MDB
>
>
> --
> *From:* Erik - 
> *To:* WSJT software development 
> *Sent:* Tuesday, July 11, 2017 11:04 AM
> *Subject:* Re: [wsjt-devel] FT8 and "Call 1st"
>
>
> "We are interested in feedback from users on the question of partial QSO
> automation.  Should "Call 1st" be changed or removed?"
>
> I like it as it is. One thing though, it gets broken by callsigns such as
> EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. Not a
> big deal since reciprocal calls such as this one are not too common. My
> over-riding request is to not remove "Call 1st".
>
> Erik EI4KF.
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> 

Re: [wsjt-devel] FT8 and "Call 1st"

[Gary McDuffie]

> On Jul 11, 2017, at 9:42 AM, Joe Taylor  wrote:
> 
> We are interested in feedback from users on the question of partial QSO 
> automation.  Should "Call 1st" be changed or removed?

I think the way you’ve done it is just right.  You are giving the operator the 
OPTION of using it or not.  For my own use, I’ll probably leave it off, but I 
know it will help many of the people to hook the caller on the first try.  1.5 
seconds isn’t much time to make up your mind and move to the mouse, not to 
mention actual turnover time of the radios involved.  Of course inaccurate 
clock settings will exacerbate the situation.  The other issue that it allows 
is the operator’s choice of whether he wants to work the calling station or not.

I’d still really like to see auto-progression added to JT65.  Many of us 
multi-task while operating.  Many times, I’ve looked up and realized I fell 
behind with sequencing and the poor guy is sitting there repeating the last 
sequence over and over when I did receive it the 1st or 2nd time.  Auto-QSO?  
No!  Auto-progression?  Yes!

Thanks for all of the wonderful work you and the many others have done on X.

Gary - AG0N


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt-devel Digest, Vol 41, Issue 158

[David Birnbaum]

After the announcement I did an update/upgrade and now have the option to
compile the 1.8 branch as well.  I compiled rc1 and version matches the rc1
on sourceforge.

I've been running it for a few hours.  Switch between FT8 and JTy5/9 works
fine including frequency switch.

In FT8 mode I find that I can click a bit late and even if transmission
starts 2 or 3 seconds into the cycle I still get contacts.  Just an
incentive to stay focused.  I'm not sure it's me, but it seems that the db
readings are lower than the earlier version of FT8 although I don;t see any
difference in signal so I guess it's just re-calibration of the dB scale.

An amazing effort by all involved to roll out a newly invented mode so fast.

Thank you all

dave
k2lyv

On Tue, Jul 11, 2017 at 1:24 PM, 
wrote:

> Send wsjt-devel mailing list submissions to
> wsjt-devel@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> or, via email, send a message with subject or body 'help' to
> wsjt-devel-requ...@lists.sourceforge.net
>
> You can reach the person managing the list at
> wsjt-devel-ow...@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of wsjt-devel digest..."
>
>
> Today's Topics:
>
>1. Re: wsjt-x v1.8.0-rc1 on raspbian = success. (ki7mt)
>2. Re: Fwd: Re: r7848 TX starts within cycle (Joe Taylor)
>3. Re: Distribution (Richard Stanley)
>4. Re: Distribution (Laurie, VK3AMA)
>
>
> --
>
> Message: 1
> Date: Tue, 11 Jul 2017 10:46:29 -0600
> From: "ki7mt" 
> To: "'WSJT software development'" 
> Subject: Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.
> Message-ID: <081301d2fa65$401b0840$c05118c0$@yahoo.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Bill,
>
>
>
> Yes, all the builds Launchpad are complete. I had trouble with Zesty and
> Clang, but believe it?s resolved now. Here?s
>
> The info:
>
>
>
>
>
> Current Version: WSJT-X 1.8.0 RC1
>
> Ubuntu Distro?s: Trusty, Xenial, Yakkety, Zesty
>
> Supported Arach: i386, amd64, armv7, armv8, ppc64el
>
>
>
>
>
> Incidentally, for folks that want to use Gdebi to install with, you can
> download the prebuilt .deb directly from Launchpad for your Distro / Arch,
> and install manually. There is no hard and fast rule to add the PPA to
> one?s sources list, it just makes it easier for updates is all. Just browse
> to the packages at:
>
>
>
> https://launchpad.net/~ki7mt/+archive/ubuntu/wsjtx-next/+packages
>
>
>
> Pick your Distro / Arch, and download it. The following is an example for
> Trusty. The .deb file are toward the bottom of the page. The packages are
> all Launchpad Built:
>
>
>
> https://launchpad.net/~ki7mt/+archive/ubuntu/wsjtx-next/+packages
>
>
>
> Using Gdebi will help with dependencies. If you use the PPA, then apt-get
> -f is the preferred option unless your on a Native Ubuntu system.
>
>
>
> 73?s
>
> Greg, KI7MT
>
>
>
>
>
> From: Bill Somerville [mailto:g4...@classdesign.com]
> Sent: Tuesday, July 11, 2017 7:18 AM
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.
>
>
>
> On 11/07/2017 14:13, Richard Lamont wrote:
>
> On 11/07/17 13:44, Bill Somerville wrote:
>
>
> I would appreciate reports of how well the Debian installer we have
> provided with the WSJT-X v1.8.0 RC1 release works. As with the other
> early release kits you will have to install dependencies manually and
> use rpm/yum/dnf to install them. In your case you will probably already
> have all the required dependencies in place.
>
> I installed the binary rc1 (r7847) from sourceforge before Joe's
> announcement of the binaries at physics.princeton.edu. Are they the same?
>
> I installed it on Ubuntu 16.04 without difficulty, although as one might
> expect gdebi recommended an earlier more stable version, probably
> because I still have Greg's PPA in /etc/apt/sources.list.d/
>
> HI Richard,
>
> yes they are the same packages.
>
> Greg is probably updating on Launchpad right now, it may even be done, so
> his cross version packages will be available very soon.
>
> I'm not sure if you are referring to an Intel/AMD machine or Raspberry Pi
> ARM installers, my request to Nik was about Raspbian.
>
> 73
> Bill
> G4WJS.
>
> -- next part --
> An HTML attachment was scrubbed...
>
> --
>
> Message: 2
> Date: Tue, 11 Jul 2017 13:04:42 -0400
> From: Joe Taylor 
> To: WSJT software development 
> Subject: Re: [wsjt-devel] Fwd: Re: r7848 TX starts within cycle
> Message-ID: 
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hi 

Re: [wsjt-devel] Fwd: Re: r7848 TX starts within cycle

[Wolfgang]

Hello Joe,

Tuesday, July 11, 2017, 7:04:42 PM, you wrote:

> I think you are objecting to the ability to start a transmission after
> the nominl start time, thus ensuring that only some fraction of the 
> normal number of symbols will be sent.

> If I have understood you correctly, I  do not understand why you would
> object to this behavior.  All WSJT-X modes except ISCAT include 
> sufficient forward error correction that even if (say) 1/3 of a 
> transmission is missing, decoding may still succeed.

agree, the forward error correction will do it's best.

Due to the short turn-over of 15 seconds, one has to carefully check
when to start CQ, otherwise only a part of the message is sent out, 
with the hope it gets decoded by someone. With JT65 one got a full 
minute to consider to start with even or odd.

A more elegant solution would be, the transmission starts at the
beginning of the selected periode.

But, as Mike, W9MDB, once said: it's '...a wee case of semantics'

73 de Wolfgang
OE1MWW

--
Amateur radio is the most expensive type of free-of-charge communication!
Amateurfunk ist die teuerste Art der kostenlosen Kommunikation!


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Distribution

[Richard Stanley via wsjt-devel]

Because I saw somewhere that you would prefer for people to only run the 
official ones for now I downloaded from Joes link and it is 7843 so should I 
stop using it and build from JTSDK as normal ?


Joe has released it so I fail to understand how it could be an unofficial 
source ?


I am out so will leave Joes version r7843 running but can always close it if 
prefered and make one from JTSDK


Regards Richard G7OED

-Original Message- 
From: Bill Somerville

Sent: Tuesday, July 11, 2017 1:07 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Distribution

On 11/07/2017 12:35, James Shaver (N2ADV) wrote:
Please be advised that there are some enterprising souls sharing links 
directly to Sourceforge distributing the Release Candidate files all over 
social media. Seeing posts crop up everywhere.



Hi James,

I'm afraid it is worse than that, looking at the pskreporter stats I see
that the most common version is a revision that is not the one that will
be the RC1 release. I guess as usual some bright spark thinks they can
pretend to be beating the system by building and distributing a kit
before the official announcement.

Fair notice to anyone who has downloaded WSJT-X v1.8.0-rc1 from an
unofficial source, r7843 is not going to be the official release
revision and whoever supplied it to you is not complying with our wishes
to not distribute unofficial binary installers of WSJT-X. There appear
to be at least 138 of you out there, perhaps we should ask Philip to
name and shame!

73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel 



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Fwd: Re: r7848 TX starts within cycle

[Joe Taylor]

Hi Wolfgang,

On 7/11/2017 12:22 PM, Wolfgang OE1MWW wrote:



If I have "TX even/1st" unchecked and I "Enable TX",
the transmission starts with CQ, disregarding the 15 sec. cycle time.


I checked that again, this can happen twice a minute, depends on the
setting and the activation of "Enable TX".

Nevertheless, I think in terms of a 'clean protocol', this should not
be possible, to start transmission during the cycle. It will send out
an un-complete message, because at the end of the cyle the TX goes off
again.

73 de Wolfgang
OE1MWW


I think you are objecting to the ability to start a transmission after 
the nominl start time, thus ensuring that only some fraction of the 
normal number of symbols will be sent.


If I have understood you correctly, I  do not understand why you would 
object to this behavior.  All WSJT-X modes except ISCAT include 
sufficient forward error correction that even if (say) 1/3 of a 
transmission is missing, decoding may still succeed.


-- 73, Joe, K1JT

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

[ki7mt via wsjt-devel]

Hi Bill,

 

Yes, all the builds Launchpad are complete. I had trouble with Zesty and Clang, 
but believe it’s resolved now. Here’s

The info:

 

 

Current Version: WSJT-X 1.8.0 RC1

Ubuntu Distro’s: Trusty, Xenial, Yakkety, Zesty

Supported Arach: i386, amd64, armv7, armv8, ppc64el

 

 

Incidentally, for folks that want to use Gdebi to install with, you can 
download the prebuilt .deb directly from Launchpad for your Distro / Arch, and 
install manually. There is no hard and fast rule to add the PPA to one’s 
sources list, it just makes it easier for updates is all. Just browse to the 
packages at:

 

https://launchpad.net/~ki7mt/+archive/ubuntu/wsjtx-next/+packages

 

Pick your Distro / Arch, and download it. The following is an example for 
Trusty. The .deb file are toward the bottom of the page. The packages are all 
Launchpad Built:

 

https://launchpad.net/~ki7mt/+archive/ubuntu/wsjtx-next/+packages

 

Using Gdebi will help with dependencies. If you use the PPA, then apt-get -f is 
the preferred option unless your on a Native Ubuntu system.

 

73’s

Greg, KI7MT

 

 

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Tuesday, July 11, 2017 7:18 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

 

On 11/07/2017 14:13, Richard Lamont wrote:

On 11/07/17 13:44, Bill Somerville wrote:
 

I would appreciate reports of how well the Debian installer we have
provided with the WSJT-X v1.8.0 RC1 release works. As with the other
early release kits you will have to install dependencies manually and
use rpm/yum/dnf to install them. In your case you will probably already
have all the required dependencies in place.

I installed the binary rc1 (r7847) from sourceforge before Joe's
announcement of the binaries at physics.princeton.edu. Are they the same?
 
I installed it on Ubuntu 16.04 without difficulty, although as one might
expect gdebi recommended an earlier more stable version, probably
because I still have Greg's PPA in /etc/apt/sources.list.d/

HI Richard,

yes they are the same packages.

Greg is probably updating on Launchpad right now, it may even be done, so his 
cross version packages will be available very soon.

I'm not sure if you are referring to an Intel/AMD machine or Raspberry Pi ARM 
installers, my request to Nik was about Raspbian.

73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[George J Molnar]

I like the feature. Suggestions for its “final”condition include -

1) May be enabled or disabled by operator 
2) Apply equally to all modes
3) Work only with standard sequence messages
4) Require a minimum of one user intervention per contact (logging/reset 
sequence, after 73)
5) Support complex callsigns without additional steps
6) Define behaviors for multiple caller situations, preferably with user 
definable criteria (weak or strong sign, new DXCC, not worked before, etc.)

Probably a big bite at first, but could be a great help overall.

73


George J Molnar, KF2T 
Nevada, USA


> On Jul 11, 2017, at 9:26 AM, James Shaver (N2ADV)  
> wrote:
> 
> I think the fact that it's user selectable is important and I agree it should 
> be kept because the turnaround time to respond to an inbound message is very 
> short (this is especially noticeable for those of us that do 99% of our 
> operating remotely where internet connections may prevent successful replies 
> in such a short amount of time).  Purists can certainly choose to not enable 
> the feature but I think it's a nice feature.  I also agree with disabling the 
> TX once the user hits the "73" in the cycle - user intervention is still 
> required which is still important in my opinion.  
> 
> My 2 cents. :)
> 
> 73,
> 
> Jim S. 
> N2ADV
> 
>> On Jul 11, 2017, at 12:07 PM, Black Michael via wsjt-devel 
>>  wrote:
>> 
>> I did send the patch that fixes that...did you see it?
>> 
>> de Mike W9MDB
>> 
>> 
>> From: Erik - 
>> To: WSJT software development  
>> Sent: Tuesday, July 11, 2017 11:04 AM
>> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
>> 
>> 
>> "We are interested in feedback from users on the question of partial QSO 
>> automation.  Should "Call 1st" be changed or removed?"
>> 
>> I like it as it is. One thing though, it gets broken by callsigns such as 
>> EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. Not a 
>> big deal since reciprocal calls such as this one are not too common. My 
>> over-riding request is to not remove "Call 1st".
>> 
>> Erik EI4KF.
>> 
>> 
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> 
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Erik -]

I wouldn’t know what to do with a patch if it came up and bit me on the . 
Gratified though to know that it is in the pipeline for a future release.

Thank you as always.

Erik EI4KF.


From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: 11 July 2017 16:08
To: WSJT software development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] FT8 and "Call 1st"

I did send the patch that fixes that...did you see it?

de Mike W9MDB



From: Erik - >
To: WSJT software development 
>
Sent: Tuesday, July 11, 2017 11:04 AM
Subject: Re: [wsjt-devel] FT8 and "Call 1st"


"We are interested in feedback from users on the question of partial QSO 
automation.  Should "Call 1st" be changed or removed?"

I like it as it is. One thing though, it gets broken by callsigns such as 
EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. Not a big 
deal since reciprocal calls such as this one are not too common. My over-riding 
request is to not remove "Call 1st".

Erik EI4KF.



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[James Shaver (N2ADV)]

I think the fact that it's user selectable is important and I agree it should 
be kept because the turnaround time to respond to an inbound message is very 
short (this is especially noticeable for those of us that do 99% of our 
operating remotely where internet connections may prevent successful replies in 
such a short amount of time).  Purists can certainly choose to not enable the 
feature but I think it's a nice feature.  I also agree with disabling the TX 
once the user hits the "73" in the cycle - user intervention is still required 
which is still important in my opinion.  

My 2 cents. :)

73,

Jim S. 
N2ADV

> On Jul 11, 2017, at 12:07 PM, Black Michael via wsjt-devel 
>  wrote:
> 
> I did send the patch that fixes that...did you see it?
> 
> de Mike W9MDB
> 
> 
> From: Erik - 
> To: WSJT software development  
> Sent: Tuesday, July 11, 2017 11:04 AM
> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
> 
> 
> "We are interested in feedback from users on the question of partial QSO 
> automation.  Should "Call 1st" be changed or removed?"
> 
> I like it as it is. One thing though, it gets broken by callsigns such as 
> EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. Not a big 
> deal since reciprocal calls such as this one are not too common. My 
> over-riding request is to not remove "Call 1st".
> 
> Erik EI4KF.
> 
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Richard Lamont]

On 11/07/17 16:42, Joe Taylor wrote:

> We are interested in feedback from users on the question of partial QSO
> automation.  Should "Call 1st" be changed or removed?

I think "Call 1st" is necessary, because there isn't nearly enough time
for an operator to decide manually. As long as TX Enable is turned off
at the end of the QSO, the machine cannot work a 'run' on its own.
That's the red line that should not be crossed. If it was, the entire 2
kHz segment would be full of stations calling CQ DX 24/7 while their
owners were doing something else.

> One more point: FT8 signals occupy the frequency/time plane more
> "densely" than JT65.  For this reason, even when we have implemented
> signal subtraction and multi-pass decoding, overlapping signals will be
> less likely to decode than is the case with JT65.  You may soon discover
> that it often pays to respond to a CQ "off frequency" by 60 Hz or more.
> We might consider offering a tool to make this easier to do.

I've tried doing this, using the F11 and F12 keys but found it
impossibly awkward to use.

It would be useful to be able to move the Tx frequency quickly to the
next regularly-spaced 60 Hz step up or down, perhaps by using Page Up /
Page Down as a keyboard shortcut. (I'm not sure quite how this might
interact with Lock Tx=Rx.)

73,
Richard G4DYA

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Dan Malcolm]

Thanks Joe.  Since you're looking for opinions, hers's mine:
1. I like FT8.  I like the fast exchange.  I also like the automation so
far.  I agree that I would not want a "QSO machine".  If that's what I
wanted, I'd just turn off my mind and sit in front of the TV all day.
However I like the degree of automation you have at this point.  That gives
the operator a leg up in this fast mode, but it also allows him choice in
how he wants to operate.  Completely manual is still a choice.  Those of us
who are "aged" to perfection, do not have the reflexes that the "non-aged"
community enjoys, so the leg up is appreciated.  In short, I think the
current level of automation, but no more, is the way to go.
2. I like "Call 1st" but would also like "Weak".  That would be good for
encouraging low power and for capturing DX on a less than perfect
propagation day. 
3. The 60Hz shift and perhaps a choice of +/- would be nice for a trial. I
know I often stay out of the JT65 pileup because it's frustrating try to
have a QSO adjacent to a stronger signal than my QSO partner.  I am often
amazed the QSO's happen at all.  That's when I go to JT9.  I think for FT8
it would have to be tried, before viability can be assessed.  That 60Hz
shift could inadvertently put you right on top of someone else.

Thanks again Joe.

Dan - K4SHQ



-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Tuesday, July 11, 2017 10:42 AM
To: WSJT software development 
Subject: [wsjt-devel] FT8 and "Call 1st"

Hi all,

WSJT-X v1.8.0-rc1 includes an optional feature that is a significant
departure from all previous WSJT-related software.

When you call CQ in FT8 mode with both "Auto Seq" and "Call 1st" 
checked, the program automatically selects the first decoded response to
your CQ and starts a QSO with the selected station.  The effect is the same
as if you had double-clicked on the caller's message.  Subsequent
transmissions will then continue automatically through the standard QSO
sequence.

When the contact is complete the CQ message (Tx6 on Tab 1) is selected but
"Tx Enable" is turned OFF.  This choice is intentional.  We want WSJT-X to
be a tool for assisting contacts between human operators, not an "Automatic
QSO Machine".

For a mode with 15-second T/R sequences and very little time for selecting
reply messages, there are obvious merits of the approach we have tentatively
adopted.  However, there are also some obvious consequences that might not
be considered desirable.  Do we want a computer algorithm to take part in
choosing our QSO partners?

It seems like a good idea to have some public discussion on whether "Call
1st" already goes too far in the direction of QSO automation.

Some of you noticed that a "Weak" box appeared briefly beside "Call 1st" 
(but was not yet implemented).  The idea was that when two or more replies
were received to one's CQ, this option would select the one with lower S/N
-- potentially encouraging people to keep their power turned down, as
appropriate for conditions.

We are interested in feedback from users on the question of partial QSO
automation.  Should "Call 1st" be changed or removed?

One more point: FT8 signals occupy the frequency/time plane more "densely"
than JT65.  For this reason, even when we have implemented signal
subtraction and multi-pass decoding, overlapping signals will be less likely
to decode than is the case with JT65.  You may soon discover that it often
pays to respond to a CQ "off frequency" by 60 Hz or more. 
We might consider offering a tool to make this easier to do.

-- Joe, K1JT


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Fwd: Re: r7848 TX starts within cycle

[Wolfgang]

>> If I have "TX even/1st" unchecked and I "Enable TX",
>> the transmission starts with CQ, disregarding the 15 sec. cycle time.

I checked that again, this can happen twice a minute, depends on the
setting and the activation of "Enable TX".

Nevertheless, I think in terms of a 'clean protocol', this should not
be possible, to start transmission during the cycle. It will send out
an un-complete message, because at the end of the cyle the TX goes off
again.

73 de Wolfgang
OE1MWW



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Black Michael via wsjt-devel]

I did send the patch that fixes that...did you see it?
de Mike W9MDB

  From: Erik - 
 To: WSJT software development  
 Sent: Tuesday, July 11, 2017 11:04 AM
 Subject: Re: [wsjt-devel] FT8 and "Call 1st"
   

"We are interested in feedback from users on the question of partial QSO 
automation.  Should "Call 1st" be changed or removed?"

I like it as it is. One thing though, it gets broken by callsigns such as 
EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. Not a big 
deal since reciprocal calls such as this one are not too common. My over-riding 
request is to not remove "Call 1st".

Erik EI4KF.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


   --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Gordon Higgins]

keep fist call. ok on enable tx  as u say it would be like sim  31  give up
go out come back see hue u worked hi

On 11 July 2017 at 17:02, Erik -  wrote:

>
> "We are interested in feedback from users on the question of partial QSO
> automation.  Should "Call 1st" be changed or removed?"
>
> I like it as it is. One thing though, it gets broken by callsigns such as
> EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. Not a
> big deal since reciprocal calls such as this one are not too common. My
> over-riding request is to not remove "Call 1st".
>
> Erik EI4KF.
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Dave 'Doc' Corio]

Joe, first, thanks for the intense amount of work you and the 
others have put into this project! The results keep getting better and 
better!


You may recall years back a program named "Lan-Link. It was 
designed for HF/VHF packet and was fairly widespread using PK-232 and 
other TNCs. That application allowed the user to carry on up to TEN QSOs 
at the same time, as well as having a "robot" mode that would decode and 
respond to key words in the incoming signals.


For example, you would call CQ and AB1CDE would respond. You could 
give AB1CDE his signal report and the "usual" info. When AB1CDE 
returned, if he were to say "rig here is" the program could respond 
with the canned message "rig here is...". If he said "I work 
at..." the program could access the specific macro that included your 
employment information.


As far as I recall this was perhaps the first software that allowed 
a completely robotic QSO based on  input received from the other 
station. It worked, to a limited degree, as long as the QSO station used 
the right words/phrases!


That said, it was fun setting it up and watching it run, but I have 
no desire to see it again! Macros have their place in the world, and 
I've used them for years. They can and do make tedious contest exchanges 
MUCH easier. They also make it much easier to have a rag-chew. You can 
send the "rig" macro while you type ahead free text to follow it.


My personal desire is that the current state of the program remain 
as it is, or perhaps a "Contest Edition" or option be added. My main 
reason for this is that when QSOs become too easy, it diminishes the 
value of the QSO. The program now terminates transmission after each 
"automatic" QSO. Adding functionality that would allow the program to 
run completely on its' own would remove any challenge left in this mode.


My opinion only. YMMV

Tnx es 73
Dave - KB3MOW

On 7/11/2017 11:42 AM, Joe Taylor wrote:

Hi all,

WSJT-X v1.8.0-rc1 includes an optional feature that is a significant 
departure from all previous WSJT-related software.


When you call CQ in FT8 mode with both "Auto Seq" and "Call 1st" 
checked, the program automatically selects the first decoded response 
to your CQ and starts a QSO with the selected station. The effect is 
the same as if you had double-clicked on the caller's message.  
Subsequent transmissions will then continue automatically through the 
standard QSO sequence.


When the contact is complete the CQ message (Tx6 on Tab 1) is selected 
but "Tx Enable" is turned OFF.  This choice is intentional.  We want 
WSJT-X to be a tool for assisting contacts between human operators, 
not an "Automatic QSO Machine".


For a mode with 15-second T/R sequences and very little time for 
selecting reply messages, there are obvious merits of the approach we 
have tentatively adopted.  However, there are also some obvious 
consequences that might not be considered desirable.  Do we want a 
computer algorithm to take part in choosing our QSO partners?


It seems like a good idea to have some public discussion on whether 
"Call 1st" already goes too far in the direction of QSO automation.


Some of you noticed that a "Weak" box appeared briefly beside "Call 
1st" (but was not yet implemented).  The idea was that when two or 
more replies were received to one's CQ, this option would select the 
one with lower S/N -- potentially encouraging people to keep their 
power turned down, as appropriate for conditions.


We are interested in feedback from users on the question of partial 
QSO automation.  Should "Call 1st" be changed or removed?


One more point: FT8 signals occupy the frequency/time plane more 
"densely" than JT65.  For this reason, even when we have implemented 
signal subtraction and multi-pass decoding, overlapping signals will 
be less likely to decode than is the case with JT65.  You may soon 
discover that it often pays to respond to a CQ "off frequency" by 60 
Hz or more. We might consider offering a tool to make this easier to do.


-- Joe, K1JT

-- 


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel





---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Erik -]

"We are interested in feedback from users on the question of partial QSO 
automation.  Should "Call 1st" be changed or removed?"

I like it as it is. One thing though, it gets broken by callsigns such as 
EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. Not a big 
deal since reciprocal calls such as this one are not too common. My over-riding 
request is to not remove "Call 1st".

Erik EI4KF.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] FT8 and "Call 1st"

[Joe Taylor]

Hi all,

WSJT-X v1.8.0-rc1 includes an optional feature that is a significant 
departure from all previous WSJT-related software.


When you call CQ in FT8 mode with both "Auto Seq" and "Call 1st" 
checked, the program automatically selects the first decoded response to 
your CQ and starts a QSO with the selected station.  The effect is the 
same as if you had double-clicked on the caller's message.  Subsequent 
transmissions will then continue automatically through the standard QSO 
sequence.


When the contact is complete the CQ message (Tx6 on Tab 1) is selected 
but "Tx Enable" is turned OFF.  This choice is intentional.  We want 
WSJT-X to be a tool for assisting contacts between human operators, not 
an "Automatic QSO Machine".


For a mode with 15-second T/R sequences and very little time for 
selecting reply messages, there are obvious merits of the approach we 
have tentatively adopted.  However, there are also some obvious 
consequences that might not be considered desirable.  Do we want a 
computer algorithm to take part in choosing our QSO partners?


It seems like a good idea to have some public discussion on whether 
"Call 1st" already goes too far in the direction of QSO automation.


Some of you noticed that a "Weak" box appeared briefly beside "Call 1st" 
(but was not yet implemented).  The idea was that when two or more 
replies were received to one's CQ, this option would select the one with 
lower S/N -- potentially encouraging people to keep their power turned 
down, as appropriate for conditions.


We are interested in feedback from users on the question of partial QSO 
automation.  Should "Call 1st" be changed or removed?


One more point: FT8 signals occupy the frequency/time plane more 
"densely" than JT65.  For this reason, even when we have implemented 
signal subtraction and multi-pass decoding, overlapping signals will be 
less likely to decode than is the case with JT65.  You may soon discover 
that it often pays to respond to a CQ "off frequency" by 60 Hz or more. 
We might consider offering a tool to make this easier to do.


-- Joe, K1JT

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJTX RC1

[Seb]

Ok I must have missed that.  Calling CQ automatically is nothing new.  This is 
done with keyers for both CW/SSB.  Of course on CW/SSB, the operator has to 
‘manually’ acknowledge a reply.  Thanks for the clarification.

73 de Sebastian, W4AS




> On Jul 11, 2017, at 11:21 AM, Steve Huston  wrote:
> 
> On Tue, Jul 11, 2017 at 11:09 AM, Seb  wrote:
>> I am seeing the same problem (at least with FT8), Enable Tx goes out after
>> logging a QSO.  I do NOT have Disable Tx after sending 73 enabled.
> 
> I believe this was the intended behavior; from an email yesterday:
> 
> On Mon, Jul 10, 2017 at 9:52 AM, Joe Taylor  wrote:
>> 3. When your QSO finishes, another CQ transmission should be queued up, but
>> "Enable Tx" will be off.  To continue running a frequency you must click
>> "Enable Tx" again.
> 
> Otherwise your machine could theoretically just keep replying as long
> as someone responds to a CQ at least once every 6 minutes.  While that
> might be nice for WAS/DXCC...
> 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJTX RC1

[Steve Huston]

On Tue, Jul 11, 2017 at 11:09 AM, Seb  wrote:
> I am seeing the same problem (at least with FT8), Enable Tx goes out after
> logging a QSO.  I do NOT have Disable Tx after sending 73 enabled.

I believe this was the intended behavior; from an email yesterday:

On Mon, Jul 10, 2017 at 9:52 AM, Joe Taylor  wrote:
> 3. When your QSO finishes, another CQ transmission should be queued up, but
> "Enable Tx" will be off.  To continue running a frequency you must click
> "Enable Tx" again.

Otherwise your machine could theoretically just keep replying as long
as someone responds to a CQ at least once every 6 minutes.  While that
might be nice for WAS/DXCC...

-- 
Steve Huston - W2SRH - Unix Sysadmin, PICSciE/CSES & Astrophysical Sci
  Princeton University  |ICBM Address: 40.346344   -74.652242
345 Lewis Library   |"On my ship, the Rocinante, wheeling through
  Princeton, NJ   08544 | the galaxies; headed for the heart of Cygnus,
(267) 793-0852  | headlong into mystery."  -Rush, 'Cygnus X-1'

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r7848

[Wolfgang]

Title: Re: [wsjt-devel] r7848



If I have "TX even/1st" unchecked and I "Enable TX",
the transmission starts with CQ, disregarding the 15 sec. cycle time.


73 de Wolfgang
OE1MWW

--
Amateur radio is the most expensive type of free-of-charge communication!
Amateurfunk ist die teuerste Art der kostenlosen Kommunikation!


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJTX RC1

[Seb]

I am seeing the same problem (at least with FT8), Enable Tx goes out after 
logging a QSO.  I do NOT have Disable Tx after sending 73 enabled.

v1.8.0-rc1 on Windows 10 64-bit.

73 de Sebastian, W4AS




> On Jul 11, 2017, at 6:13 AM, Gordon Higgins  wrote:
> 
> HI all using ft8 v1.8.0-rc1
>  when i call cq  with call 1st ticked workes fine call sequence as exppeted 
> but when i have logged call, enable tx goes out @ i have to re  enable to 
> call cq again, i do not have  disable tx after sending 73 ticked ??
> 
> 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian AND armbian = success.

[Bill Somerville]

On 11/07/2017 14:45, Nikiforos Kontopoulos wrote:


Actually I’ve  just finished installing the deb file on my …..Armbian 
powered OrangePi Plus 2e (xfce) as I fortold right after the Raspbian 
version.


As you have already guessed there was some messages about unmet 
dependencies concerning libqt5*


Apt-get install -f install seemed to fix all dependency issues and 
then dpkg -I wsjt_1.8.0-rc1_armhf.deb installed everything ok.


The wsjt and wsjtx are then found in the Multimedia group of

I have some photos including armbian and raspbian versions as proof of 
concept.


https://www.dropbox.com/preview/Public/7863403151886675780-account_id%3D1.jpg?role=personal

https://www.dropbox.com/preview/Public/2671256672190357003-account_id%3D1.jpg?role=personal

https://www.dropbox.com/preview/Public/4609045080612754347-account_id%3D1.jpg?role=personal

Therefore I believe that the .deb installation file will work ufb also 
for Raspbian if it works for Armbian. But still the user will have to 
resolve the issues with dependencies.



Hi Nik,

that's good news. I am also interested if the performance i.e. the speed 
of the software, is any better using the official deb file?


73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian AND armbian = success.

[Nikiforos Kontopoulos]

Hello dr Bill and many tks for your wonderful work!

If only we lived a bit closer to lend you some of my hw for further testing.

Actually I’ve  just finished installing the deb file on my …..Armbian powered 
OrangePi Plus 2e (xfce) as I fortold right after the Raspbian version.

As you have already guessed there was some messages about unmet dependencies 
concerning libqt5*

Apt-get install -f install seemed to fix all dependency issues and then dpkg -I 
wsjt_1.8.0-rc1_armhf.deb installed everything ok.

The wsjt and wsjtx are then found in the Multimedia group of

I have some photos including armbian and raspbian versions as proof of concept.

https://www.dropbox.com/preview/Public/7863403151886675780-account_id%3D1.jpg?role=personal

https://www.dropbox.com/preview/Public/2671256672190357003-account_id%3D1.jpg?role=personal

https://www.dropbox.com/preview/Public/4609045080612754347-account_id%3D1.jpg?role=personal


Therefore I believe that the .deb installation file will work ufb also for 
Raspbian if it works for Armbian. But still the user will have to resolve the 
issues with dependencies.


Best 73 de sv1eex - Nik


Sent from Mail for Windows 10


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Auto-sequence (r7848)

[Black Michael via wsjt-devel]

A small change to get that to work.
Index: 
mainwindow.cpp===---
 mainwindow.cpp      (revision 7849)+++ mainwindow.cpp      (working copy)@@ 
-2782,7 +2782,7 @@ void MainWindow::FT8_AutoSeq(QString message) {   int 
i1=message.indexOf(m_baseCall);-  int i2=message.indexOf(m_hisCall);+  int 
i2=message.indexOf(Radio::base_callsign(m_hisCall));   if(i1>10 and i2>i1+3) {  
   if ((message.indexOf (" 73") < 0 || m_ntx != 6)) {       
if(ui->cbAutoSeq->isChecked() and !m_sentFirst73) processMessage 
(message,43,false);
 de Mike W9MDB

  From: Erik - 
 To: WSJT software development  
 Sent: Tuesday, July 11, 2017 2:59 AM
 Subject: [wsjt-devel] Auto-sequence (r7848)
   
 EA8/G8BCG called CQ and I answered: EA8/G8BCG EI4KF    G8BCG returned a 
report (I know why G8BCG and not EA8/G8BCG)    Auto-sequence, though enabled, 
did not function and the entire contact had to be made manually. Of course that 
isn’t a problem but I wonder if that is the expected behaviour. It seemed that 
the change of the callsign broke auto-sequence.     Erik EI4KF.       
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


   --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

[Richard Lamont]

On 11/07/17 14:18, Bill Somerville wrote:
> On 11/07/2017 14:13, Richard Lamont wrote:
>> On 11/07/17 13:44, Bill Somerville wrote:
>>
>>> I would appreciate reports of how well the Debian installer we have
>>> provided with the WSJT-X v1.8.0 RC1 release works. As with the other
>>> early release kits you will have to install dependencies manually and
>>> use rpm/yum/dnf to install them. In your case you will probably already
>>> have all the required dependencies in place.
>> I installed the binary rc1 (r7847) from sourceforge before Joe's
>> announcement of the binaries at physics.princeton.edu. Are they the same?
>>
>> I installed it on Ubuntu 16.04 without difficulty, although as one might
>> expect gdebi recommended an earlier more stable version, probably
>> because I still have Greg's PPA in/etc/apt/sources.list.d/
> 
> HI Richard,
> 
> yes they are the same packages.
> 
> Greg is probably updating on Launchpad right now, it may even be done,
> so his cross version packages will be available very soon.
> 
> I'm not sure if you are referring to an Intel/AMD machine or Raspberry
> Pi ARM installers, my request to Nik was about Raspbian.

Thanks Bill. Intel/amd64 in my case.

73,
Richard G4DYA

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

[Bill Somerville]

On 11/07/2017 14:13, Richard Lamont wrote:

On 11/07/17 13:44, Bill Somerville wrote:


I would appreciate reports of how well the Debian installer we have
provided with the WSJT-X v1.8.0 RC1 release works. As with the other
early release kits you will have to install dependencies manually and
use rpm/yum/dnf to install them. In your case you will probably already
have all the required dependencies in place.

I installed the binary rc1 (r7847) from sourceforge before Joe's
announcement of the binaries at physics.princeton.edu. Are they the same?

I installed it on Ubuntu 16.04 without difficulty, although as one might
expect gdebi recommended an earlier more stable version, probably
because I still have Greg's PPA in/etc/apt/sources.list.d/


HI Richard,

yes they are the same packages.

Greg is probably updating on Launchpad right now, it may even be done, 
so his cross version packages will be available very soon.


I'm not sure if you are referring to an Intel/AMD machine or Raspberry 
Pi ARM installers, my request to Nik was about Raspbian.


73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

[Richard Lamont]

On 11/07/17 13:44, Bill Somerville wrote:

> I would appreciate reports of how well the Debian installer we have
> provided with the WSJT-X v1.8.0 RC1 release works. As with the other
> early release kits you will have to install dependencies manually and
> use rpm/yum/dnf to install them. In your case you will probably already
> have all the required dependencies in place.

I installed the binary rc1 (r7847) from sourceforge before Joe's
announcement of the binaries at physics.princeton.edu. Are they the same?

I installed it on Ubuntu 16.04 without difficulty, although as one might
expect gdebi recommended an earlier more stable version, probably
because I still have Greg's PPA in /etc/apt/sources.list.d/

73,
Richard G4DYA

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

[Bill Somerville]

On 11/07/2017 13:36, Nikiforos Kontopoulos wrote:


Finished compiling and tested wsjt-x v1.8.0-rc1 on my raspberry pi 3 
with Raspbian.


20m Jt65a + Ft8 work like a charm. Had some qsos already.

Will also try to compile it on armbian for OrangePi plus 2e.


Hi Nik,

glad to here it is working for you.

I would appreciate reports of how well the Debian installer we have 
provided with the WSJT-X v1.8.0 RC1 release works. As with the other 
early release kits you will have to install dependencies manually and 
use rpm/yum/dnf to install them. In your case you will probably already 
have all the required dependencies in place.


I have tried to optimize the WSJT-X build for performance on Raspberry 
Pi but I do not have a system I can test extensively on. If you can 
install it and compare performance with your own builds I would like to 
know how it goes please?


If it works well I will update the build system or at least provide 
instructions on what I have done to optimize so that all other Raspberry 
Pi users can benefit.


73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

[Nikiforos Kontopoulos]

Hello all.

Finished compiling and tested wsjt-x v1.8.0-rc1 on my raspberry pi 3 with 
Raspbian.

20m Jt65a + Ft8 work like a charm. Had some qsos already.

Will also try to compile it on armbian for OrangePi plus 2e.



Best 73 de SV1EEX - Nik



Sent from Mail for Windows 10

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Beta Release: WSJT-X Version 1.8.0-rc1

[Joe Taylor]

The WSJT Development Group is pleased to announce a candidate release of 
WSJT-X Version 1.8.0.  This is a beta release, already tested in the 
field by around 160 alpha-test users.  A short list of new features and 
capabilities (including the new FT8 and FreqCal modes) can be found in 
the Release Notes:

http://www.physics.princeton.edu/pulsar/K1JT/Release_Notes_1.8.0.txt

After any reported problems with this beta release have been addressed, 
Version 1.8.0 will become the standard "General Availability" release of 
WSJT-X.


Installation packages for Windows, Linux, OS X, and Raspbian Jessie can
be downloaded from the WSJT web site:
http://physics.princeton.edu/pulsar/K1JT/wsjtx.html

A detailed log of program changes since v1.7.0 is available here:
http://physics.princeton.edu/pulsar/K1JT/wsjtx-1.8.0.log

Upgrading from version 1.4 or later will be seamless.  There is no need 
to uninstall a previous version or to move any files.


Please report any problems you find with this beta release to one of 
these email lists: wsjt-devel@lists.sourceforge.net 
wsjtgr...@yahoogroups.com .  For both lists you will need to be a 
subscriber in order to post there.


-- 73 from Joe, K1JT, for the WSJT Development Group

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Beta Release: WSJT-X Version 1.8.0-rc1

[Joe Taylor]

The WSJT Development Group is pleased to announce a candidate release of 
WSJT-X Version 1.8.0.  This is a beta release, already tested in the 
field by around 160 alpha-test users.  A short list of new features and 
capabilities (including the new FT8 and FreqCal modes) can be found in 
the Release Notes:

http://www.physics.princeton.edu/pulsar/K1JT/Release_Notes_1.8.0.txt

After any reported problems with this beta release have been addressed, 
Version 1.8.0 will become the standard "General Availability" release of 
WSJT-X.


Installation packages for Windows, Linux, OS X, and Raspbian Jessie can
be downloaded from the WSJT web site:
http://physics.princeton.edu/pulsar/K1JT/wsjtx.html

A detailed log of program changes since v1.7.0 is available here:
http://physics.princeton.edu/pulsar/K1JT/wsjtx-1.8.0.log

Upgrading from version 1.4 or later will be seamless.  There is no need 
to uninstall a previous version or to move any files.


Please report any problems you find with this beta release to one of 
these email lists: wsjt-devel@lists.sourceforge.net 
wsjtgr...@yahoogroups.com .  For both lists you will need to be a 
subscriber in order to post there.


-- 73 from Joe, K1JT, for the WSJT Development Group

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Distribution

[Bill Somerville]

On 11/07/2017 12:35, James Shaver (N2ADV) wrote:

Please be advised that there are some enterprising souls sharing links directly 
to Sourceforge distributing the Release Candidate files all over social media. 
Seeing posts crop up everywhere.


Hi James,

I'm afraid it is worse than that, looking at the pskreporter stats I see 
that the most common version is a revision that is not the one that will 
be the RC1 release. I guess as usual some bright spark thinks they can 
pretend to be beating the system by building and distributing a kit 
before the official announcement.


Fair notice to anyone who has downloaded WSJT-X v1.8.0-rc1 from an 
unofficial source, r7843 is not going to be the official release 
revision and whoever supplied it to you is not complying with our wishes 
to not distribute unofficial binary installers of WSJT-X. There appear 
to be at least 138 of you out there, perhaps we should ask Philip to 
name and shame!


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Distribution

[James Shaver (N2ADV)]

Please be advised that there are some enterprising souls sharing links directly 
to Sourceforge distributing the Release Candidate files. There have been posts 
all over Facebook so far and people are downloading like crazy. 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Distribution

[James Shaver (N2ADV)]

Please be advised that there are some enterprising souls sharing links directly 
to Sourceforge distributing the Release Candidate files all over social media. 
Seeing posts crop up everywhere. 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] wsjt-x 1.8RC! great! Only small flies in the ointment

[Peter Frenning [OZ1PIF]]

  
  
JT8 seems to really rock'n'roll.
  Two fairly small problems:
  1'st report after selecting a new callsign to work, should be kept
  until end of QSO.
  I'm to old for this fast-paced mode, I really need ½-1s more
  between overs to react before the next message hits the airwaves.
  (Probably to late to do anything about that)

-- 
Vy 73 de OZ1PIF/5Q2M, Peter

**
** The day Microsoft makes something	**
** that doesn't suck is probably the 	**
** day they start making vacuum		**
** cleaners ! **
**  	-- Anonymous Wise Guy	**
**
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
**


  


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Possible bug in 7818 thru 7844

[Richard Lamont]

On 11/07/17 01:57, George J Molnar wrote:

> I can confirm Gary’s report on 7844 for MacOS. 
> 
> George J Molnar, KF2T 
> Nevada, USA

I can confirm it on 7844, 7848 and rc1 for Ubuntu 16.04.

73,
Richard G4DYA



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJTX RC1

[Bill Somerville]

On 11/07/2017 10:57, char...@sucklingfamily.free-online.co.uk wrote:

  I must have missed the announcement that installers for
1.8.0 are available for download now.


Hi Charlie and all,

no such announcement has been made (ok perhaps one in that SourceForge 
automatically tells registered users when files have been uploaded), I 
am sure it is imminent. Sometimes it is like guarding a sweetshop from 
unruly children around here ;)


As for the version naming, we have not got around to bumping the version 
on the development branch, it's nothing to worry about, in fact it will 
help to encourage beta testers to focus on the upcoming release 
candidate. I am always amazed at how much credence people will attribute 
to a label written by a human. The release candidate (RC) is what will 
need expanded testing. It, or a successor, will become the next official 
general availability release (GA), once any final critical defects are 
resolved. Release candidates and GA releases are cut from a separate 
copy of the source code which is branched from the development source 
code, this allows us to get on with potentially disruptive changes in 
the development source code while managing the release from the now 
hopefully much more stable release branch.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJTX RC1

[Gordon Higgins]

HI all using ft8 v1.8.0-rc1
 when i call cq  with call 1st ticked workes fine call sequence as exppeted
but when i have logged call, enable tx goes out @ i have to re  enable to
call cq again, i do not have  disable tx after sending 73 ticked ??


now  looking for dxcc n0  50 in ft8like mode,   have decoded down to
-21  @ up to  +15  with no trouble .

 well done 73 gordon

On 11 July 2017 at 10:57,  wrote:

> Hi Greg
>
> All understood.  I must have missed the announcement that installers for
> 1.8.0 are available for download now.
>
> As you note, we should concentrate on testing that.
>
> 73
>
> Charlie
>
> > Erik, All,
> >
> > At this point in the release cycle, its beneficial to the development
> team
> > to test the installation, as well as new features, on as many instances
> as
> > possible. Bill created installers for most, if not all, the supported
> > distributions. We should be testing that release, and providing feedback
> > of
> > our observations. The revision numbers mean very little to end users at
> at
> > present. As for laymen terms, it gets complicated "real quick", so
> there's
> > not much point in hashing through that.
> >
> > Continuing to build from the development branch will only slow things
> > down.
> > I can't say for certain, however, based on previous release cycles there
> > will be one or more additional RC's before the final release.
> >
> > Unless something dramatic happens, there won't be any major changes made
> > that warrants dev-branch builds for the masses. What is most needed now
> is
> > hammering out the proposed release code. If something major crops up,
> they
> > can always post another RC.
> >
> > The more testing we do on the RC revision will only help to ensure a
> > trouble free product later down the line. Unless your one of the core
> > developers, or a distribution package maintainers, building from source
> > code is not the best approach.
> >
> > I am running the revision Bill posted for Windows. Installation went
> > without issue, and seems to be running as expected. That
> > revision-(1.8.0-RC1)-is what we need to be testing.
> >
> > 73's
> > Greg, KI7MT
> >
> >
> >
> > On Mon, Jul 10, 2017 at 11:57 PM, Erik -  wrote:
> >
> >> I guess I’m having a ‘duh’ moment: r7848 is wsjtx-1.8.0-rc1 (I
> >> presume)
> >> ……….. if I update svn and compile I get r7848 but it is
> >> 1.7.1-devel and
> >> this is what I do not understand due to my total lack of knowledge. If
> >> someone could tell me in layman’s terms why that is I would be
> >> grateful.
> >>
> >>
> >>
> >> Erik EI4KF.
> >>
> >>
> >>
> >> 
> >> --
> >> Check out the vibrant tech community on one of the world's most
> >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> >> ___
> >> wsjt-devel mailing list
> >> wsjt-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >>
> >>
> > 
> --
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org!
> > http://sdm.link/slashdot___
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJTX RC1

[charlie]

Hi Greg

All understood.  I must have missed the announcement that installers for 
1.8.0 are available for download now.

As you note, we should concentrate on testing that.

73

Charlie

> Erik, All,
>
> At this point in the release cycle, its beneficial to the development team
> to test the installation, as well as new features, on as many instances as
> possible. Bill created installers for most, if not all, the supported
> distributions. We should be testing that release, and providing feedback
> of
> our observations. The revision numbers mean very little to end users at at
> present. As for laymen terms, it gets complicated "real quick", so there's
> not much point in hashing through that.
>
> Continuing to build from the development branch will only slow things
> down.
> I can't say for certain, however, based on previous release cycles there
> will be one or more additional RC's before the final release.
>
> Unless something dramatic happens, there won't be any major changes made
> that warrants dev-branch builds for the masses. What is most needed now is
> hammering out the proposed release code. If something major crops up, they
> can always post another RC.
>
> The more testing we do on the RC revision will only help to ensure a
> trouble free product later down the line. Unless your one of the core
> developers, or a distribution package maintainers, building from source
> code is not the best approach.
>
> I am running the revision Bill posted for Windows. Installation went
> without issue, and seems to be running as expected. That
> revision-(1.8.0-RC1)-is what we need to be testing.
>
> 73's
> Greg, KI7MT
>
>
>
> On Mon, Jul 10, 2017 at 11:57 PM, Erik -  wrote:
>
>> I guess I’m having a ‘duh’ moment: r7848 is wsjtx-1.8.0-rc1 (I
>> presume)
>> ……….. if I update svn and compile I get r7848 but it is
>> 1.7.1-devel and
>> this is what I do not understand due to my total lack of knowledge. If
>> someone could tell me in layman’s terms why that is I would be
>> grateful.
>>
>>
>>
>> Erik EI4KF.
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJTX RC1

[Erik -]

Greg – thank you, clear and concise.

Another observation, probably already known but anyway: clearly FT8 usage has 
spiked today now that an official downloadable release is available. I am CQing 
on 20m and getting multiple callers. But no decodes. I have to stop CQing and 
wait several periods to see if some of the callers stop and then I decode the 
remaining one. So is there anything in the works to improve this i.e decode all 
of what is calling or even just one of them when there are more than one 
responding?

Thanks again,

Erik.


From: Greg Beam [mailto:ki7m...@gmail.com]
Sent: 11 July 2017 08:37
To: WSJT software development 
Subject: Re: [wsjt-devel] WSJTX RC1

Erik, All,

At this point in the release cycle, its beneficial to the development team to 
test the installation, as well as new features, on as many instances as 
possible. Bill created installers for most, if not all, the supported 
distributions. We should be testing that release, and providing feedback of our 
observations. The revision numbers mean very little to end users at at present. 
As for laymen terms, it gets complicated "real quick", so there's not much 
point in hashing through that.

Continuing to build from the development branch will only slow things down. I 
can't say for certain, however, based on previous release cycles there will be 
one or more additional RC's before the final release.

Unless something dramatic happens, there won't be any major changes made that 
warrants dev-branch builds for the masses. What is most needed now is hammering 
out the proposed release code. If something major crops up, they can always 
post another RC.

The more testing we do on the RC revision will only help to ensure a trouble 
free product later down the line. Unless your one of the core developers, or a 
distribution package maintainers, building from source code is not the best 
approach.

I am running the revision Bill posted for Windows. Installation went without 
issue, and seems to be running as expected. That revision-(1.8.0-RC1)-is what 
we need to be testing.

73's
Greg, KI7MT



On Mon, Jul 10, 2017 at 11:57 PM, Erik - 
> wrote:
[cid:image001.jpg@01D2FA22.AF2CDA30]
I guess I’m having a ‘duh’ moment: r7848 is wsjtx-1.8.0-rc1 (I presume) ……….. 
if I update svn and compile I get r7848 but it is 1.7.1-devel and this is what 
I do not understand due to my total lack of knowledge. If someone could tell me 
in layman’s terms why that is I would be grateful.

Erik EI4KF.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJTX RC1

[Greg Beam]

Erik, All,

At this point in the release cycle, its beneficial to the development team
to test the installation, as well as new features, on as many instances as
possible. Bill created installers for most, if not all, the supported
distributions. We should be testing that release, and providing feedback of
our observations. The revision numbers mean very little to end users at at
present. As for laymen terms, it gets complicated "real quick", so there's
not much point in hashing through that.

Continuing to build from the development branch will only slow things down.
I can't say for certain, however, based on previous release cycles there
will be one or more additional RC's before the final release.

Unless something dramatic happens, there won't be any major changes made
that warrants dev-branch builds for the masses. What is most needed now is
hammering out the proposed release code. If something major crops up, they
can always post another RC.

The more testing we do on the RC revision will only help to ensure a
trouble free product later down the line. Unless your one of the core
developers, or a distribution package maintainers, building from source
code is not the best approach.

I am running the revision Bill posted for Windows. Installation went
without issue, and seems to be running as expected. That
revision-(1.8.0-RC1)-is what we need to be testing.

73's
Greg, KI7MT



On Mon, Jul 10, 2017 at 11:57 PM, Erik -  wrote:

> I guess I’m having a ‘duh’ moment: r7848 is wsjtx-1.8.0-rc1 (I presume)
> ……….. if I update svn and compile I get r7848 but it is 1.7.1-devel and
> this is what I do not understand due to my total lack of knowledge. If
> someone could tell me in layman’s terms why that is I would be grateful.
>
>
>
> Erik EI4KF.
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJTX RC1

[Erik -]

Ok Iain, I think I follow. My weird way of thinking made me believe that 
1.8.0-devel releases would go to 1.8.0 and not 1.7.1-devel releases. For the 
average user, it is confusing - or maybe it's just me I suppose.

Thanks anyway.

Erik.


-Original Message-
From: iain macdonnell - N6ML [mailto:a...@dseven.org] 
Sent: 11 July 2017 07:25
To: WSJT software development 
Subject: Re: [wsjt-devel] WSJTX RC1

On Mon, Jul 10, 2017 at 11:57 PM, Erik -  wrote:
>
> I guess I’m having a ‘duh’ moment: r7848 is wsjtx-1.8.0-rc1 (I presume) ……….. 
> if I update svn and compile I get r7848 but it is 1.7.1-devel and this is 
> what I do not understand due to my total lack of knowledge. If someone could 
> tell me in layman’s terms why that is I would be grateful.

Explaining source code management in layman's terms is non-trivial.
Explaining it in *any* terms is non-trivial! :)

If you want to evaluate the RC's, it might be easier to just download the built 
packages as they're published/announced.

If you wan to stay on the bleeding edge, you could keep building the way you 
have been, but you're building from the trunk, which could conceivably have 
some features that will not be part of the 1.8.0 release.

It is possible to build from the 1.8.0-rc1 branch (with JTSDK, etc.) but it's 
probably not worth the complexity, unless you're involved in the release 
process somehow.

73,

~iain / N6ML

--
Check out the vibrant tech community on one of the world's most engaging tech 
sites, Slashdot.org! http://sdm.link/slashdot 
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Auto-sequence (r7848)

[Erik -]

EA8/G8BCG called CQ and I answered: EA8/G8BCG EI4KF

G8BCG returned a report (I know why G8BCG and not EA8/G8BCG)

Auto-sequence, though enabled, did not function and the entire contact had to 
be made manually. Of course that isn't a problem but I wonder if that is the 
expected behaviour. It seemed that the change of the callsign broke 
auto-sequence.

Erik EI4KF.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJTX RC1

[Erik -]

Hi Charlie - I'm too thick to follow, please try again. Everyone can download 
the official release at 
https://sourceforge.net/projects/wsjt/files/wsjtx-1.8.0-rc1/wsjtx-1.8.0-rc1-win32.exe/download

and get 1.8.0 but a svn update and compile gets 1.7.1

Can you elaborate a bit more on the explanation?

Thanks 

Erik.


-Original Message-
From: char...@sucklingfamily.free-online.co.uk 
[mailto:char...@sucklingfamily.free-online.co.uk] 
Sent: 11 July 2017 07:08
To: WSJT software development 
Subject: Re: [wsjt-devel] WSJTX RC1

Hi Erik

No, r7848 is still 1.7.1.

While preparations have been made for 1.8.0 those are not yet implemented in 
what we build.

73

Charlie G3WDG

>
> I guess I'm having a 'duh' moment: r7848 is wsjtx-1.8.0-rc1 (I 
> presume) ... if I update svn and compile I get r7848 but it is 
> 1.7.1-devel and this is what I do not understand due to my total lack 
> of knowledge. If someone could tell me in layman's terms why that is I would 
> be grateful.
>
> Erik EI4KF.
>
> --
>  Check out the vibrant tech community on one of the world's 
> most engaging tech sites, Slashdot.org!
> http://sdm.link/slashdot__
> _
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>



--
Check out the vibrant tech community on one of the world's most engaging tech 
sites, Slashdot.org! http://sdm.link/slashdot 
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJTX RC1

[iain macdonnell - N6ML]

On Mon, Jul 10, 2017 at 11:57 PM, Erik -  wrote:
>
> I guess I’m having a ‘duh’ moment: r7848 is wsjtx-1.8.0-rc1 (I presume) ……….. 
> if I update svn and compile I get r7848 but it is 1.7.1-devel and this is 
> what I do not understand due to my total lack of knowledge. If someone could 
> tell me in layman’s terms why that is I would be grateful.

Explaining source code management in layman's terms is non-trivial.
Explaining it in *any* terms is non-trivial! :)

If you want to evaluate the RC's, it might be easier to just download
the built packages as they're published/announced.

If you wan to stay on the bleeding edge, you could keep building the
way you have been, but you're building from the trunk, which could
conceivably have some features that will not be part of the 1.8.0
release.

It is possible to build from the 1.8.0-rc1 branch (with JTSDK, etc.)
but it's probably not worth the complexity, unless you're involved in
the release process somehow.

73,

~iain / N6ML

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJTX RC1

[charlie]

Hi Erik

No, r7848 is still 1.7.1.

While preparations have been made for 1.8.0 those are not yet implemented
in what we build.

73

Charlie G3WDG

>
> I guess I'm having a 'duh' moment: r7848 is wsjtx-1.8.0-rc1 (I presume)
> ... if I update svn and compile I get r7848 but it is 1.7.1-devel
> and this is what I do not understand due to my total lack of knowledge. If
> someone could tell me in layman's terms why that is I would be grateful.
>
> Erik EI4KF.
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJTX RC1

[Erik -]

I guess I'm having a 'duh' moment: r7848 is wsjtx-1.8.0-rc1 (I presume) 
... if I update svn and compile I get r7848 but it is 1.7.1-devel and 
this is what I do not understand due to my total lack of knowledge. If someone 
could tell me in layman's terms why that is I would be grateful.

Erik EI4KF.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel