> 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
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 fea
> 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 a
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 sequen
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 ...
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. Perha
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
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
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" wil
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
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
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
te
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
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 o
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
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,
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
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
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
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:4
20 matches
Mail list logo