Re: [wsjt-devel] 1.9 rc2 windows size

[Andras Bato]

Hi Jerry,
I was quite busy with KH6CW yesterday...
As for the new version, just wait for the release V1.9.0
rc2 is release candidate.
I use both V1.8.0 and V1.9.0 rc2 under Windows 10 64 bit version.
You will have another mail. A forward.
Good testing!
gl de ha6nn
Andras

On Sun, Mar 4, 2018 at 4:43 PM, Andras Bato  wrote:

> Hi Jerry,
> I see 3000 HZ 0 - 3000
> but I have cut the lower 0500 Hz by DSP:::
> GL
> Andras HA6NN
>
>
> On Sun, Mar 4, 2018 at 4:34 PM, Jerry S  wrote:
>
>> I noticed that the band activity window width in 1.9.0 rc2 is not being
>> saved.
>> The width can be resized in relation to the rx frequency window but
>> settings are not saved.
>> It was saved in 1.8.
>>
>> Jerry W8DLD
>>
>> 
>> --
>> 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] 1.9 rc2 windows size

[Andras Bato]

Jerry and all,
I'm so sorry for mistaking you with another Jerry!
I did not want to write to the forum, please excuse me!
Otherwise I really can cut the lower or upper half of the 3000 Hz wide FT8
subband using DSP, etc.
gl de ha6nn
Andras


On Mon, Mar 5, 2018 at 8:59 AM, Andras Bato  wrote:

> Hi Jerry,
> I was quite busy with KH6CW yesterday...
> As for the new version, just wait for the release V1.9.0
> rc2 is release candidate.
> I use both V1.8.0 and V1.9.0 rc2 under Windows 10 64 bit version.
> You will have another mail. A forward.
> Good testing!
> gl de ha6nn
> Andras
>
> On Sun, Mar 4, 2018 at 4:43 PM, Andras Bato  wrote:
>
>> Hi Jerry,
>> I see 3000 HZ 0 - 3000
>> but I have cut the lower 0500 Hz by DSP:::
>> GL
>> Andras HA6NN
>>
>>
>> On Sun, Mar 4, 2018 at 4:34 PM, Jerry S  wrote:
>>
>>> I noticed that the band activity window width in 1.9.0 rc2 is not being
>>> saved.
>>> The width can be resized in relation to the rx frequency window but
>>> settings are not saved.
>>> It was saved in 1.8.
>>>
>>> Jerry W8DLD
>>>
>>> 
>>> --
>>> 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] Public test of FT8 DXpedition mode March 6-7

[Joe Taylor]

Bonjour Jean,

On 3/5/2018 2:45 AM, Jean Raynaud F8RZ wrote:

Disappointed by the timing, which practically precludes EU from 
participating... And yet, if you want to see the effectiveness in 
difficult conditions, what better QRM generator than EU can you find ?


tongue in cheek... !


Yes, if you and others in EU want to participate in the first public 
test of FT8 DXpedition Mode you'll need to stay up late or get up very 
early.


Obviously it's impossible for us to select a time for the test run 
that's optimum for everyone.  This time it was essential to choose times 
that would be reasonable for two hard-working team members of the Baker 
Island DXpedition, AA7A and N1DG.


Who knows?  After analysis of the first test we might decide that 
another one would be useful.  We might then place it on a weekend, 
something more like 1700 UTC, using "daylight" bands.  Or we might try 
to accommodate friends in VK/ZL.  Or ...


-- 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] Public test of FT8 DXpedition mode March 6-7

[James Shaver]

It also might not be a bad thing if some well-meaning but otherwise
uninformed ops running 1.8 wander into the "pileup" as it may help simulate
real-world conditions where this may also happen with more frequency.
Though they may not decode the "fox" I've seen any number of times where
people will start calling a "DX" even though they can't hear them so I'd
expect this will happen during the public test as word spreads.  It'll help
add legitimacy to real-world QRM.  

Just my 2 cents, feel free to keep the change :)

Jim S. 
N2ADV

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Monday, March 5, 2018 2:02 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7

On 3/4/2018 8:12 PM, David Fisher NX6D wrote:
> I’m curious to know what will happen when someone wanders into these 
> tests, without RC2, and tries to send one of the messages not used in 
> these abbreviated sequences.  Will those callers be ignored?

