Re: [wsjt-devel] Double Display in Rx window

[Ricky Scott]

Yes its double in the received window on the right side, ok on the left.  Only calls directed at me, if I put the cursor on someone in the window its a single.On July 7, 2017 at 10:20 PM iain macdonnell - N6ML  wrote:On Fri, Jul 7, 2017 at 5:52 PM, Neil Zampella  wrote:Seeing double entries for the replying station in the RX window, r7812.Yep, me too... seems to be only on messages directed to my callsign.73,~iain / N6ML--Check out the vibrant tech community on one of the world's mostengaging tech sites, Slashdot.org! http://sdm.link/slashdot___wsjt-devel mailing listwsjt-devel@lists.sourceforge.nethttps://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] Double Display in Rx window

[iain macdonnell - N6ML]

On Fri, Jul 7, 2017 at 5:52 PM, Neil Zampella  wrote:
> Seeing double entries for the replying station in the RX window, r7812.

Yep, me too... seems to be only on messages directed to my callsign.

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] FT8 Testing

[Gary McDuffie]

> On Jul 7, 2017, at 9:19 PM, David  wrote:
> 
> Hi All...been on 20m 17.074 calling CQ..Gary AG0N called me decode was -19 
> but the band here is up and down at the moment .tnx Gary hope we can do 
> it sometime
> 
> 73 David VK4BDJ

I got all but the 73, David.  It is legal and logged.  Thanks.

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

[wsjt-devel] FT8

[David]

Hi good sigs from USA..tnx guys for QSO

David  VK4BDJ


--
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 Testing

[Eric Gruff]

David,

I just swung the beam your way. If you're still around, I'm monitoring 14074
FT8.

Eric NC6K

-Original Message-
From: David [mailto:djm...@bigpond.com] 
Sent: Friday, July 7, 2017 8:19 PM
To: 'WSJT software development' 
Subject: [wsjt-devel] FT8 Testing

Hi All...been on 20m 17.074 calling CQ..Gary AG0N called me decode was
-19 but the band here is up and down at the moment .tnx Gary hope we can
do it sometime

73 David VK4BDJ



--
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] FT8 on test

[David]

Hi ...made a couple of contacts VK4QG and N7XR..found out that once 
you double click on the callsign it has an Auto Seq feature.real 
neat helps with the Qso as the mode is so fast..


Love the mode and will continue to test it

73 David VK4BDJ


--
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 Testing

[David]

Hi All...been on 20m 17.074 calling CQ..Gary AG0N called me decode was 
-19 but the band here is up and down at the moment .tnx Gary hope we 
can do it sometime


73 David VK4BDJ


--
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] Compiling issues...

[Greg Beam]

Hi Ryan,

 

I think the package your looking for is:

 

https://packages.ubuntu.com/xenial/libusb-1.0-0-dev

 

https://packages.ubuntu.com/xenial/i386/libusb-1.0-0-dev/filelist

 

 

.. so that would be: sudo apt-get install libusb-1.0-0-dev

 

That is the package for 16.04 (Xenial).

 

I don’t know how your compiling WSJT-X, so I can’t advise any further than that.

 

73’s

Greg, KI7MT

 

 

From: Ryan Tourge [mailto:ryan.tou...@gmail.com] 
Sent: Friday, July 7, 2017 9:05 PM
To: ll...@gcis.biz; WSJT software development 
Subject: Re: [wsjt-devel] Compiling issues...

 

Well I've tried everything I can think of. And what you fellas could think of, 
and what Facebook could think of. I'm missing something. I'll wait for the RC.

 

On Fri, Jul 7, 2017 at 9:19 PM, Lloyd Kirk mailto:ll...@gcis.biz> > wrote:

You need libusb-1.0.0  and the -devel package I suspect.

Had a similar issue with this on my old centos 6 box and had to compile that 
from source..

Lloyd Kirk
WB5HUP

On 2017-07-07 19:31, G8DQX (WSJT developers on SF) wrote:

Ryan,

one suspects that, for Ubuntu, the command should be:

SUDO APT INSTALL LIBUSB-1.0-0-DEV

HTH,

Robin, G8DQX

 On 08/07/17 00:50, Bill Somerville wrote:

Hi Ryan,

sorry you are having trouble building WSJT-X. Try this:

$ sudo apt install libusb-devel

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

 

--
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] Compiling issues...

[Ryan Tourge]

Well I've tried everything I can think of. And what you fellas could think
of, and what Facebook could think of. I'm missing something. I'll wait for
the RC.

On Fri, Jul 7, 2017 at 9:19 PM, Lloyd Kirk  wrote:

> You need libusb-1.0.0  and the -devel package I suspect.
>
> Had a similar issue with this on my old centos 6 box and had to compile
> that from source..
>
> Lloyd Kirk
> WB5HUP
>
> On 2017-07-07 19:31, G8DQX (WSJT developers on SF) wrote:
>
>> Ryan,
>>
>> one suspects that, for Ubuntu, the command should be:
>>
>> SUDO APT INSTALL LIBUSB-1.0-0-DEV
>>
>> HTH,
>>
>> Robin, G8DQX
>>
>>  On 08/07/17 00:50, Bill Somerville wrote:
>>
>> Hi Ryan,
>>>
>>> sorry you are having trouble building WSJT-X. Try this:
>>>
>>> $ sudo apt install libusb-devel
>>>
>>> 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
>
--
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.7.1 r7812

[David]

Hi Joe and Bill.compiled r7812 with JTSDK and it works 100% .FT8 
RX/TX


working well with FT-450D rig.thanks guys maybe we will get a 
contact...usually on 20m 14074.00 for FT8


73 David VK4BDJ


--
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: IMPORTANT NOTICE

[Steven Franke]

Hi Bob,

Bill may have gone to bed… He was on 20m, 14.074.

Steve, k9an

> On Jul 8, 2017, at 2:05 AM, Robert Nobis  wrote:
> 
> Hi Bill,
> 
> Fantastic. Just wondering, what band were you on?
> 
> 
> Bob Nobis 
> n7...@nobis.net 
> 
> 
>> On Jul 7, 2017, at 18:10, Bill Somerville > > wrote:
>> 
>> On 08/07/2017 00:53, Joe Taylor wrote:
>>> To:  Users of FT8 
>>> From:WSJT Development Team 
>>> Subject: IMPORTANT NOTICE ABOUT FT8 
>> HI Joe,
>> 
>> working UFB here, my first FT8 long path QSO using 50W my end:
>> 
>> 010245  Tx  1212 ~  VK6KXW G4WJS IO91
>> 010230 -14  0.7 1189 ~  CQ VK6KXW OF87
>> 010246  Tx  1189 ~  VK6KXW G4WJS IO91
>> 010300 -16  0.2 1189 ~  G4WJS VK6KXW -14
>> 010300 -16  0.2 1189 ~  G4WJS VK6KXW -14
>> 010315  Tx  1189 ~  VK6KXW G4WJS R-16
>> 010330 -16  0.2 1188 ~  G4WJS VK6KXW RRR
>> 010330 -16  0.2 1188 ~  G4WJS VK6KXW RRR
>> 010345  Tx  1189 ~  VK6KXW G4WJS 73
>> 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 
> 
--
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: IMPORTANT NOTICE

