Hi Jerry,
I guess you attached them to a post to this list, that will exceed the
attachment size limit. It is easier to copy the file(s) to a cloud
storage service and then just post a link to them here. Dropbox, Google
Drive, One Drive, ... there are many you can use for free. If you can't
Bill,
I uploaded the WAV files and the moderator needs to review them..
KI6RRD, Jerry
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Monday, December 23, 2019 3:13 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Strange Even/Odd frame
On 26/12/2019 17:40, DX Jami via wsjt-devel wrote:
My point is WSJT-X should allow "non-standard" call signs.
Danny,
WSJT-X goes to a lot of trouble to support "non-standard" callsigns, but
there is no free lunch. The non-standard callsigns supported by WSJT-X
in MSK144, FT4, and FT8 modes
Thanks Saku. I understand the work-around and use various versions myself.
My point is WSJT-X should allow "non-standard" call signs. Those non-standard
calls are only non-standard for WSJT-X and A-OK for the rest of the ham radio
world. Many DXpeditions have similar problems as does
On 26/12/2019 17:22, Steven Franke via wsjt-devel wrote:
I can tell from the results that the Rx frequency was probably set to
something near 1500 Hz.
Hi Steve & Mike,
the default Rx offset when running jt9 stand-alone is 1500 Hz, you can
use the '-f' command line option to experiment and
Mike,
>
> Ok...not as insane as I thought I was…
See my annotations to your list of decodes, below, in red. I can tell from the
results that the Rx frequency was probably set to something near 1500 Hz. I can
assure you that there are only 3 passes (see my previous post for the
definition of
DX Jami via wsjt-devel kirjoitti 24.12.2019 klo 15.26:
Another shortfall with non-standard calls is signing like me -
W4/AH6FX. The "real estate" shortfall does not allow passing my grid,
so that is very bothersome to some folks.
Hi!
There is a good practice for this used by F5MYK/MM. For
Looking at Steve's explanation it appears we can get up to 4 passes -- the
additional pass for the multiple methods on each main pass.Sound right?
Mike
On Thursday, December 26, 2019, 11:07:24 AM CST, Black Michael
wrote:
Ok...not as insane as I thought I wasthe XYL will be
Ok...not as insane as I thought I wasthe XYL will be happy with that :-)
I'm debugging this on a friend's computer.
Here's a dropbox link to the WAV file that produces 4 passes as can be seen
below which I've put in bold and
Hi Steve, That was a great explanation. Thank you. Have a happy and healthy
new year. 73, Sam W2JDB
-Original Message-
From: Steven Franke via wsjt-devel
To: WSJT software development
Cc: Steven Franke
Sent: Thu, Dec 26, 2019 10:24 am
Subject: Re: [wsjt-devel] 3 passes??
Mike and
Now I'm trying to figure out why I thought 3 passeswas debugging a problem
with JTAlert so I think my brain must have been distracted
Arrghhh..hate when that happens
Mike
On Thursday, December 26, 2019, 09:26:01 AM CST, Steven Franke via
wsjt-devel wrote:
Mike and Bill,
Josh,
May I suggest that you monitor your processor (CPU) utilization using
the Windows Resource Monitor.
You may find that if the total CPU usage is near 100% when a receive
period starts that there are no decodes and no .wav file is saved (
temporary creation not started ?? ) .
AL, K0VM
Mike and Bill,
WSJT-X does three decoding passes, where a “pass” consists of the following
steps:
1. do spectral analysis and make a list of likely FT8 signal candidates, sorted
in order of increasing offset frequency. If a candidate is found near the
current Rx frequency, put that candidate
Mike,
I don't see any evidence of a 4th decoding pass in the list of decodes
you provided in your OP. What makes you think there is such a pass?
I see a single decode at 1824 Hz which I assume is at or very near you
currently set Rx audio offset, I see 24 decodes in ascending frequency
OK...let's call it 4-pass thenI wasn't including the rx offset as pass#1.
I didn't think anything was happening after what you're calling the 3rd pass
occurs...but 3 more decodes show up.So that's the AP or some decodes are still
being worked on after the 3rd pass?
Mike
On Thursday,
On 26/12/2019 14:36, Black Michael via wsjt-devel wrote:
Is there a 3-pass going on now in 2.1.2?
I'm seeing 3 passes from the decodes.
de Mike W9MDB
Mike,
this is nothing new. The first decode attempt is at the Rx audio offset,
then another across the passband, and a third after
Is there a 3-pass going on now in 2.1.2?I'm seeing 3 passes from the
decodes.de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Consider transitioning to FLRig -- actively supported and can set up with all
sorts of programs talking to it either via rigctld or rigctlcom
I haveWSJT-XLog4OM3 local utilitiesN1MMFLDigi
All working at once talking to the rig.
WSJT-X -> FLRigLog4OM -> rigctld -> FLRigLocal utils -> both waysN1MM
OK. Thanks a lot for the clarification, Bill. And by the way, thank you for
your excellent support. Let me extend my wishes for a peaceful and merry
Christmas to you and the rest of the development team!
Tom OH6VDA
> 26. des. 2019 kl. 15:05 skrev Bill Somerville :
>
> On 25/12/2019 17:57,
On 25/12/2019 17:47, Josh Rovero wrote:
Bill, et al,
Windows 10 Home, 64-bit, Version 1909, Build 18363.535
WSJT-X 2.1.1
When I first start 8 x WSJT-X instances on this i7 PC, they all decode
FT8 frames and save WAV files for every time segment. Each WAV file
is 352K in size.
After some
On 25/12/2019 17:57, Tom Ramberg via wsjt-devel wrote:
Does WSJT-X support Omnirig 2.0?
Tom OH6VDA
Hi Tom,
the first two rigs are supported by the existing Omni-Rig support in
WSJT-X. It is unlikely that full support for all four rigs will be added
for the following reasons:
1) The
21 matches
Mail list logo