Only Fox sends a new type of message -- that is, one not supported in WSJT-X
v1.8.0.

I hope it's clear in the FT8 DXpedition Mode User Guide
http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf

... that Fox will respond only to

1. Initial calls like line 2 in the User Guide's example sequence (top of
page 2).  These messages must be received above 1000 Hz; and

2. Messages like lines 4 and 6, from stations to whom Fox has already sent a
signal report.  These must be received between 300 and 900 Hz.

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


--
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] Public test of FT8 DXpedition mode March 6-7

[Joe Taylor]

On 3/4/2018 8:12 PM, David Fisher NX6D wrote:
I’m curious to know what will happen when someone wanders into these 
tests, without RC2, and tries to send one of the messages not used in 
these abbreviated sequences.  Will those callers be ignored?


Only Fox sends a new type of message -- that is, one not supported in 
WSJT-X v1.8.0.


I hope it's clear in the FT8 DXpedition Mode User Guide
http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf

... that Fox will respond only to

1. Initial calls like line 2 in the User Guide's example sequence (top 
of page 2).  These messages must be received above 1000 Hz; and


2. Messages like lines 4 and 6, from stations to whom Fox has already 
sent a signal report.  These must be received between 300 and 900 Hz.


-- 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] Public test of FT8 DXpedition mode March 6-7

[Lee J. Imber (WW2DX)]

Hi Joe,

I will be in V26 this weekend (if the storm on wed allows it). Would be willing 
to be the FOX if need be to put some load on the code.

73 Lee
WW2DX


> On Mar 5, 2018, at 2:09 PM, James Shaver  wrote:
> 
> It also might not be a bad thing if some well-meaning but otherwise
> uninformed ops running 1.8 wander into the "pileup" as it may help simulate
> real-world conditions where this may also happen with more frequency.
> Though they may not decode the "fox" I've seen any number of times where
> people will start calling a "DX" even though they can't hear them so I'd
> expect this will happen during the public test as word spreads.  It'll help
> add legitimacy to real-world QRM.  
> 
> Just my 2 cents, feel free to keep the change :)
> 
> Jim S. 
> N2ADV
> 
> -Original Message-
> From: Joe Taylor [mailto:j...@princeton.edu] 
> Sent: Monday, March 5, 2018 2:02 PM
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7
> 
> On 3/4/2018 8:12 PM, David Fisher NX6D wrote:
>> I’m curious to know what will happen when someone wanders into these 
>> tests, without RC2, and tries to send one of the messages not used in 
>> these abbreviated sequences.  Will those callers be ignored?
> 
> Only Fox sends a new type of message -- that is, one not supported in WSJT-X
> v1.8.0.
> 
> I hope it's clear in the FT8 DXpedition Mode User Guide
> http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf
> 
> ... that Fox will respond only to
> 
> 1. Initial calls like line 2 in the User Guide's example sequence (top of
> page 2).  These messages must be received above 1000 Hz; and
> 
> 2. Messages like lines 4 and 6, from stations to whom Fox has already sent a
> signal report.  These must be received between 300 and 900 Hz.
> 
>   -- 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
> 
> 
> --
> 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] Public test of FT8 DXpedition mode March 6-7

[Joe Taylor]

Bonjour Jean,

On 3/5/2018 2:45 AM, Jean Raynaud F8RZ wrote:

Disappointed by the timing, which practically precludes EU from 
participating... And yet, if you want to see the effectiveness in 
difficult conditions, what better QRM generator than EU can you find ?


tongue in cheek... !



Yes, if you and others in EU want to participate in the first public 
test of FT8 DXpedition Mode you'll need to stay up late or get up very 
early.


Obviously it's impossible for us to select a time for the test run 
that's optimum for everyone.  This time it was essential to choose times 
that would be reasonable for two hard-working team members of the Baker 
Island DXpedition, AA7A and N1DG.


Who knows?  After analysis of the first test we might decide that 
another one would be useful.  We might then place it on a weekend, 
something more like 1700 UTC, using "daylight" bands.  Or we might try 
to accommodate friends in VK/ZL.  Or ...