[Robert Nobis]

Hi Bill,

Fantastic. Just wondering, what band were you on?


Bob Nobis 
n7...@nobis.net


> On Jul 7, 2017, at 18:10, Bill Somerville  wrote:
> 
> On 08/07/2017 00:53, Joe Taylor wrote:
>> To:  Users of FT8 
>> From:WSJT Development Team 
>> Subject: IMPORTANT NOTICE ABOUT FT8 
> HI Joe,
> 
> working UFB here, my first FT8 long path QSO using 50W my end:
> 
> 
> 010245  Tx  1212 ~  VK6KXW G4WJS IO91
> 010230 -14  0.7 1189 ~  CQ VK6KXW OF87
> 010246  Tx  1189 ~  VK6KXW G4WJS IO91
> 010300 -16  0.2 1189 ~  G4WJS VK6KXW -14
> 010300 -16  0.2 1189 ~  G4WJS VK6KXW -14
> 010315  Tx  1189 ~  VK6KXW G4WJS R-16
> 010330 -16  0.2 1188 ~  G4WJS VK6KXW RRR
> 010330 -16  0.2 1188 ~  G4WJS VK6KXW RRR
> 010345  Tx  1189 ~  VK6KXW G4WJS 73
> 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] FT8: IMPORTANT NOTICE

[Dave Clouser]

Thank you Joe and team. looking forward to it.

Dave NZ3M


On 7/7/2017 9:10 PM, Bill Somerville wrote:

On 08/07/2017 00:53, Joe Taylor wrote:

To: Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8


HI Joe,

working UFB here, my first FT8 long path QSO using 50W my end:

010245  Tx  1212 ~  VK6KXW G4WJS IO91

010230 -14  0.7 1189 ~  CQ VK6KXW OF87

010246  Tx  1189 ~  VK6KXW G4WJS IO91

010300 -16  0.2 1189 ~  G4WJS VK6KXW -14

010300 -16  0.2 1189 ~  G4WJS VK6KXW -14

010315  Tx  1189 ~  VK6KXW G4WJS R-16

010330 -16  0.2 1188 ~  G4WJS VK6KXW RRR

010330 -16  0.2 1188 ~  G4WJS VK6KXW RRR

010345  Tx  1189 ~  VK6KXW G4WJS 73

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] FT8: IMPORTANT NOTICE

[Bill Somerville]

On 08/07/2017 02:10, Bill Somerville wrote:

working UFB here


12 US states, 1 VE province, 4 DXCC (K, VE, EI, VK) in less than 90 
minutes on 20m. And we haven't even beta released FT8 yet.


Thanks folks:

US Counties

   confirmed: 0
   worked   : 16

   Count   State  CountyCallsign
 QTHBandMode   Status

   1  ALMARSHALLKQ5S
 Albertville, AL 20M FT8   worked
   2  AL  SHELBY  WB4KDI
  Birmingham, AL 20M FT8   worked
   3  AZMARICOPAAA7A
  Scottsdale, AZ 20M FT8   worked
   4  FL LEEW9BS
  Fort Myers, FL 20M FT8   worked
   5  GA QUITMAN   AI5II
  Georgetown, GA 20M FT8   worked
   6  IL   CHAMPAIGNK9AN
  Urbana, IL 20M FT8   worked
   7  MOCASSNV0O
 Lees Summit, MO 20M FT8   worked
   8  MSHARRISONWQ5L
Gulfport, MS 20M FT8   worked
   9  NJ  MERCERK1JT
   Princeton, NJ 20M FT8   worked
  10  NY MADISON   N2ADV
  Oneida, NY 20M FT8   worked
  11  PA   BUCKS   W2SRH
 Morrisville, PA 20M FT8   worked
  12  PA FAYETTE  KN3ILZ
   Connellsville, PA 20M FT8   worked
  13  PA  MCKEAN  KB3MOW
   Port Allegany, PA 20M FT8   worked
  14  PA MONTOUR   N3JIX
Danville, PA 20M FT8   worked
  15  TXANGELINA   N5SDD
  Huntington, TX 20M FT8   worked
  16  VA HANOVER   K4DET
  Glen Allen, VA 20M FT8   worked

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] Compiling issues...

[Lloyd Kirk]

You need libusb-1.0.0  and the -devel package I suspect.

Had a similar issue with this on my old centos 6 box and had to compile 
that from source..


Lloyd Kirk
WB5HUP

On 2017-07-07 19:31, G8DQX (WSJT developers on SF) wrote:

Ryan,

one suspects that, for Ubuntu, the command should be:

SUDO APT INSTALL LIBUSB-1.0-0-DEV

HTH,

Robin, G8DQX

 On 08/07/17 00:50, Bill Somerville wrote:


Hi Ryan,

sorry you are having trouble building WSJT-X. Try this:

$ sudo apt install libusb-devel

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] FT8: IMPORTANT NOTICE

[Bill Somerville]

On 08/07/2017 00:53, Joe Taylor wrote:

To: Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8


HI Joe,

working UFB here, my first FT8 long path QSO using 50W my end:

010245  Tx  1212 ~  VK6KXW G4WJS IO91

010230 -14  0.7 1189 ~  CQ VK6KXW OF87

010246  Tx  1189 ~  VK6KXW G4WJS IO91

010300 -16  0.2 1189 ~  G4WJS VK6KXW -14

010300 -16  0.2 1189 ~  G4WJS VK6KXW -14

010315  Tx  1189 ~  VK6KXW G4WJS R-16

010330 -16  0.2 1188 ~  G4WJS VK6KXW RRR

010330 -16  0.2 1188 ~  G4WJS VK6KXW RRR

010345  Tx  1189 ~  VK6KXW G4WJS 73

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] Double Display in Rx window

[Steve Huston]

Same version, same thing here.  This is a new config (I had
accidentally "cloned" my development config into default, and the
program wouldn't open, so I erased it and started from scratch).

https://www.dropbox.com/s/dxom5s5t8f2n7d6/Screenshot%202017-07-07%2020.58.24.png?dl=0

On Fri, Jul 7, 2017 at 8:52 PM, Neil Zampella  wrote:
> Hi all ..
>
> Seeing double entries for the replying station in the RX window, r7812.
> See attached pic.
>
> 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
>



-- 
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

[wsjt-devel] Fwd: Double Decodes on Received Transmissions - FT8

[Tom-KQ5S]

​
Why am I getting double decodes on transmissions I receive m my QSO partner
in the Rx Frequency.

I have attempted to attach a screenshot.  If not here is a copy and paste.


003945  -6  0.5  784 ~  KQ5S G4WJS +00
003945  -6  0.5  784 ~  KQ5S G4WJS +00

004002  Tx   785 ~  G4WJS KQ5S R-06

004015  -7  0.5  784 ~  KQ5S G4WJS RRR
004015  -7  0.5  784 ~  KQ5S G4WJS RRR

004030  Tx   785 ~  G4WJS KQ5S 73

004045  -9  0.0  784 ~  KQ5S G4WJS 73
004045  -9  0.0  784 ~  KQ5S G4WJS 73


​

73,
Tom - KQ5S
--
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] Double Display in Rx window

