Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-27 Thread Black Michael via wsjt-devel
Actually CW operators use apriori operation all the time. When you're in a poor signal CW QSO with a dxepedition or such all you listen for is your call sign -- not theirs.  You assume (apriori) that they are the ones responding and you have a sequence you follow so you just continue. Mike

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-27 Thread Glenn Williams via wsjt-devel
- From: Glenn Williams via wsjt-devel [mailto:wsjt- de...@lists.sourceforge.net] Sent: Saturday, January 27, 2024 1:12 AM To: wsjt-devel@lists.sourceforge.net Cc: Glenn Williams Subject: Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45 So, Do you mean that a priori information is used

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Jim Shorney via wsjt-devel
I would agree to that. I saw one with a P7 call yesterday that looked quite legitimate. My finger wanted badly to click on it but I said "no, wait...". Never saw it again. Despite what the nay-sayers claim, FT modes do require some human thought to get the best out of them. :) 73 -Jim NU0C

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Reino Talarmo via wsjt-devel
age- > From: Glenn Williams via wsjt-devel [mailto:wsjt- > de...@lists.sourceforge.net] > Sent: Saturday, January 27, 2024 1:12 AM > To: wsjt-devel@lists.sourceforge.net > Cc: Glenn Williams > Subject: Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue > 45 > > S

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Glenn Williams via wsjt-devel
Message- From: Glenn Williams via wsjt-devel [mailto:wsjt- de...@lists.sourceforge.net] Sent: Friday, January 26, 2024 6:43 PM To: wsjt-devel@lists.sourceforge.net Cc: Glenn Williams Subject: Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45 I am reporting here another issue with my TX5S QSO

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Adrian via wsjt-devel
: Glenn Williams via wsjt-devel [mailto:wsjt- de...@lists.sourceforge.net] Sent: Friday, January 26, 2024 6:43 PM To: wsjt-devel@lists.sourceforge.net Cc: Glenn Williams Subject: Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45 I am reporting here another issue with my TX5S QSO and the FT8

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Uwe, DG2YCB via wsjt-devel
Okay, then let's continue to observe whether we can find a pattern under which exact conditions the unwanted effect occurs. As said, the F/H-related part of the code in v2.7.0-rc3 (regular version) is identical to the i+ version. This should therefore make no difference. 73 de DG2YCB, Uwe

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Reino Talarmo via wsjt-devel
Cc: Glenn Williams > Subject: Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue > 45 > > I am reporting here another issue with my TX5S QSO and > the FT8 windows that happened last night. (Previous > report is under "Subject: > [wsjt-devel] skips RX frequency window (bug?) ws

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Scott Armstrong via wsjt-devel
I saw the same behavior over the past few days while working TX5S. I am running 2.7.0-rc3 (regular version) not the improved version. My first thoughts were that it was due to the Rx green goalpost in the waterfall being over a different stream than the one sending the response. I have no means

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Black Michael via wsjt-devel
#1 That's a false decode (detectable as a funky message) #2 Not on the Fox offsets.  Fox never transmitted at 474 Mike W9MDB On Friday, January 26, 2024 at 11:19:40 AM CST, Glenn Williams via wsjt-devel wrote: I am reporting here another issue with my TX5S QSO and the FT8 windows

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Black Michael via wsjt-devel
No...it just appends the file.  Size doesn't matter as the saying goes... Mike W9MDB On Friday, January 26, 2024 at 11:10:08 AM CST, Glenn Williams via wsjt-devel wrote: So, Once upon a time I asked a question and the gurus had an answer (V2.2.2 I think). My question was about

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Glenn Williams via wsjt-devel
I am reporting here another issue with my TX5S QSO and the FT8 windows that happened last night. (Previous report is under "Subject: [wsjt-devel] skips RX frequency window (bug?) wsjtx-2.7.0-rc3".) I am also NOT confirmed in ClubLog! My screenshots with iPhone are in

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Glenn Williams via wsjt-devel
So, Once upon a time I asked a question and the gurus had an answer (V2.2.2 I think). My question was about "how does FT8 keep huge files open and still keep up with the band activity while updating huge files". Today's question is about that. ALL.TXT has grown really large. Is there a

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Gary Rogers via wsjt-devel
I had the same thing happen as with Fred. Improved rc3 for Mac M1Sent from my iPhoneOn Jan 26, 2024, at 11:00 AM, Fred Price via wsjt-devel wrote: Screenshot of it happening to me with TX5S.  On Jan 26, 2024, at 10:51 AM, Uwe, DG2YCB via wsjt-devel wrote:  But it worked also when I

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Uwe, DG2YCB via wsjt-devel
But it worked also when I set my Rx QRG manually 275 Hz next to the Fox offset. 73 de DG2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg2...@gmx.de Info: www.qrz.com/db/DG2YCB Am 26.01.2024 um 16:44 schrieb Black Michael: Perhaps

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Black Michael via wsjt-devel
Perhaps when the fox offset for your callsign changes? I think I've seen that. On Friday, January 26, 2024 at 09:15:37 AM CST, Uwe, DG2YCB via wsjt-devel wrote: Hi Rich, Last night I ran some tests with our good old standard WSJT-X (latest code) using three instances all

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Uwe, DG2YCB via wsjt-devel
Rick, Just completed the same test with the i+ 2.7.1-devel "240202" code. Identical results as with our standard WSJT-X v2.7.0-rc3 (not surprising, since this part of the code is identical). Not a single issue, all messages to the own callsign were displayed correctly in the right window. So, I

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Uwe, DG2YCB via wsjt-devel
Hi Rich, Last night I ran some tests with our good old standard WSJT-X (latest code) using three instances all connected via virtual audio.  One in FT8 Fox mode and the other two in FT8 Hound mode. Then I simulated just such QSO situations, but each time the reports appeared in the right-hand

Re: [wsjt-devel] wsjt-devel Digest, Vol 119, Issue 45

2024-01-26 Thread Rich - K1HTV via wsjt-devel
I have noticed the same thing at times while running as Hound in F/H where the report from the Fox will appear in the Band Activity column but not in the Rx Frequency column.I am presently running the "WSJT-X V2.7.1 devel 231031 Improved PLUS" version. Also, when the "Start new period decodes at