-- 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] Public test of FT8 DXpedition mode March 6-7

[Pino Zollo]

Hi,

being hound, I have not clear if set up split operation as Rig or Fake it.

Can please explain... if rig how to set the TX freq. on the rig ?


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

[wsjt-devel] Always on the visible working area

[Pino Zollo]

I have two displays ...

One is dedicated to WSJT-X; the other to WEB and other applications.

I am on Linux Mint 18.3.

Right clicking on the top bar of wsjt-x I set "Always on the visible
working area".



The problem is that this setting does not last very muchafter a
while of using this setting is disabled.

This happens only for wsjt-xboth 1.8.0 and the new 1.9.0-rc2.

TU

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] Public test of FT8 DXpedition mode March 6-7

[Bill Somerville]

On 05/03/2018 21:30, Pino Zollo wrote:

Hi,

being hound, I have not clear if set up split operation as Rig or Fake it.

Can please explain... if rig how to set the TX freq. on the rig ?


TU de Pino

ZP4kfx


Hi Pino,

just the same as with other modes of operation, either "Rig" or "Fake 
It" will work. Transmit frequency setting is automatic, you only have to 
set your Rx dial frequency either on the rig, typed directly into the 
band drop down list edit box, or by setting up a frequency and mode in 
"Settings->Frequencies->Working Frequencies".


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] Always on the visible working area

[Bill Somerville]

On 05/03/2018 21:33, Pino Zollo wrote:

I have two displays ...

One is dedicated to WSJT-X; the other to WEB and other applications.

I am on Linux Mint 18.3.

Right clicking on the top bar of wsjt-x I set "Always on the visible
working area".



The problem is that this setting does not last very muchafter a
while of using this setting is disabled.

This happens only for wsjt-xboth 1.8.0 and the new 1.9.0-rc2.

TU

Pino ZP4KFX


Hi Pino,

what do you expect to happen when you have "Always on the visible 
working area" checked? I am guessing this means move that window to the 
current virtual desktop. WSJT-X should remain on the virtual desktop you 
move it to and restart there if the virtual desktop still exists.


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] Public test of FT8 DXpedition mode March 6-7

[David Fisher]

Jim has made the point I was heading towards.  Even when 1.9 is released 
publically, there will be plenty of users of older versions and some will jump 
into fray.  In a test, it’s not very likely there will be much QRM.  In the 
real world, when a rare DX is at stake, I expect it could be quite a mess.  
Some will be transmitting on the DX frequency, some will be transmitting into 
the 300-900 Hz space, etc.  I’m simply trying to stimulate a little 
brainstorming about how this could go wrong and what could be done to mitigate 
it.  We’ve already seen lots of examples of people running old versions of the 
code, running RCs past their expiration date, etc.



I’m not a purveyor of gloom and doom, far from it.  But it’s difficult to roll 
out a dramatically different version of the program once so many are running an 
older incompatible version.  And, even if they are running 1.9, how will they 
get the experience to use the new mode effectively?



Dave / NX6D






From: James Shaver 
Sent: Monday, March 5, 2018 11:09:37 AM
To: 'WSJT software development'
Subject: Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7

It also might not be a bad thing if some well-meaning but otherwise
uninformed ops running 1.8 wander into the "pileup" as it may help simulate
real-world conditions where this may also happen with more frequency.
Though they may not decode the "fox" I've seen any number of times where
people will start calling a "DX" even though they can't hear them so I'd
expect this will happen during the public test as word spreads.  It'll help
add legitimacy to real-world QRM.

Just my 2 cents, feel free to keep the change :)

Jim S.
N2ADV

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Monday, March 5, 2018 2:02 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7

On 3/4/2018 8:12 PM, David Fisher NX6D wrote:
> I’m curious to know what will happen when someone wanders into these
> tests, without RC2, and tries to send one of the messages not used in
> these abbreviated sequences.  Will those callers be ignored?

Only Fox sends a new type of message -- that is, one not supported in WSJT-X
v1.8.0.