[Neil Zampella]

Hi all ..

Seeing double entries for the replying station in the RX window, 
r7812.See attached pic.


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] Compiling issues...

[G8DQX (WSJT developers on SF)]

Ryan,

one suspects that, for Ubuntu, the command should be:

*sudo apt install libusb-1.0-0-dev*

HTH,

Robin, G8DQX


On 08/07/17 00:50, Bill Somerville wrote:

Hi Ryan,

sorry you are having trouble building WSJT-X. Try this:

$ sudo apt install libusb-devel

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: IMPORTANT NOTICE

[David Tiller]

Joe and the dev team,

Excellent work! The new-and-improved FT8 is working well. I'm using 7812 on a 
Mac.

One thing I'm seeing, however: I'm getting double decodes when I'm in a QSO. 
For instance:

[cid:25421FA7-3F32-40AC-9BD3-18D564FDDAC7]

Is it just me?

--
David Tiller
Sr. Architect/Lead Consultant | CapTech
(804) 304-0638 | 
dtil...@captechconsulting.com



On Jul 7, 2017, at 7:53 PM, Joe Taylor 
mailto:j...@princeton.edu>> wrote:

To:  Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8

If you are building WSJT-X for yourself from source code, you may now upgrade 
to r7812 and recompile. You will then have access to the latest version of FT8 
plus some new features for setting default operating frequencies by mode and 
IARU region.  The program built in this way will be called WSJT-X v1.7.1 r7812.

Note that essentially the same program will soon be packaged for wider 
distribution as as "WSJT-X Version 1.8.0-rc1" (release candidate 1), see below).

Remember that FT8 in code revisions 7812 are higher is NOT COMPATIBLE with that 
in 7782 and earlier.  To use FT8 you must upgrade to r7812.
If you see FT8 signals that do not decode, they may be using the obsolete 
protocol.

About the Default Working Frequencies
=

FT8 will likely be popular with MF and HF users as well as the VHF multi-hop 
sporadic-E DXers it was designed for.  After consultation with the user 
community, we have reworked the suggested operating frequency defaults to 
include FT8.  This was not easy on every relevant band; where possible, we have 
suggested a 2 kHz range for exclusive FT8 use. (Exclusivity is important, as 
the T/R period is 15 s which will not mix well with mode that use one-minute 
sequences.)

In general the FT8 frequencies are set 2kHz below the current JT65 allocation.  
This should allow operation using a normal SSB filter width without too much 
interference from strong JT65 signals up the band.  On some bands that has not 
been possible since JT65 sits at the lowest usable narrow band data mode 
frequency, when considering all international band plans.

For the 660 m and 2200 m  bands we have not assigned separate frequencies for 
JT65/JT9/FT8, and just expect users to coordinate themselves.  The numbers of 
active operators will probably be low enough that this will not cause issues.

For 160 m we assume that the JT65 and JT9 sub-bands can be squeezed to
1 kHz each, and FT8 can sit above using up to another 1 kHz.

Previous 80 m use of JT modes has done a disservice to JA operators, who have 
no privileges on the current WSPR/JT65/JT9 allocations.  To correct this we 
have moved the allocations to a part of the band where JAs can operate.  
Obviously this change will impact other non-WSJT-X users, so for now we suggest 
that if you intend to operate on 80 m JT65/JT9/WSPR then you manually change 
the working frequencies in WSJT-X ("Settings->Frequencies") back to the old 
allocations until a general availability release of WSJT-X v1.8.0 is published. 
This will allow time for other software teams to coordinate with us.

The old allocations are:

JT65 3.567 MHz
JT9  3.578 MHz
WSPR 3.5926 MHz

For 6 m we understand that the IARU Region 1 band plan is not to the liking of 
DX chasers around the world and largely ignored by Region 1 users.  However we 
cannot reasonably continue to set working frequency suggestions that drive 
traffic to parts of the band that are not supposed to be used for narrow band 
data modes.  The v1.8.0 release will allow Region-specific working frequencies 
as well as globally coordinated ones.  Consequently we have set the Region 1 
working frequencies roughly in line with the band plan.  If you do not like the 
allocations then do not complain to us, but complain to your Region 1 band 
coordinator along with reasons why you think it should change.  The proposed 
Region 1 working frequencies are usable globally wherever 6m data mode 
operation is permitted so we have set them as global rather than Region 1 
specific.  Region 2 and 3 operators will have both local and global frequencies 
offered.

Other changes are in line with current usage.


Finally, if you are waiting for pre-built installation packages:

We plan to post a release candidate for WSJT-X v1.8.0-rc1 configured for 
Windows, Linux, and OS X very soon -- probably early next week.  Thanks for 
your patience!

   -- 73, Joe, K1JT (for the WSJT Development Team)

--
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: IMPORTANT NOTICE

[Eric Gruff]

My thanks also to Joe and the team. Two QSOs completed so far, and one with
signal levels around -18. No repeats needed, and seems like all working so
far.


NC6K

-Original Message-
From: Dan Malcolm [mailto:dan.malcol...@gmail.com] 
Sent: Friday, July 7, 2017 5:42 PM
To: 'WSJT software development' 
Subject: Re: [wsjt-devel] FT8: IMPORTANT NOTICE

Thanks Joe.  I know you and your fellow developers have been hard at it, and
we appreciate the effort, and the great results.

One issue I am seeing that during a QSO, my QSO partners replies show up in
Band Activity fine, but get doubled in Rx Frequency.  I have screen shots,
and will provide them if you need them.  Thanks again.

Dan - K4SHQ

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Friday, July 07, 2017 6:54 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] FT8: IMPORTANT NOTICE

To:  Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8

If you are building WSJT-X for yourself from source code, you may now
upgrade to r7812 and recompile. You will then have access to the latest
version of FT8 plus some new features for setting default operating
frequencies by mode and IARU region.  The program built in this way will be
called WSJT-X v1.7.1 r7812.

Note that essentially the same program will soon be packaged for wider
distribution as as "WSJT-X Version 1.8.0-rc1" (release candidate 1), see
below).

Remember that FT8 in code revisions 7812 are higher is NOT COMPATIBLE with
that in 7782 and earlier.  To use FT8 you must upgrade to r7812.
If you see FT8 signals that do not decode, they may be using the obsolete
protocol.

About the Default Working Frequencies
=

FT8 will likely be popular with MF and HF users as well as the VHF multi-hop
sporadic-E DXers it was designed for.  After consultation with the user
community, we have reworked the suggested operating frequency defaults to
include FT8.  This was not easy on every relevant band; where possible, we
have suggested a 2 kHz range for exclusive FT8 use. 
(Exclusivity is important, as the T/R period is 15 s which will not mix well
with mode that use one-minute sequences.)

In general the FT8 frequencies are set 2kHz below the current JT65
allocation.  This should allow operation using a normal SSB filter width
without too much interference from strong JT65 signals up the band.  On some
bands that has not been possible since JT65 sits at the lowest usable narrow
band data mode frequency, when considering all international band plans.

For the 660 m and 2200 m  bands we have not assigned separate frequencies
for JT65/JT9/FT8, and just expect users to coordinate themselves.  The
numbers of active operators will probably be low enough that this will not
cause issues.

For 160 m we assume that the JT65 and JT9 sub-bands can be squeezed to
1 kHz each, and FT8 can sit above using up to another 1 kHz.

Previous 80 m use of JT modes has done a disservice to JA operators, who
have no privileges on the current WSPR/JT65/JT9 allocations.  To correct
this we have moved the allocations to a part of the band where JAs can
operate.  Obviously this change will impact other non-WSJT-X users, so for
now we suggest that if you intend to operate on 80 m JT65/JT9/WSPR then you
manually change the working frequencies in WSJT-X
("Settings->Frequencies") back to the old allocations until a general
availability release of WSJT-X v1.8.0 is published. This will allow time for
other software teams to coordinate with us.

The old allocations are:

JT65 3.567 MHz
JT9  3.578 MHz
WSPR 3.5926 MHz

For 6 m we understand that the IARU Region 1 band plan is not to the liking
of DX chasers around the world and largely ignored by Region 1 users.
However we cannot reasonably continue to set working frequency suggestions
that drive traffic to parts of the band that are not supposed to be used for
narrow band data modes.  The v1.8.0 release will allow Region-specific
working frequencies as well as globally coordinated ones.  Consequently we
have set the Region 1 working frequencies roughly in line with the band
plan.  If you do not like the allocations then do not complain to us, but
complain to your Region 1 band coordinator along with reasons why you think
it should change.  The proposed Region 1 working frequencies are usable
globally wherever 6m data mode operation is permitted so we have set them as
global rather than Region 1 specific.  Region 2 and 3 operators will have
both local and global frequencies offered.

Other changes are in line with current usage.


Finally, if you are waiting for pre-built installation packages:

We plan to post a release candidate for WSJT-X v1.8.0-rc1 configured for
Windows, Linux, and OS X very soon -- probably early next week.  Thanks for
your patience!

 -- 73, Joe, K1JT (for the WSJT Development Team)


--
Check o

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[Dan Malcolm]

Thanks Joe.  I know you and your fellow developers have been hard at it, and
we appreciate the effort, and the great results.

One issue I am seeing that during a QSO, my QSO partners replies show up in
Band Activity fine, but get doubled in Rx Frequency.  I have screen shots,
and will provide them if you need them.  Thanks again.

Dan - K4SHQ

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Friday, July 07, 2017 6:54 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] FT8: IMPORTANT NOTICE

To:  Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8

If you are building WSJT-X for yourself from source code, you may now
upgrade to r7812 and recompile. You will then have access to the latest
version of FT8 plus some new features for setting default operating
frequencies by mode and IARU region.  The program built in this way will be
called WSJT-X v1.7.1 r7812.

Note that essentially the same program will soon be packaged for wider
distribution as as "WSJT-X Version 1.8.0-rc1" (release candidate 1), see
below).

Remember that FT8 in code revisions 7812 are higher is NOT COMPATIBLE with
that in 7782 and earlier.  To use FT8 you must upgrade to r7812.
If you see FT8 signals that do not decode, they may be using the obsolete
protocol.

About the Default Working Frequencies
=

FT8 will likely be popular with MF and HF users as well as the VHF multi-hop
sporadic-E DXers it was designed for.  After consultation with the user
community, we have reworked the suggested operating frequency defaults to
include FT8.  This was not easy on every relevant band; where possible, we
have suggested a 2 kHz range for exclusive FT8 use. 
(Exclusivity is important, as the T/R period is 15 s which will not mix well
with mode that use one-minute sequences.)

In general the FT8 frequencies are set 2kHz below the current JT65
allocation.  This should allow operation using a normal SSB filter width
without too much interference from strong JT65 signals up the band.  On some
bands that has not been possible since JT65 sits at the lowest usable narrow
band data mode frequency, when considering all international band plans.

For the 660 m and 2200 m  bands we have not assigned separate frequencies
for JT65/JT9/FT8, and just expect users to coordinate themselves.  The
numbers of active operators will probably be low enough that this will not
cause issues.

For 160 m we assume that the JT65 and JT9 sub-bands can be squeezed to
1 kHz each, and FT8 can sit above using up to another 1 kHz.

Previous 80 m use of JT modes has done a disservice to JA operators, who
have no privileges on the current WSPR/JT65/JT9 allocations.  To correct
this we have moved the allocations to a part of the band where JAs can
operate.  Obviously this change will impact other non-WSJT-X users, so for
now we suggest that if you intend to operate on 80 m JT65/JT9/WSPR then you
manually change the working frequencies in WSJT-X
("Settings->Frequencies") back to the old allocations until a general
availability release of WSJT-X v1.8.0 is published. This will allow time for
other software teams to coordinate with us.

The old allocations are:

JT65 3.567 MHz
JT9  3.578 MHz
WSPR 3.5926 MHz

For 6 m we understand that the IARU Region 1 band plan is not to the liking
of DX chasers around the world and largely ignored by Region 1 users.
However we cannot reasonably continue to set working frequency suggestions
that drive traffic to parts of the band that are not supposed to be used for
narrow band data modes.  The v1.8.0 release will allow Region-specific
working frequencies as well as globally coordinated ones.  Consequently we
have set the Region 1 working frequencies roughly in line with the band
plan.  If you do not like the allocations then do not complain to us, but
complain to your Region 1 band coordinator along with reasons why you think
it should change.  The proposed Region 1 working frequencies are usable
globally wherever 6m data mode operation is permitted so we have set them as
global rather than Region 1 specific.  Region 2 and 3 operators will have
both local and global frequencies offered.

Other changes are in line with current usage.


Finally, if you are waiting for pre-built installation packages:

We plan to post a release candidate for WSJT-X v1.8.0-rc1 configured for
Windows, Linux, and OS X very soon -- probably early next week.  Thanks for
your patience!

 -- 73, Joe, K1JT (for the WSJT Development Team)


--
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: IMPORTANT NOTICE

[Joe Taylor]

To:  Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8

If you are building WSJT-X for yourself from source code, you may now 
upgrade to r7812 and recompile. You will then have access to the latest 
version of FT8 plus some new features for setting default operating 
frequencies by mode and IARU region.  The program built in this way will 
be called WSJT-X v1.7.1 r7812.


Note that essentially the same program will soon be packaged for wider 
distribution as as "WSJT-X Version 1.8.0-rc1" (release candidate 1), see 
below).


Remember that FT8 in code revisions 7812 are higher is NOT COMPATIBLE 
with that in 7782 and earlier.  To use FT8 you must upgrade to r7812.
If you see FT8 signals that do not decode, they may be using the 
obsolete protocol.


About the Default Working Frequencies
=

FT8 will likely be popular with MF and HF users as well as the VHF 
multi-hop sporadic-E DXers it was designed for.  After consultation with 
the user community, we have reworked the suggested operating frequency 
defaults to include FT8.  This was not easy on every relevant band; 
where possible, we have suggested a 2 kHz range for exclusive FT8 use. 
(Exclusivity is important, as the T/R period is 15 s which will not mix 
well with mode that use one-minute sequences.)


