Re: [wsjt-devel] Fwd: Enhancement suggestion - 30 second cycles

[jbozell via wsjt-devel]

Moderators! Help! Please!

While I’ve found this to be royally entertaining, this equine has been beaten, 
flayed, left for dead, reanimated and zombified. Perhaps I’m overly naïve, but 
does this discussion of “split” really cause the amount of confusion implied 
except among the principals involved in the discussion? Is there anyone who has 
gotten to the description of “split” in the manual and said “Oh no, no, no. No 
way...I don’t get it so I’m not going to use FT8”??

Joe/WB0CDY

From: Phil Williams via wsjt-devel 
Reply-To: WSJT software development 
Date: Monday, May 8, 2023 at 11:28
To: WSJT software development 
Cc: Phil Williams 
Subject: Re: [wsjt-devel] Fwd: Enhancement suggestion - 30 second cycles

Gah! I am out of here!
Phil de W1ZOT

On Mon, May 8, 2023, 13:11 Adrian via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net>> 
wrote:

On 9/5/23 02:49, Jim Brown via wsjt-devel wrote:
> #1 is hardly a benefit,


Why not, utilizing a gap at 100Hz or 2900Hz is very useful and effective
with split.


> #3 is bogus.

How would you know ? You lack the technical ability..


> #2 is a side benefit, but VERY secondary, and not the fundamental
> purpose of the practice.

Absolute BS for the same reason for #1 I used to think you knew what you
were talking about,..


Who cares about you or your 70 yr old history, old dogs can't learn new
tricks ?

Mike makes excellent points, which you fail to comprehend.

The harmonic prevention title is ridiculous, keep it simple like "Signal
Quality"


vk4tux





___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX

[jbozell via wsjt-devel]

Well! This seemingly innocuous (but useful) thread has suddenly gotten much 
more interesting. Popcorn please...who has the square for the first person to 
say “if you don’t like it, scroll down”? 

73,

WB0CDY

From: Paul Randall 
Reply-To: WSJT software development 
Date: Wednesday, August 19, 2020 at 3:17 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX


[External Email]
Actually, NO.
I've asked stupid questions on here, been pointed at the answer elsewhere and 
regretted my lack of "go find it".
What I can say is I didn't make my questions into a boxed set, to be enjoyed 
for a whole season.
If you've nothing better to do it may be a distraction but this forum is 
purposed for "WSJT Software development"
WSJT software allows us all to use some extremely clever turnkey signal 
processing software to make contacts on almost every band with potentially 
minimal equipment. It does however still require operators to have a tad more 
than minimal "pizzaz!"

A while back I saw CQs from (bogus) T3ST (bogus) - I'm sure I could have 
complained here "why did I see this?" and who could have known this was BOGUS 
(bogus callsign) BOGUS.  T3ST? who could have guessed? BOGUS

So, if you are operating CW or SSB or AM or FM or RTTY or anything else, and 
you hear a BOGUS (bogus) callsign, please don't expect your morse key, or 
electronic keyer, or balanced modulator, or any other modulator, to remove from 
you the need to identify the callsign as BOGUS (bogus) or prevent you from 
replying.

WSJT software in conjunction with PSKReporter has revolutionised our view of 
LF, VHF and UHF propagation. I worked Falklands on top band! My neighbour was 
able to record transmissions from D4VHF Cape Verde on 2M for almost every day 
in June, a path length equivalent to Europe - North America. I personally 
worked D4VHF on 70cm twice in July. Transatlantic path length on 70cm??? Really?

Let's keep this channel open and clear for input to the software development 
team for that purpose - software development, also keep in mind WSJT software 
has a specific purpose and is not intended to be a "go everywhere, do 
everything" answer for every possible scenario you might experience. Licensed 
operator is still required.

Maybe a lot of these posts might be better sent to a WSJT user forum, where 
operators can exchange experiences and gain understanding.

So,  I echo the OMs intention, let's rejoice in asking questions, but please 
re-consider the bandwidth you are occupying, is it appropriate or perhaps 
better elsewhere?

My 2p worth

Paul G3NJV






From: Carey Fisher 
Sent: 19 August 2020 20:36
To: WSJT software development 
Subject: Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX

I find the discussion interesting.
73, Carey, WB4HXE

On Wed, Aug 19, 2020 at 2:42 PM Gary McDuffie 
mailto:mcduf...@ag0n.net>> wrote:

> On Aug 19, 2020, at 02:21, Stephen VK3SIR 
> mailto:vk3...@hotmail.com>> wrote:
>
>
> --
>
> Why has the stream been decoded (good) and the logic allowed it to be 
> identified – displayed - as coming from Morocco (bad)? The station should not 
> display that it has come from Morocco in the first place as the call violates 
> the rules of callsign structures for that DXCC entity. That is the real point 
> I am making here !
>
> —
>

Good grief!  Can this thread not die?  If you don’t know the call and it looks 
bogus (yes it does) why are you even looking at it?  Dimiss it and move on.  
There is supposed to be an operator at the keyboard to interpret these things.

Gary - AG0N

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Carey Fisher
careyfis...@gmail.com

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel