"That's ridiculous. A "block" wouldn't keep a station from transmitting,
just from being displayed. Can't you just ignore it?"
Not easy to ignore when all callers are displayed in Rx frequency window. A
large part of this problem would be fixed by making the RX frequency window
display only cal
> On Dec 2, 2019, at 19:57, Carey Fisher wrote:
>
> That's ridiculous. A "block" wouldn't keep a station from transmitting, just
> from being displayed. Can't you just ignore it?
Exactly. Blocking your program from showing him won’t do a thing about the way
his signal affects your receiver
If he's not tripping my Call First so I can use the program as it was
designed, I don't give a damn what he's doing... Ron, WV4P
On Tue, 3 Dec 2019 at 10:51, Gary McDuffie wrote:
>
>
> > On Dec 2, 2019, at 19:57, Carey Fisher wrote:
> >
> > That's ridiculous. A "block" wouldn't keep a station f
Hi Bill and all,
First, thank you all for your support, it is greatly appreciated!
I think I found the source of the "noise" problem (however the "no audio"
problem still seems to be a mystery for me and many others).
what I forgot to mention was that I'm also using JTAlert with WSJT-X. It
app
That is being addressed in the next release of JTAlert.
#1 It will no longer allow use of the default sound device.#2 It will warn you
if the device changes
That should cover most bases.
de Mike W9MDB
On Tuesday, December 3, 2019, 11:36:15 AM CST, Frederic Beaulieu
wrote:
Hi Bill a
On 03/12/2019 14:00, Frederic Beaulieu wrote:
I'm still a little bit puzzled regarding the "Windows 10 64-bit audio
mixer" since a lot of applications seem to appears in it without valid
reason. If someone could produce a systematic procedure to avoid
sending non-related audio to the radio spea
That's an absolutely terrible idea unless it was purely an option. When
I have several callers I queue up the next one in the messages boxes if
I'm confident the station in QSO is sending me his final 73. I am then
able to answer the next station immediately upon conclusion of the QSO
and I
The point is that you said you needed a block to prevent the impact of
an unwanted caller on your receiver. You just made that up.
The program was designed to require you to actually be an operator,
which is why you have to enable each QSO instead of it being fully
robotic. "Call 1st" is m
Dave, with all due respect, maybe you need to read the thread again... You
are going off on wild tangents in your attempt to discredit and trash talk
every operator you can.
The Reason this is needed is to block Lids from tripping Call First, and or
to prevent them from calling you at all. Maybe a
On 12/3/2019 10:11 AM, David Gilbert wrote:
find it ridiculous that people smart enough to get a license
Sadly, too many did nothing more than memorizing answers to multiple
guess questions, not bothering to study the concepts behind the questions.
73, Jim K9YC
Not so. Any of it.
I've made over 2,000 FT8/FT4 contacts (over 130 countries) in about
three months time and the only ones that weren't DX were the ones that
called me. I tail end DX stations for many of my contacts, but when I
call CQ DX I have zero problem ignoring the persistent statesid
David,
As I suspected you are a casual user, hence why you are not able to
comprehend the benefits. For Comparison, since you brought it up..Many
weeks I was doing 1500 + Q's in FT-8 only last year during the grid chase.
I was on the FT-4 Alpha Test Team and I won First Place World in the last
FT
Amazing how those who don't see a need for a new option have their
opinions and reflect only a view from their use of the software. Again,
we need to think and view this issue from the operator's point of view
that is located in remote DX wanted locations, and end up in a pile-up.
Mostly thes
W9MDB wrote:
I'm all ears for opinions from operators who have had a call pileup on them.
I've been a ham since 1955, General in '56, Extra '59. I've always been
primarily a CW op, mostly contesting and chasing DX. I've been the guy
on the DX end of pileups working CW in a major contest, no
YES! This is quite important, and something that Elecraft got right in
the K3 from the very beginning (2008). When you switch to digital modes,
the equalizer is bypassed and processing is turned off. They also tell
you how to set audio drive level so that ALC is disabled.
73, Jim K9YC
On 12/
It's not a lockout file.
The idea is very simple.
Right now call first always picks the 1st decode...ergo the problem
So the idea is that once a call is worked it gets put in a list (doesn't matter
whether or not you log it). The call first logic checks the list and ignores
anybody in it.If
16 matches
Mail list logo