In general the FT8 frequencies are set 2kHz below the current JT65 
allocation.  This should allow operation using a normal SSB filter width 
without too much interference from strong JT65 signals up the band.  On 
some bands that has not been possible since JT65 sits at the lowest 
usable narrow band data mode frequency, when considering all 
international band plans.


For the 660 m and 2200 m  bands we have not assigned separate 
frequencies for JT65/JT9/FT8, and just expect users to coordinate 
themselves.  The numbers of active operators will probably be low enough 
that this will not cause issues.


For 160 m we assume that the JT65 and JT9 sub-bands can be squeezed to
1 kHz each, and FT8 can sit above using up to another 1 kHz.

Previous 80 m use of JT modes has done a disservice to JA operators, who 
have no privileges on the current WSPR/JT65/JT9 allocations.  To correct 
this we have moved the allocations to a part of the band where JAs can 
operate.  Obviously this change will impact other non-WSJT-X users, so 
for now we suggest that if you intend to operate on 80 m JT65/JT9/WSPR 
then you manually change the working frequencies in WSJT-X 
("Settings->Frequencies") back to the old allocations until a general 
availability release of WSJT-X v1.8.0 is published. This will allow time 
for other software teams to coordinate with us.


The old allocations are:

JT65 3.567 MHz
JT9  3.578 MHz
WSPR 3.5926 MHz

For 6 m we understand that the IARU Region 1 band plan is not to the 
liking of DX chasers around the world and largely ignored by Region 1 
users.  However we cannot reasonably continue to set working frequency 
suggestions that drive traffic to parts of the band that are not 
supposed to be used for narrow band data modes.  The v1.8.0 release will 
allow Region-specific working frequencies as well as globally 
coordinated ones.  Consequently we have set the Region 1 working 
frequencies roughly in line with the band plan.  If you do not like the 
allocations then do not complain to us, but complain to your Region 1 
band coordinator along with reasons why you think it should change.  The 
proposed Region 1 working frequencies are usable globally wherever 6m 
data mode operation is permitted so we have set them as global rather 
than Region 1 specific.  Region 2 and 3 operators will have both local 
and global frequencies offered.


Other changes are in line with current usage.


Finally, if you are waiting for pre-built installation packages:

We plan to post a release candidate for WSJT-X v1.8.0-rc1 configured for 
Windows, Linux, and OS X very soon -- probably early next week.  Thanks 
for your patience!


-- 73, Joe, K1JT (for the WSJT Development Team)

--
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] Compiling issues...

[Bill Somerville]

On 08/07/2017 00:41, Ryan Tourge wrote:
I'm having trouble compiling WSJT-X. I've installed the SDK and I 
believe all the dependencies that it has yelled at me about.  It 
appears to have built hamlib-3 fine but when I try to build the latest 
development branch it gives me the following:


This is on an Ubuntu 16.04 32 Bit system:

/home/ryantourge/jtsdk/hamlib3/lib/libhamlib.a(usb_port.o): In 
function `usb_port_open':
(.text.usb_port_open+0x197): undefined reference to 
`libusb_set_auto_detach_kernel_driver'

collect2: error: ld returned 1 exit status


Hi Ryan,

sorry you are having trouble building WSJT-X. Try this:

$ sudo apt install libusb-devel

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] Compiling issues...

[Ryan Tourge]

I'm having trouble compiling WSJT-X. I've installed the SDK and I believe
all the dependencies that it has yelled at me about.  It appears to have
built hamlib-3 fine but when I try to build the latest development branch
it gives me the following:

This is on an Ubuntu 16.04 32 Bit system:

/home/ryantourge/jtsdk/hamlib3/lib/libhamlib.a(usb_port.o): In function
`usb_port_open':
(.text.usb_port_open+0x197): undefined reference to
`libusb_set_auto_detach_kernel_driver'
collect2: error: ld returned 1 exit status
CMakeFiles/wsjtx.dir/build.make:1019: recipe for target 'wsjtx' failed
make[2]: *** [wsjtx] Error 1
CMakeFiles/Makefile2:175: recipe for target 'CMakeFiles/wsjtx.dir/all'
failed
make[1]: *** [CMakeFiles/wsjtx.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2
--
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] Frequency List in r7805

[Bill Somerville]

On 07/07/2017 23:55, Neil Zampella wrote:
quick question, should frequencies that should be labeled at FT8 in 
the frequency list have the Mode blank when looking at the list, or is 
this something that will change at midnight, like Cinderella's coach 
?? :)


The reason I ask, is that they're turning up in the list when I'm in 
JT65/JT9 mode.


Hi Neil,

that sounds like you have added the FT8 frequencies manually.

Working frequencies with a blank mode are offered for all modes.

Yes the current pumpkin will transform after midnight UTC assuming you 
rebuild the latest version. Hopefully the results will be more 
persistent than Cinderella's accoutrements.


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] Frequency List in r7805

[Neil Zampella]

Hi all,

quick question, should frequencies that should be labeled at FT8 in the 
frequency list have the Mode blank when looking at the list, or is this 
something that will change at midnight, like Cinderella's coach ??  :)


The reason I ask, is that they're turning up in the list when I'm in 
JT65/JT9 mode.


Cheers,

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] FT8: IMPORTANT NOTICE

[charlie]

Thanks, Joe

> Correct.  It's not yet  UTC on July 8.
>
> On 7/7/2017 1:27 PM, char...@sucklingfamily.free-online.co.uk wrote:
>> Hi Joe
>>
>> I think the code in mainwindow.cpp still has the restriction on mycall,
>> in
>> two places.
>>
>> Program does not run unless mycall set to one of the test calls.
>>
>> Charlie
>>
>>> To:  Users of FT8
>>> From:WSJT Development Team
>>> Subject: IMPORTANT NOTICE ABOUT EXPERIMENTAL MODE FT8
>>>
>>> The planned protocol change in FT8 is now complete and tested.
>>> Effective
>>> at  UTC on July 8, 2017, you should stop using FT8 with any WSJT-X
>>> code revision earlier than r7805.
>>>
>>> If you are building WSJT-X for yourself from source code, on July 8 or
>>> later you may upgrade to the latest code revision and recompile. You
>>> will then have access to the latest version of FT8.
>>>
>>> If you are waiting for pre-built installation packages: We plan to post
>>> a release candidate for WSJT-X v1.8.0-rc1 configured for Windows,
>>> Linux,
>>> and OS X very soon -- probably early next week.  Thanks for your
>>> patience.
>>>
>>> -- 73, Joe, K1JT (for the WSJT Development Team)
>>>
>>> --
>>> 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: IMPORTANT NOTICE

[Joe Taylor]

Correct.  It's not yet  UTC on July 8.

On 7/7/2017 1:27 PM, char...@sucklingfamily.free-online.co.uk wrote:

Hi Joe

I think the code in mainwindow.cpp still has the restriction on mycall, in
two places.

Program does not run unless mycall set to one of the test calls.

Charlie


To:  Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT EXPERIMENTAL MODE FT8

The planned protocol change in FT8 is now complete and tested. Effective
at  UTC on July 8, 2017, you should stop using FT8 with any WSJT-X
code revision earlier than r7805.

If you are building WSJT-X for yourself from source code, on July 8 or
later you may upgrade to the latest code revision and recompile. You
will then have access to the latest version of FT8.