I hope it's clear in the FT8 DXpedition Mode User Guide
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fphysics.princeton.edu%2Fpulsar%2Fk1jt%2FFT8_DXpedition_Mode.pdf=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435%7C1%7C0%7C636558738863273348=Fv8YsdwGWJtpSR6%2FWEfmU20p4YKCftMbHMR1DPSlWWk%3D=0

... that Fox will respond only to

1. Initial calls like line 2 in the User Guide's example sequence (top of
page 2).  These messages must be received above 1000 Hz; and

2. Messages like lines 4 and 6, from stations to whom Fox has already sent a
signal report.  These must be received between 300 and 900 Hz.

-- 73, Joe, K1JT


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! 
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdot=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435%7C1%7C0%7C636558738863273348=xGQwTM3BgptdcOi46oTsiKW94MZx7uTgvEU0CQhngRo%3D=0
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435%7C1%7C0%7C636558738863273348=IpyYm%2Fvh7eTF9ROKzkA4vD%2Fap0Q8FKMMfNoc8EpC8aI%3D=0


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdot=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435%7C1%7C0%7C636558738863273348=xGQwTM3BgptdcOi46oTsiKW94MZx7uTgvEU0CQhngRo%3D=0
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435%7C1%7C0%7C636558738863273348=IpyYm%2Fvh7eTF9ROKzkA4vD%2Fap0Q8FKMMfNoc8EpC8aI%3D=0
--
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] Public test of FT8 DXpedition mode March 6-7

[Joe Taylor]

Dave --

All understood.  Rest assured, we have already spent plenty of time 
thinking about -- and testing -- the sort of complications you describe.


No doubt we will still have some surprises. Some will be ones we have 
foreseen, others probably not.  That's precisely why we are doing more 
testing!

-- 73, Joe, K1JT

On 3/5/2018 3:33 PM, David Fisher wrote:
Jim has made the point I was heading towards.  Even when 1.9 is released 
publically, there will be plenty of users of older versions and some 
will jump into fray.  In a test, it’s not very likely there will be much 
QRM.  In the real world, when a rare DX is at stake, I expect it could 
be quite a mess.  Some will be transmitting on the DX frequency, some 
will be transmitting into the 300-900 Hz space, etc.  I’m simply trying 
to stimulate a little brainstorming about how this could go wrong and 
what could be done to mitigate it.  We’ve already seen lots of examples 
of people running old versions of the code, running RCs past their 
expiration date, etc.


I’m not a purveyor of gloom and doom, far from it.  But it’s difficult 
to roll out a dramatically different version of the program once so many 
are running an older incompatible version.  And, even if they are 
running 1.9, how will they get the experience to use the new mode 
effectively?


Dave / NX6D


*From:* James Shaver 
*Sent:* Monday, March 5, 2018 11:09:37 AM
*To:* 'WSJT software development'
*Subject:* Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7
It also might not be a bad thing if some well-meaning but otherwise
uninformed ops running 1.8 wander into the "pileup" as it may help simulate
real-world conditions where this may also happen with more frequency.
Though they may not decode the "fox" I've seen any number of times where
people will start calling a "DX" even though they can't hear them so I'd
expect this will happen during the public test as word spreads.  It'll help
add legitimacy to real-world QRM.

Just my 2 cents, feel free to keep the change :)

Jim S.
N2ADV

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Monday, March 5, 2018 2:02 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7

On 3/4/2018 8:12 PM, David Fisher NX6D wrote:
I’m curious to know what will happen when someone wanders into these 
tests, without RC2, and tries to send one of the messages not used in 
these abbreviated sequences.  Will those callers be ignored?


Only Fox sends a new type of message -- that is, one not supported in WSJT-X
v1.8.0.

I hope it's clear in the FT8 DXpedition Mode User Guide
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fphysics.princeton.edu%2Fpulsar%2Fk1jt%2FFT8_DXpedition_Mode.pdf=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435%7C1%7C0%7C636558738863273348=Fv8YsdwGWJtpSR6%2FWEfmU20p4YKCftMbHMR1DPSlWWk%3D=0

... that Fox will respond only to

1. Initial calls like line 2 in the User Guide's example sequence (top of
page 2).  These messages must be received above 1000 Hz; and

