Hi Joe
Section 8.1
I think either the notes in Astro window or the user guide text could
benefit from an explanation of how to enter sked frequency directly into
band edit box.
The frequency entered has to be in the form nnnk (eg 225k) which puts sked
frequency at band edge + 225kHz.
Maybe a s
>From running the samples...
MSK144 &
QRZ64 :
JT4 $
ISCAT *
Mike W9MDB From: "Laurie, VK3AMA"
To: WSJT software development
Sent: Wednesday, October 26, 2016 4:03 PM
Subject: [wsjt-devel] UDP Mode utf8 values
Can someone provide me with a link to where the UDP Mode values are defin
In reference to the RRR patch that was previously disapprovedwhat about
making this an option with "Prompt me to log QSO" as a tristate checkbox?
If I make such a patch would it be considered for inclusion? Otherwise I won't
waste my time.
Index:
mainwindow.cpp==
Hi Joe
Yes, fine now.
In section 6.5, file path needs changing:
"navigate to ...\save\samples\130610_2343.wav"
I guess this result is with two pass decoding selected as specified
earlier in the tutorial. I kept getting 18 decodes, but noticed my
erasure patterns and aggressive decoding level w
Can someone provide me with a link to where the UDP Mode values are
defined? There is nothing in the NetworkMessage.hpp fileor in the user
guide.
Currently I am aware of "@" = "JT9" & "#" = "JT65". What are the other
defined designators and their corresponding human-readable mode strings?
de
On 27/10/2016 2:33 AM, Black Michael wrote:
Perhaps more approriately
JT-Alert-X, by VK3AMA, is currently only available for Windows. A
re-write is underway for cross-platform support and planned for 2017.
de Mike W9MDB
Also, it hasn't been called JT-Alert-X for a very long time. The h
Many thanks to all those providing suggestions for improvements to the
WSJT-X User Guide. Your comments are greatly appreciated!
-- Joe, K1JT
--
The Command Line: Reinvented for Modern Developers
Did the resurge
Hi Charlie,
> The two JT4 files are reported by Windows as 52s in length, compared to
> others that are 59s. Also at a lower bitrate (maybe WSJT10 recordings?).
Correct. This has now been taken care of.
> Are you updating online user guide as you go (at the URL you gave out), or
> are the edits
HI Joe
>
> Better still, find out why the files don't work with *Decode at 52s*
> checked. This should not happen. I will fix...
The two JT4 files are reported by Windows as 52s in length, compared to
others that are 59s. Also at a lower bitrate (maybe WSJT10 recordings?).
Are you updating onl
Hi Charlie,
> Mystery solved re non decode of JT4 examples.
>
> They decode fine if decode at 52s is *not* checked.
>
> Given JT4 is intended for EME, it may be better to choose files that work
> with decode at 52s checked.
This anomaly is fixed in revision 7236.
-- Joe
Perhaps more approriatelyJT-Alert-X, by VK3AMA, is currently only available
for Windows. A re-write is underway for cross-platform support and planned for
2017.
de Mike W9MDB
From: Parker Dinkins
To: wsjt-devel@lists.sourceforge.net
Sent: Wednesday, October 26, 2016 8:06 AM
Subje
12. Cooperating Programs
JT-ALERT-X, by VK3AMA, is available only for Windows.
-
The hyperlink for "JT-ALERT-X" is not correct.
The link should be "hamapps.com".
In addition, the sentence should read
JTAlert, by VK3AMA, is available only for Windows.
---
Parker W5ADD
--
Hi Charlie,
Thanks for catching this.
> Mystery solved re non decode of JT4 examples.
>
> They decode fine if decode at 52s is *not* checked.
>
> Given JT4 is intended for EME, it may be better to choose files that work
> with decode at 52s checked.
Better still, find out why the files don't wor
Hi Joe
Mystery solved re non decode of JT4 examples.
They decode fine if decode at 52s is *not* checked.
Given JT4 is intended for EME, it may be better to choose files that work
with decode at 52s checked.
Charlie
> Hi all,
>
> Slowly but surely, a respectable User Guide for WSJT-X v1.7 has b
Hi Joe
I have now been able to decode the two JT4 sample files. I am not sure
why I had difficulty before.
Charlie
> Hi all,
>
> Slowly but surely, a respectable User Guide for WSJT-X v1.7 has been
> taking shape. Much material has been added over the past week or so --
> and quite a bit more,
Hi Rex and Bill,
Thanks for the corrections to the User Guide text concerning
*Allow Tx frequency changes while transmitting*. I should have caught
that... and will fix it.
-- Joe
--
The Command Line: Reinvent
On hamlib you can just do a "git pull" to see if there any updates. They don't
happen very often.So if it's up-to-date no rebuild is needed.
de Mike W9MDB
From: Bob KD7YZ
To: WSJT software development
Sent: Wednesday, October 26, 2016 7:32 AM
Subject: Re: [wsjt-devel] building haml
On 26-Oct-16 0832, Bob KD7YZ wrote:
> also, I didn't see a 'making elecraft" or some such .. I have K3 .. do
Belay that question. I just saw this go by on screen
-
CC ts440.lo
CC ts940.lo
CC ts711.lo
CC ts811.lo
CC r5000.l
On 26-Oct-16 0827, Bob KD7YZ wrote:
> I started the build-hamlib3 process prior to doing a build-wsjtx .
>
> Do I need to rebuild this if I see already up to date ?
>
also, I didn't see a 'making elecraft" or some such .. I have K3 .. do
I still need hamlib?
--
73,
Bob KD7YZ
I started the build-hamlib3 process prior to doing a build-wsjtx .
Do I need to rebuild this if I see already up to date ?
what I saw in the cmd window
---
Hi Rex & Joe,
comments in line below.
On 26/10/2016 03:23, Rex Moncur wrote:
Section 8.1 has the following statement:
If you will use automatic Doppler tracking and your radio accepts
frequency-setting commands while transmitting, check *Allow Tx
frequency changes while transmitting*. *Tran
Hi Joe
I've got up to Section 6.3.
I think before this, perhaps at the beginning of that section, there needs
to be an instruction to download the Samples, as otherwise the user won't
have them, together with a stepwise method of how to do it (ie click the
appropriate box to start the download).
22 matches
Mail list logo