If you are waiting for pre-built installation packages: We plan to post
a release candidate for WSJT-X v1.8.0-rc1 configured for Windows, Linux,
and OS X very soon -- probably early next week.  Thanks for your patience.

-- 73, Joe, K1JT (for the WSJT Development Team)

--
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] Suggestions for three extra bits in FT8

[Philip Gladstone]

I'd like to see a message type that consisted of a callsign in the 
current format, and the rest of the bits are in a callsign specific 
message format. It should be displayed as HEX. There should be a website 
somewhere where the message format is defined based on the sending 
callsign. For example, it might be used to report location data from 
(say) a balloon.


It turns out that a useful message size can actually be fit into the 
existing 72 bit message (there are, as I recall, around 2^68 code points 
that are unused -- 28 bits for a callsign + 48 bits for 12 hex 
characters -- fits easily into the existing format).


Philip

On 07/07/2017 12:55, Black Michael via wsjt-devel wrote:
Consideration may be given to using the 3 bits as an index rather than 
binary bits.
That would give 7 options based on a 3-bit index with 000 meaning no 
options.


de Mike W9MDB




*From:* Alexandre Moleiro via wsjt-devel 


*To:* WSJT software development 
*Cc:* Alexandre Moleiro 
*Sent:* Friday, July 7, 2017 11:49 AM
*Subject:* Re: [wsjt-devel] Suggestions for three extra bits in FT8

Hi!

3 extra bits can potentially create 5 new FT8 "submodes" with just 
these constraints:

-15 second T/R period
-72 bits of payload each period

This can open a whole new world of qso sequences, multi-pass decoding, 
TX power adjustment, beaconing, etc.


We can look at "most requested" features (portable and rover 
operation, complete grids contests, very complex compound callsigns, 
etc) but we can also begin with a clean sheet of paper and try to take 
a step into the future.


73 de CT1GVN







On Thursday, July 6, 2017, 2:49:12 PM GMT+1, Bill Somerville 
 wrote:



On 06/07/2017 14:26, James Lemley wrote:
> After discarding the idea of encoding eight humorous messages, and
> without studying the rest of the protocol to see if these are already
> implemented, here are my suggestions for the three extra bits with a
> transmit frame:

HI James,

adding extra ad hoc messages can be easily done by using some of the
unused existing message space. For example the directional CQ messages
were inserted by using the unused callsign series E9xx. These sort of
things require no extra bits, just global agreement.

With respect to your other suggestions, in the protocols as they stand
every standard message except the 73 one expects acknowledgement. The 73
and free text messages do not expect acknowledgement although some free
text messages can be constructed to imply acknowledgement is expected,
"REPORT PSE?" for example. When acknowledgement is not received then
simply repeating the last message until acknowledgement is received is
all that is needed. It is unfortunate that many users wish to shorten
the QSO sequences without regard for the above. There are some cases for
dropping messages like the initial grid reply to a CQ when propagation
is unstable.

I believe you are not thinking far enough outside the box with how an
extra bit may be used. For example the current protocol is partitioned
into two by a single bit. One half encompasses every standard message
and the other half encompasses all the free text messages. A single
extra bit opens up the possibility of a whole new protocol with a
message space as large as the existing protocol. Using one or more extra
bits to add value to the existing protcol would be missing a huge
opportunity.

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




--
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/w

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[charlie]

Hi Joe

I think the code in mainwindow.cpp still has the restriction on mycall, in
two places.

Program does not run unless mycall set to one of the test calls.

Charlie

> To:  Users of FT8
> From:WSJT Development Team
> Subject: IMPORTANT NOTICE ABOUT EXPERIMENTAL MODE FT8
>
> The planned protocol change in FT8 is now complete and tested. Effective
> at  UTC on July 8, 2017, you should stop using FT8 with any WSJT-X
> code revision earlier than r7805.
>
> If you are building WSJT-X for yourself from source code, on July 8 or
> later you may upgrade to the latest code revision and recompile. You
> will then have access to the latest version of FT8.
>
> If you are waiting for pre-built installation packages: We plan to post
> a release candidate for WSJT-X v1.8.0-rc1 configured for Windows, Linux,
> and OS X very soon -- probably early next week.  Thanks for your patience.
>
>   -- 73, Joe, K1JT (for the WSJT Development Team)
>
> --
> 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]

Consideration may be given to using the 3 bits as an index rather than binary 
bits.That would give 7 options based on a 3-bit index with 000 meaning no 
options.
de Mike W9MDB


  From: Alexandre Moleiro via wsjt-devel 
 To: WSJT software development  
Cc: Alexandre Moleiro 
 Sent: Friday, July 7, 2017 11:49 AM
 Subject: Re: [wsjt-devel] Suggestions for three extra bits in FT8
   
Hi!
3 extra bits can potentially create 5 new FT8 "submodes" with just these 
constraints:
-15 second T/R period-72 bits of payload each period
This can open a whole new world of qso sequences, multi-pass decoding, TX power 
adjustment, beaconing, etc.
We can look at "most requested" features (portable and rover operation, 
complete grids contests, very complex compound callsigns, etc) but we can also 
begin with a clean sheet of paper and try to take a step into the future.

73 de CT1GVN







On Thursday, July 6, 2017, 2:49:12 PM GMT+1, Bill Somerville 
 wrote:

On 06/07/2017 14:26, James Lemley wrote:
> After discarding the idea of encoding eight humorous messages, and 
> without studying the rest of the protocol to see if these are already 
> implemented, here are my suggestions for the three extra bits with a 
> transmit frame:

HI James,

adding extra ad hoc messages can be easily done by using some of the 
unused existing message space. For example the directional CQ messages 
were inserted by using the unused callsign series E9xx. These sort of 
things require no extra bits, just global agreement.

With respect to your other suggestions, in the protocols as they stand 
every standard message except the 73 one expects acknowledgement. The 73 
and free text messages do not expect acknowledgement although some free 
text messages can be constructed to imply acknowledgement is expected, 
"REPORT PSE?" for example. When acknowledgement is not received then 
simply repeating the last message until acknowledgement is received is 
all that is needed. It is unfortunate that many users wish to shorten 
the QSO sequences without regard for the above. There are some cases for 
dropping messages like the initial grid reply to a CQ when propagation 
is unstable.

I believe you are not thinking far enough outside the box with how an 
extra bit may be used. For example the current protocol is partitioned 
into two by a single bit. One half encompasses every standard message 
and the other half encompasses all the free text messages. A single 
extra bit opens up the possibility of a whole new protocol with a 
message space as large as the existing protocol. Using one or more extra 
bits to add value to the existing protcol would be missing a huge 
opportunity.

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


   --
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

[Alexandre Moleiro via wsjt-devel]

Hi!
3 extra bits can potentially create 5 new FT8 "submodes" with just these 
constraints:
-15 second T/R period-72 bits of payload each period
This can open a whole new world of qso sequences, multi-pass decoding, TX power 
adjustment, beaconing, etc.
We can look at "most requested" features (portable and rover operation, 
complete grids contests, very complex compound callsigns, etc) but we can also 
begin with a clean sheet of paper and try to take a step into the future.