2. Messages like lines 4 and 6, from stations to whom Fox has already sent a
signal report.  These must be received between 300 and 900 Hz.

     -- 73, Joe, K1JT


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! 
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdot=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435%7C1%7C0%7C636558738863273348=xGQwTM3BgptdcOi46oTsiKW94MZx7uTgvEU0CQhngRo%3D=0

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435%7C1%7C0%7C636558738863273348=IpyYm%2Fvh7eTF9ROKzkA4vD%2Fap0Q8FKMMfNoc8EpC8aI%3D=0


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdot=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435%7C1%7C0%7C636558738863273348=xGQwTM3BgptdcOi46oTsiKW94MZx7uTgvEU0CQhngRo%3D=0

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net

Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7

[David Fisher]

Joe



Thanks for the reply.  In the spirit of trying to make useful suggestions 
rather than just complaining, let me suggest that once 1.9 is released to the 
public, that some additional demonstrations of the new mode be conducted so 
that the public could get some practice with it before a real DXPedition starts 
using it.  Perhaps you have that in mind.  It will take a big public 
announcement, and a lot of them, to get the message across.



Dave / NX6D




From: Joe Taylor 
Sent: Monday, March 5, 2018 12:40:28 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7

Dave --

All understood.  Rest assured, we have already spent plenty of time
thinking about -- and testing -- the sort of complications you describe.

No doubt we will still have some surprises. Some will be ones we have
foreseen, others probably not.  That's precisely why we are doing more
testing!
-- 73, Joe, K1JT

On 3/5/2018 3:33 PM, David Fisher wrote:
> Jim has made the point I was heading towards.  Even when 1.9 is released
> publically, there will be plenty of users of older versions and some
> will jump into fray.  In a test, it’s not very likely there will be much
> QRM.  In the real world, when a rare DX is at stake, I expect it could
> be quite a mess.  Some will be transmitting on the DX frequency, some
> will be transmitting into the 300-900 Hz space, etc.  I’m simply trying
> to stimulate a little brainstorming about how this could go wrong and
> what could be done to mitigate it.  We’ve already seen lots of examples
> of people running old versions of the code, running RCs past their
> expiration date, etc.
>
> I’m not a purveyor of gloom and doom, far from it.  But it’s difficult
> to roll out a dramatically different version of the program once so many
> are running an older incompatible version.  And, even if they are
> running 1.9, how will they get the experience to use the new mode
> effectively?
>
> Dave / NX6D
>
> 
> *From:* James Shaver 
> *Sent:* Monday, March 5, 2018 11:09:37 AM
> *To:* 'WSJT software development'
> *Subject:* Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7
> It also might not be a bad thing if some well-meaning but otherwise
> uninformed ops running 1.8 wander into the "pileup" as it may help simulate
> real-world conditions where this may also happen with more frequency.
> Though they may not decode the "fox" I've seen any number of times where
> people will start calling a "DX" even though they can't hear them so I'd
> expect this will happen during the public test as word spreads.  It'll help
> add legitimacy to real-world QRM.
>
> Just my 2 cents, feel free to keep the change :)
>
> Jim S.
> N2ADV
>
> -Original Message-
> From: Joe Taylor [mailto:j...@princeton.edu]
> Sent: Monday, March 5, 2018 2:02 PM
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7
>
> On 3/4/2018 8:12 PM, David Fisher NX6D wrote:
>> I’m curious to know what will happen when someone wanders into these
>> tests, without RC2, and tries to send one of the messages not used in
>> these abbreviated sequences.  Will those callers be ignored?
>
> Only Fox sends a new type of message -- that is, one not supported in WSJT-X
> v1.8.0.
>
> I hope it's clear in the FT8 DXpedition Mode User Guide
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fphysics.princeton.edu%2Fpulsar%2Fk1jt%2FFT8_DXpedition_Mode.pdf=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435%7C1%7C0%7C636558738863273348=Fv8YsdwGWJtpSR6%2FWEfmU20p4YKCftMbHMR1DPSlWWk%3D=0
>
> ... that Fox will respond only to
>
> 1. Initial calls like line 2 in the User Guide's example sequence (top of
> page 2).  These messages must be received above 1000 Hz; and
>
> 2. Messages like lines 4 and 6, from stations to whom Fox has already sent a
> signal report.  These must be received between 300 and 900 Hz.
>
>  -- 73, Joe, K1JT
>
> 
> --
> Check out the vibrant tech community on one of the world's most engaging
> tech sites, Slashdot.org!
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdot=02%7C01%7C%7Cfd79ea2387714f9be0fa08d582cce425%7C84df9e7fe9f640afb435%7C1%7C0%7C636558738863273348=xGQwTM3BgptdcOi46oTsiKW94MZx7uTgvEU0CQhngRo%3D=0
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> 

