On 25/11/2018 01:51, Dana Myers wrote:
On 11/24/2018 5:04 PM, Bill Somerville wrote:
You can resample the 12kHz WSJT-X .WAV files down to 8kHz (there are
several tools that can do that) degrade them then resample back to
12kHz as a work around.
Audacity has long been my tool of choice for
On 11/24/2018 5:04 PM, Bill Somerville wrote:
You can resample the 12kHz WSJT-X .WAV files down to 8kHz (there are several tools that can do that) degrade them then resample
back to 12kHz as a work around.
Audacity has long been my tool of choice for that. Not really sure I'd say
"degrade",
On 25/11/2018 00:44, Dana Myers wrote:
On 11/24/2018 4:14 PM, Bill Somerville wrote:
The only way to check the sensitivity of the 75-bit and 77-bit
decoders on air is to do a controlled test.
Exactly. A *controlled* test, that is reproducible. Let me introduce
an invaluable
tool for
On 11/24/2018 4:14 PM, Bill Somerville wrote:
The only way to check the sensitivity of the 75-bit and 77-bit decoders on air
is to do a controlled test.
Exactly. A *controlled* test, that is reproducible. Let me introduce an
invaluable
tool for this:
On 24/11/2018 23:56, Stephen Ireland wrote:
Jesus,
I am making similar observations – well its hard to observe at the
moment as I am seeing little here in VK; issues are beyond propagation
as v1 signals boom in (especially for some reason from EA).
One must always delete the wsjtx.ini when
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] Sensitivity problem when decoding v2.0.0-rc4
Good afternoon, even if it's repetitive, I'll say again that after several
days, I look for stations by the different bands, I only decode very few ...
understandable that there are not many that
Good afternoon, even if it's repetitive, I'll say again that after several
days, I look for stations by the different bands, I only decode very few
... understandable that there are not many that come out in 77 bits, until
here, it has its logic .. .
However, before, as a rule, to work European
