Seems like the best way then would be if they maintain their own channel, as is
the case with CHIRP, VirtualBox, and countless other applications. Then I
could add that source and the package manager would use the more up to date
packages seamlessly. The packages are already being built for a
FWIW .. it affects the other program as it turns up the MiC/Line In to
100%, so no matter what program uses that audio it will be at 100%
Neil, KN3ILZ
On 5/10/2019 11:06 AM, Enrique Scheuer wrote:
Hello Mike,thanks Im already aware but it doenst mention that it aslo
affects JTDX .
73 de
> On May 10, 2019, at 09:04, Jason Peardon wrote:
>
> Lower it until the scale in WSJT-X is around 60% consistently.
That should be 30 on the audio meter in WSJT-X when tuned to a clean frequency
and just listening to white noise.
Gary - AG0N
Re: Adam Bartlett 2019-05-10
> One of the challenges of automatic updating is package managers and such on
> the Linux side are often generations behind (not a big deal, but if a user
> installs Ubuntu, types "apt install wsjtx" and they still have 1.x in their
> repo it's going to confuse them)
One of the challenges of automatic updating is package managers and such on
the Linux side are often generations behind (not a big deal, but if a user
installs Ubuntu, types "apt install wsjtx" and they still have 1.x in their
repo it's going to confuse them) and trying to deal with those can be
Hello Mike,thanks Im already aware but it doenst mention that it aslo
affects JTDX .
73 de Enrique
PY2CP
Em sex, 10 de mai de 2019 às 11:42, Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> escreveu:
> Known bug
>
> http://physics.princeton.edu/pulsar/k1jt/Reported_bugs.txt
>
>
If the program on startup finds a valid Internet connection, then check for
an update automatically. If one is available, download it, or at least
supply a link to the file, and THEN allow the user to install (or delete)
it as they feel. Make it keep bugging the user on startup of WSJTx until
If you are running Windows 10:
Right click the speaker icon in the bottom right corner down by the clock
Select: Open Sound Settings
In the new window that opens find "Input" where the microphone is listed
Below that you should see Device Properties; click this
In the new dialog box that opens
Known bug
http://physics.princeton.edu/pulsar/k1jt/Reported_bugs.txt
de Mike W9MDB
On Friday, May 10, 2019, 9:27:57 AM CDT, Enrique Scheuer
wrote:
Hello sirs,
After installing WSJT-X rc5 the my JTDX 135 audio input also jumped to 100 pct
and I am not suceeding to fix it. Any
Hello sirs,
After installing WSJT-X rc5 the my JTDX 135 audio input also jumped to 100
pct and I am not suceeding to fix it. Any suggestion?
73 de Enrique
PY2CP
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Backwards compatibility is a thing ...
Also, if the new version of the software knows how to decode an older
encoding, you already have an implied version number.
It's not like this takes eons to decode, nothing wrong with trying several
times, newest version first, next version next and so on.
The other problem with an expiration, what happens when the devs forget to push
a new version on schedule?
Don’t think it could happen? Would you believe last week that very thing
happened with Mozilla Firefox on a security certificate breaking things for
everyone globally that used the
Even easier than modifying the hosts file, I can just change the system date to
get around an offline check.
-Matt / KK4NDE
From: rjai...@gmail.com [mailto:rjai...@gmail.com]
Sent: Thursday, May 09, 2019 11:21 PM
To: WSJT software development
Cc: Gustafson Neil
Subject: Re: [wsjt-devel]
Hi Onno,
>A better idea is to include a protocol version number in the QSO information,
>that way both sides have a chance to alert the operator.
A nice idea, but that information needs to be sent using the lower layer of the
previous protocol version….
73, Reino, oh3ma
I would be against a kill switch if it can't phone home as this would
restrict people to only using the program if they were online. This would
stop people using it if they were located somewhere where there was no
internet access.
73
Jonathan
GI7KMC
On Fri, 10 May 2019 at 04:23,
A better idea is to include a protocol version number in the QSO
information, that way both sides have a chance to alert the operator.
I should also point out that in ICT data exchange it's common practice to
include a version in the meta-data to prevent exactly this issue.
--
finger painting on
16 matches
Mail list logo