Re: [wsjt-devel] Public test of FT8 DXpedition mode March 6-7

[Joe Taylor]

Dave --

On 3/5/2018 5:46 PM, David Fisher NX6D wrote:
... let me suggest that once 1.9 
is released to the public, that some additional demonstrations of the 
new mode be conducted so that the public could get some practice with it 
before a real DXPedition starts using it.  Perhaps you have that in 
mind.  It will take a big public announcement, and a lot of them, to get 
the message across.


Not sure why you would imagine we haven't been thinking about such 
matters for a long time already.


Detailed planning for FT8 started in August 2017 -- soon after FT8 was 
first becoming widely used.  We have been testing DXpedition Mode on the 
air, and fine-tuning it, since October, with a variety of test groups.
Our experience is that no potential Hound who reads and follows the 
published instructions has any trouble working a station acting as Fox.


To be sure, when "real DX" becomes involved we will have more 
well-behaved Hounds, generally far more QRM, and, yes, some 
not-so-well-behaved Hounds.  We have given a lot of thought to 
minimizing the undesired effects of these inevitable complications, and 
that thought is built into both the software and the instructions for 
its use.


Of course we will still have some surprises.  That's why we are 
conducting more tests and soliciting more widespread participation.


Feel free to run some tests on your own, if you wish, with a few 
buddies.  I don't think you'll find it difficult to be effective as 
either a Fox or a Hound.  hen you can help to instruct others, when 
operational questions arise.


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

[wsjt-devel] The native foxes and hounds are restless

[Julian VK4CMV]

Something interesting  up on my screen early one morning on 80m ... also
getting warnings from the new WSJT-X about maybe I should be turning on the
fox/hounds mode. Too sleepy to deal with it at that time of the day.

Looking forward to the tests - might get through on the 20m one ...
--
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] Audio input from RTP stream?

[Phil Karn]

How hard would it be for WJST to accept receive audio from a RTP (Real
Time Protocol) multicast network stream?

RTP is *the* standard for voice over IP (VoIP). It runs over UDP/IP,
usually as unicast IPv4 but also as multicast IPv4 or IPv6. It's just a
streaming protocol that identifies and sequence numbers packets. It can
carry any codec you want.

I've been writing my own SDR from scratch over the past year or so. A
core design feature is the use of IP multicasting for all inter-module
communications, e.g., I/Q sample streams, uncompressed PCM audio,
Opus-compressed audio, decoded digital data frames, hardware status,
metadata, etc.

I've found this to be remarkably versatile and practical. Any number of
receivers can listen to a multicast stream without any prior
arrangement. The various modules can be on the same system, on different
systems on the same LAN, or systems in different locations connected by
a multicast-capable IP network. Modules can be individually stopped and
restarted without killing others (though some real-time data will of
course be lost.)

My receiver outputs uncompressed audio as a standard RTP/UDP/IP
multicast stream containing mono or stereo 16-bit linear PCM audio at 48
kHz. To now get this into WSJT on OSX, I run my RTP receiver/player
program, intercept the OS X audio with Soundflower, and then tell WSJT
to take its input from Soundflower.

This sort of works, but it causes problems. You have to be careful to
keep system sounds out of Soundflower, and you can't run any unrelated
sound applications.

It would be great if WSJT could natively process an incoming RTP audio
stream without touching the local machine's audio subsystem. It would
not have to echo to the system audio output; if want to monitor it I can
simply run an instance of my RTP audio player that will join the same
multicast stream and WSJT doesn't need to know.

As a follow-on project, it would also be nice to give WSJT the option of
generating a RTP stream with transmit PCM audio.