73 de CT1GVN







On Thursday, July 6, 2017, 2:49:12 PM GMT+1, Bill Somerville 
 wrote:

On 06/07/2017 14:26, James Lemley wrote:
> After discarding the idea of encoding eight humorous messages, and 
> without studying the rest of the protocol to see if these are already 
> implemented, here are my suggestions for the three extra bits with a 
> transmit frame:

HI James,

adding extra ad hoc messages can be easily done by using some of the 
unused existing message space. For example the directional CQ messages 
were inserted by using the unused callsign series E9xx. These sort of 
things require no extra bits, just global agreement.

With respect to your other suggestions, in the protocols as they stand 
every standard message except the 73 one expects acknowledgement. The 73 
and free text messages do not expect acknowledgement although some free 
text messages can be constructed to imply acknowledgement is expected, 
"REPORT PSE?" for example. When acknowledgement is not received then 
simply repeating the last message until acknowledgement is received is 
all that is needed. It is unfortunate that many users wish to shorten 
the QSO sequences without regard for the above. There are some cases for 
dropping messages like the initial grid reply to a CQ when propagation 
is unstable.

I believe you are not thinking far enough outside the box with how an 
extra bit may be used. For example the current protocol is partitioned 
into two by a single bit. One half encompasses every standard message 
and the other half encompasses all the free text messages. A single 
extra bit opens up the possibility of a whole new protocol with a 
message space as large as the existing protocol. Using one or more extra 
bits to add value to the existing protcol would be missing a huge 
opportunity.

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] FT8: IMPORTANT NOTICE

[Joe Taylor]

To:  Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT EXPERIMENTAL MODE FT8

The planned protocol change in FT8 is now complete and tested. Effective 
at  UTC on July 8, 2017, you should stop using FT8 with any WSJT-X 
code revision earlier than r7805.


If you are building WSJT-X for yourself from source code, on July 8 or 
later you may upgrade to the latest code revision and recompile. You 
will then have access to the latest version of FT8.


If you are waiting for pre-built installation packages: We plan to post 
a release candidate for WSJT-X v1.8.0-rc1 configured for Windows, Linux, 
and OS X very soon -- probably early next week.  Thanks for your patience.


-- 73, Joe, K1JT (for the WSJT Development Team)

--
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] Preparation for WSJT-X v1.8.0-rc1

[Black Michael via wsjt-devel]

For Bill
The easy way to test functionality is to remove set_vfo from dummy.c in hamlib 
and test with that and rigctld.
WSJT-X will fail.  So it's just changing the set_vfo capability logic to match 
get the get_vfo logic.
Bill's hamlib has been updated for the rigctld side to fix that side of the 
problem.  The set_vfo.patch is the WSJT-X side of the equation.
This showed up on the FT-891/991 not having vfo capabilities. de Mike W9MDB


  From: Joe Taylor 
 To: WSJT software development  
 Sent: Friday, July 7, 2017 8:20 AM
 Subject: Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1
   
Mike --

Thanks for submitting the patches!  I have installed "menu.patch" and 
"qsotime.patch".  They appear to be OK, but please double-check to be 
sure their functions are what's wanted.

I have left rigctld_setvfo.patch for Bill; I have no easy way to test 
its functionality here.

    -- Joe

On 7/6/2017 5:06 PM, Black Michael via wsjt-devel wrote:
> Pull the qsotime.patch again -- I just posted another one.
> 
> At least in my testing it's working for both double clicking QSOs in the 
> Rx Freq column and with short modes.
> 
> de Mike W9MDB
> 
> 
> *From:* Bill Somerville 
> *To:* wsjt-devel@lists.sourceforge.net
> *Sent:* Thursday, July 6, 2017 11:12 AM
> *Subject:* Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1
> 
> On 06/07/2017 17:00, Black Michael via wsjt-devel wrote:
>> I've got 3 patches outstanding
>>
>> #1 Menu controls working when controls are hidden + CTRL-E/Shift-E 
>> shortcuts for enabling/disabling Tx even/1st
>> #2 Fix rigctld aborting on rigs without set_vfo (e.g. FT-891/991)
>> #3 Fix QSO start times for double-click progression and autoseq modes
>>
>> Here they are:
>>
>> https://www.dropbox.com/s/d20ycgqtthckudk/rigctld_setvfo.patch?dl=1
>> https://www.dropbox.com/s/frarvcjefhxn5d2/menu.patch?dl=1
>> https://www.dropbox.com/s/kr4lcc7rcg00j1i/qsotime.patch?dl=1
>>
>> de Mike W9MDB
> Hi Mike,
> thanks for the reminder. I need to pull the amended version of your 
> start and end times and check it it with short T/R periods. I will look 
> at those three as well.
> 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
> 

--
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] Preparation for WSJT-X v1.8.0-rc1

[Joe Taylor]

Mike --

Thanks for submitting the patches!  I have installed "menu.patch" and 
"qsotime.patch".  They appear to be OK, but please double-check to be 
sure their functions are what's wanted.


I have left rigctld_setvfo.patch for Bill; I have no easy way to test 
its functionality here.


-- Joe

On 7/6/2017 5:06 PM, Black Michael via wsjt-devel wrote:

Pull the qsotime.patch again -- I just posted another one.

At least in my testing it's working for both double clicking QSOs in the 
Rx Freq column and with short modes.


de Mike W9MDB


*From:* Bill Somerville 
*To:* wsjt-devel@lists.sourceforge.net
*Sent:* Thursday, July 6, 2017 11:12 AM
*Subject:* Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1

On 06/07/2017 17:00, Black Michael via wsjt-devel wrote:

I've got 3 patches outstanding

#1 Menu controls working when controls are hidden + CTRL-E/Shift-E 
shortcuts for enabling/disabling Tx even/1st

#2 Fix rigctld aborting on rigs without set_vfo (e.g. FT-891/991)
#3 Fix QSO start times for double-click progression and autoseq modes

Here they are:

https://www.dropbox.com/s/d20ycgqtthckudk/rigctld_setvfo.patch?dl=1
https://www.dropbox.com/s/frarvcjefhxn5d2/menu.patch?dl=1
https://www.dropbox.com/s/kr4lcc7rcg00j1i/qsotime.patch?dl=1

de Mike W9MDB

Hi Mike,
thanks for the reminder. I need to pull the amended version of your 
start and end times and check it it with short T/R periods. I will look 
at those three as well.

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



--
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

[Jordan Sherer]

I think this might have been might missed in the fury of activity yesterday.

Is there a write-up of the protocol anywhere for deeper understanding?

Best,
Jordan
KN4CRD