I'm willing to do the work myself, but I'd like to know if anybody else
is already working on something like this, or if anyone has advice for
how to minimize my changes to the WSJT program structure. (I've not
looked at the source yet.)

73, Phil


--
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] The native foxes and hounds are restless

[charlie]

Hi Julian

I have seen the warning "Should you be in FT8 Dxpedition Hound mode" when
not set to Hound.

I can trigger this message using a Fox message including a hashed call eg

K1ABC RR73; W9XYZ 

It only appears, for me, when the correct Fox callsign is in the DX Call
box.  I guess this is a feature designed to help a Hound who has forgotten
to enter Hound, when already listening for an intended Fox.

After pressing OK to this warning, it decodes as if set to Hound, but
Hound does not appear checked in the Advanced settings window.

73

Charlie G3WDG

> Something interesting  up on my screen early one morning on 80m ... also
> getting warnings from the new WSJT-X about maybe I should be turning on
> the
> fox/hounds mode. Too sleepy to deal with it at that time of the day.
>
> Looking forward to the tests - might get through on the 20m one ...
> --
> 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] Audio input from RTP stream?

[Borja Marcos]

> On 6 Mar 2018, at 07:29, Phil Karn  wrote:
> 
> How hard would it be for WJST to accept receive audio from a RTP (Real
> Time Protocol) multicast network stream?
> 
> My receiver outputs uncompressed audio as a standard RTP/UDP/IP
> multicast stream containing mono or stereo 16-bit linear PCM audio at 48
> kHz. To now get this into WSJT on OSX, I run my RTP receiver/player
> program, intercept the OS X audio with Soundflower, and then tell WSJT
> to take its input from Soundflower.
> 
> This sort of works, but it causes problems. You have to be careful to
> keep system sounds out of Soundflower, and you can't run any unrelated
> sound applications.

Several years ago I did something of that sort using Quicktime Broadcaster and
Digital Performer. I was showing a friend how to have someone far away listen to
my mixing bus and it worked very well.

I used Jack OS X but I’m not sure wether it still works on Mac OS X It wasn’t
so bad in software compatibility (if I remember well we were keeping a voice
chat with iChat). Of course you had to be careful and make sure that stuff
like system sounds were routed to a different output but other than that it
worked.

https://en.wikipedia.org/wiki/JACK_Audio_Connection_Kit

It was several years ago but I think I remember that a couple of years
later I tried Soundflower and I had some problems with it. But it could be 
just the changes Apple had been making in Core Audio. 

In my case I was streaming stereo 24 bit @44.1 KHz audio and
meanwhile I was running Digital Performer mixing a multi track recording
(no more than eight tracks, that’s an advantage of jazz!). The machine
was a Power Mac G5 and I ran everything together (Digital Performer,
Quicktime Broadcaster and Jack OS X).

> It would be great if WSJT could natively process an incoming RTP audio
> stream without touching the local machine's audio subsystem. It would
> not have to echo to the system audio output; if want to monitor it I can
> simply run an instance of my RTP audio player that will join the same
> multicast stream and WSJT doesn't need to know.
> 
> As a follow-on project, it would also be nice to give WSJT the option of
> generating a RTP stream with transmit PCM audio.

That would be really awesome, defining some standard “audio bus” for 
radio applications. Making it multi platform and multi tooklit can be 
tricky, though. WSJT-X is based on Qt audio. But, what about other apps?

Maybe Jack (i see there is a Jack2 version and it supports Windows as well)
could work?

https://github.com/jackaudio/jackaudio.github.com

Sorry about being a bit vague, I haven’t looked at this for a long time!




Borja - EA2EKH



--
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] Public test of FT8 DXpedition mode March 6-7

[Borja Marcos]

> On 5 Mar 2018, at 00:43, Joe Taylor  wrote:
> 
> All participating stations must use program version WSJT-X v1.9.0-rc2. If you 
> don't yet have it, download links are available here:
> https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

I won’t be able to take part but maybe I have something useful to contribute. 
My cluster is storing Pskreporter events again. I have
historical data since May with some small gaps and a one month long gap for 
January 2018. 

In case it’s useful to study the tests ping me off list and I can arrange 
access to the cluster and Kibana (the visualization program).

73,


Borja / EA2EKH





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