On Jul 6, 2017, 12:22 PM -0400, Jordan Sherer , wrote:
> Thanks for the insight, Bill. Is there a writeup of the protocol anywhere for 
> deeper understanding?
>
> One idea I had after playing around with PSK & FSQ these past few days is to 
> leverage an extra bit to allow for a QSO centered around freeform messaging 
> on HF. Specifically, one of those bits to be used as a "continuation bit" to 
> signal (when true) that the message is split between multiple transmission 
> blocks. An example:
>
> CQ KN4CRD EM73 (continuation)
> WAS CT DE PA (continuation)
> WAS NY RI MA (continuation)
> CQ KN4CRD EM73 (stop)
>
> or
>
> G4WJS KN4CRD -10 (continuation)
> DT -0.5 QSB (continuation)
> NAME JORDAN (continuation)
> 5W INDR MLOOP (continuation)
> G4WJS KN4CRD K (stop)
>
> The nice thing is that with the FT8 transmissions, you'd see those 
> incremental messages come in every 15 seconds. So, it would be a middle 
> ground between real-time PSK decoding and the one minute delay of JT65. 
> Transmissions would still be synchronized to the time interval, so there 
> shouldn't be too much dead air between responses (15 seconds of dead air is 
> way easier to stomach than 60+).
>
> The other thing that I've been noticing is that with the pace of the FT8 
> transmissions, repeat messages are coming in frequently because there is a 
> miss to engage the calling CQ station, or perhaps autoseq was disabled, or 
> there was some band fading that caused the decoder to missfire. The 
> continuation bit could be used to synchronize on a 30 second interval with 
> doubling of every message to ensure delivery:
>
> CQ KN4CRD EM73 (continuation)
> CQ KN4CRD EM73 (stop)
>
> or
>
> KN4CRD G4WJS -18 (continuation)
> KN4CRD G4WJS -18 (stop)
>
> As above, if you had a reliable signal you would see the first interval come 
> in (with a continuation indicator, maybe an ellipsis ... in the ui or 
> something next to the message). That would give the responding station 15 
> more seconds to write their reply while the second (duplicated) transmission 
> came in (which would be really useful in freeform text).
>
> I have some other ideas regarding the other bits, but I'd like to dig into 
> the protocol as it is today before suggesting anything else.
>
> Curious on what y'all think about something like this?
>
> Best,
> Jordan
> KN4CRD
>
>
>
>
>
>
> On Thu, Jul 6, 2017 at 9:47 AM, Bill Somerville  (mailto:g4...@classdesign.com)> wrote:
> > On 06/07/2017 14:26, James Lemley wrote:
> > > After discarding the idea of encoding eight humorous messages, and 
> > > without studying the rest of the protocol to see if these are already 
> > > implemented, here are my suggestions for the three extra bits with a 
> > > transmit frame:
> >
> > HI James,
> >
> > adding extra ad hoc messages can be easily done by using some of the unused 
> > existing message space. For example the directional CQ messages were 
> > inserted by using the unused callsign series E9xx. These sort of things 
> > require no extra bits, just global agreement.
> >
> > With respect to your other suggestions, in the protocols as they stand 
> > every standard message except the 73 one expects acknowledgement. The 73 
> > and free text messages do not expect acknowledgement although some free 
> > text messages can be constructed to imply acknowledgement is expected, 
> > "REPORT PSE?" for example. When acknowledgement is not received then simply 
> > repeating the last message until acknowledgement is received is all that is 
> > needed. It is unfortunate that many users wish to shorten the QSO sequences 
> > without regard for the above. There are some cases for dropping messages 
> > like the initial grid reply to a CQ when propagation is unstable.
> >
> > I believe you are not thinking far enough outside the box with how an extra 
> > bit may be used. For example the current protocol is partitioned into two 
> > by a single bit. One half encompasses every standard message and the other 
> > half encompasses all the free text messages. A single extra bit opens up 
> > the possibility of a whole new protocol with a message space as large as 
> > the existing protocol. Using one or more extra bits to add value to the 
> > existing protcol would be missing a huge opportunity.
> >
> > 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 (mailto:wsjt-devel@lists.sourceforge.net)
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
--

Re: [wsjt-devel] FT8 audio spacing - waterfall graticule

[Bill Somerville]

On 07/07/2017 11:23, Richard Lamont wrote:

FT8 doesn't have a two-pass decoder. Even it it did, a signal that
doesn't have another one overlapping it stands a better chance of being
decoded.

A regular spacing of (say) 60 Hz would help to keep things apart.

I'm not suggesting that this should be forced on users by WSJT-X, but
there is a way it could be hinted at for those who want to choose
regular steps when calling CQ. And that is to add, subtly and in the
background, a graticule to the waterfall.


Hi Richard,

we did consider enforcing channelization while designing FT8, there are 
sensitivity and decoder speed advantages to be had if signals can be 
assumed to be at certain offsets. The raised frequency calibration and 
stability requirements were considered to be unlikely to be met by all 
stations,


Having a "hint" graticule is not a bad idea though.

Two pass decoding is being investigated as FT8 looks like it will be 
popular on busy HF bands. It remains to be seen how users get on with 
the rather fast pace of thinking that it imposes, particularly with only 
limited support from JTAlert and similar.


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] FT8 audio spacing - waterfall graticule

[Richard Lamont]

FT8 doesn't have a two-pass decoder. Even it it did, a signal that
doesn't have another one overlapping it stands a better chance of being
decoded.

A regular spacing of (say) 60 Hz would help to keep things apart.

I'm not suggesting that this should be forced on users by WSJT-X, but
there is a way it could be hinted at for those who want to choose
regular steps when calling CQ. And that is to add, subtly and in the
background, a graticule to the waterfall.

At the moment the waterfall has bright, thin green horizontal lines
marking the boundaries between T/R periods. We could add, as a
configurable option, somewhat darker thin green vertical lines at 60 Hz
steps.

Another option would be to move the marker pips at the top of the
waterfall from 100 Hz steps to 60 Hz steps.


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] Preparation for WSJT-X v1.8.0-rc1

[Bill Somerville]

On 07/07/2017 07:58, Adrian Fabry wrote:
2. For the saved wav files, mode and submode should be included in the 
file name


Hi Ady,

more information is included in the catalogue of the WAV files. It can 
be examined using a tool like Audacity to look at the metadata. It is 
unfortunate that the WAV file format largely designed by Microsoft is 
not correctly displayed in MS Windows File Explorer. At some point I am 
considering displaying the metadata either in a custom file selector for 
WSJT-X "Open file" or displaying the information when a file is played back.


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] Preparation for WSJT-X v1.8.0-rc1

[Adrian Fabry]

Hi Joe,

thank you and all the development team for the work.

I'd suggest two features:

1. QRA64:  Different color (or using bold chars) for the AP part of the
decoded message, when AP was used in the decode.
2. For the saved wav files, mode and submode should be included in the file
name

73 Ady YO2NAA


On Thu, Jul 6, 2017 at 6:46 PM, Joe Taylor  wrote:

> Hi all,
>
> I'm compiling a list of important new features and other changes that will
> be in WSJT-X v1.8.
>
> 1.  New mode called FT8: QSOs 4 times faster than JT9, JT65
> 2.  New mode for Frequency Calibration
> 3.  Improved performance of decoders for JT65, QRA64, and MSK144
> 4.  New utility programs: msk144code, fmeasure, fmtave, fcal, ft8sim,
> ft8d.
> 5.  Options to minimize sizes of Main window and Wide Graph window.
> 6.  New default table of recommended operating frequencies
> 7.  Improved CAT control for many rigs, including operation through
> Commander and OmniRig
> 8.  Many minor bug fixes and tweaks to the user interface
>
> Have I omitted anything that should be in this list?
>
> -- 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