Re: [wsjt-devel] AGC affecting SuperFox decoding #FH

2024-09-28 Thread Bill Barrett via wsjt-devel
tnx Jim-

Bill
W2PKY

On Sat, Sep 28, 2024 at 10:52 AM James Shaver (N2ADV) via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> This, IMO, is the best answer. I know that humans like
> one-size-fits-all/blanket answers but, realistically, the only
> one-size-fits-all answer is: it depends.
>
> 73,
>
> Jim S.
> N2ADV
>
> On Sep 28, 2024, at 10:16 AM, Bill Barrett via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> 
> Perhaps a message to the user:
>
> "Consider experimenting with AGC settings for best SF decoding"
>
> Bill
> W2PKY
>
> On Sat, Sep 28, 2024 at 10:07 AM 5p1kzx via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>> Hi all
>> Sometimes AGC is usefull and other times AGC off is better. It has to
>> decided by the user and not by the software. So far I haven't had any
>> problems in decoding any SF signals if they  were over -16dB in snr. Condx
>> ain't static It's dynamic so one have to play with
>> AGC/Preamp/Filter/ATT/Notch/Band-
>> Pass to get the best decode. No settings will work every time. One has to
>> take the time to learn what ones radio does with different settings. I
>> spend a lot of times playing with the settings when k8k was operating from
>> American Samoa and that experience came handy when hunting N5J🙂
>>
>> 73 de 5p1kzx
>>
>>
>>
>> Sendt fra min Galaxy
>>
>>
>>  Oprindelig besked 
>> Fra: Christoph Berg via wsjt-devel 
>> Dato: 28.09.2024 14.29 (GMT+01:00)
>> Til: Black Michael , WSJT software development <
>> wsjt-devel@lists.sourceforge.net>
>> Cc: Christoph Berg 
>> Emne: Re: [wsjt-devel] AGC affecting SuperFox decoding #FH
>>
>> Re: Black Michael via wsjt-devel
>> > We need to do some testing but I'm considering changing Hamlib to put
>> all rigs on FAST AGC (if AGC is not OFF) for WSJT-X operation.  So a
>> setting of medium or slow would get changed to fast.
>>
>> That sounds like it should be done by wsjtx, not hamlib.
>>
>> 73,
>> Christoph DF7CB
>>
>>
>> ___
>> 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
>>
> ___
> 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
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] AGC affecting SuperFox decoding #FH

2024-09-28 Thread Bill Barrett via wsjt-devel
Perhaps a message to the user:

"Consider experimenting with AGC settings for best SF decoding"

Bill
W2PKY

On Sat, Sep 28, 2024 at 10:07 AM 5p1kzx via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Hi all
> Sometimes AGC is usefull and other times AGC off is better. It has to
> decided by the user and not by the software. So far I haven't had any
> problems in decoding any SF signals if they  were over -16dB in snr. Condx
> ain't static It's dynamic so one have to play with
> AGC/Preamp/Filter/ATT/Notch/Band-
> Pass to get the best decode. No settings will work every time. One has to
> take the time to learn what ones radio does with different settings. I
> spend a lot of times playing with the settings when k8k was operating from
> American Samoa and that experience came handy when hunting N5J🙂
>
> 73 de 5p1kzx
>
>
>
> Sendt fra min Galaxy
>
>
>  Oprindelig besked 
> Fra: Christoph Berg via wsjt-devel 
> Dato: 28.09.2024 14.29 (GMT+01:00)
> Til: Black Michael , WSJT software development <
> wsjt-devel@lists.sourceforge.net>
> Cc: Christoph Berg 
> Emne: Re: [wsjt-devel] AGC affecting SuperFox decoding #FH
>
> Re: Black Michael via wsjt-devel
> > We need to do some testing but I'm considering changing Hamlib to put
> all rigs on FAST AGC (if AGC is not OFF) for WSJT-X operation.  So a
> setting of medium or slow would get changed to fast.
>
> That sounds like it should be done by wsjtx, not hamlib.
>
> 73,
> Christoph DF7CB
>
>
> ___
> 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
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] CY9C

2024-08-30 Thread Bill Barrett via wsjt-devel
They are on 80M regular F/H right now, easy.
GL
Bill W2PKY

On Fri, Aug 30, 2024 at 9:50 PM Bill Barrett 
wrote:

> Hello Gary-
> I worked them last night on 160M from Central Fl. So 80M SB possible.
> Like many I also need 80M. My Qs have been showing up in Club Log the next
> day.
>
> 73 & GL w/80M
>
> Bill W2PKY
>
> On Fri, Aug 30, 2024 at 9:44 PM Gary McDuffie via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>>
>>
>> > On Aug 26, 2024, at 02:49, Charles Suckling via wsjt-devel <
>> wsjt-devel@lists.sourceforge.net> wrote:
>> >
>> > They are also apparently using Club Log.  Don't know how often they are
>> uploading, but I and two other stations that they sent RR73 to are not
>> currently in the log.
>>
>> Some of their entries are QUITE delayed.  Some of mine were quick, but
>> for a long time I was missing some bands.  As of yesterday, it seems to be
>> caught up with my log with 6 bands listed.  I’ve yet to hear a peep out of
>> them on 80m and I wonder if the propagation is even possible at this part
>> of the cycle. If they’ve been on, I’m sure not hearing them.  It’s the
>> noise time of the year, so it may not happen here.  I’ve monitored 24 hrs a
>> daytime on some days and hear nothing but an occasional station calling
>> them.  I’m likely going to be limited to 6 bands only with them.  I felt
>> very fortunate to get them, because I am currently very antenna limited.
>>
>> 73, Gary - AG0N
>>
>> ___
>> 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] CY9C

2024-08-30 Thread Bill Barrett via wsjt-devel
Hello Gary-
I worked them last night on 160M from Central Fl. So 80M SB possible.
Like many I also need 80M. My Qs have been showing up in Club Log the next
day.

73 & GL w/80M

Bill W2PKY

On Fri, Aug 30, 2024 at 9:44 PM Gary McDuffie via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

>
>
> > On Aug 26, 2024, at 02:49, Charles Suckling via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
> >
> > They are also apparently using Club Log.  Don't know how often they are
> uploading, but I and two other stations that they sent RR73 to are not
> currently in the log.
>
> Some of their entries are QUITE delayed.  Some of mine were quick, but for
> a long time I was missing some bands.  As of yesterday, it seems to be
> caught up with my log with 6 bands listed.  I’ve yet to hear a peep out of
> them on 80m and I wonder if the propagation is even possible at this part
> of the cycle. If they’ve been on, I’m sure not hearing them.  It’s the
> noise time of the year, so it may not happen here.  I’ve monitored 24 hrs a
> daytime on some days and hear nothing but an occasional station calling
> them.  I’m likely going to be limited to 6 bands only with them.  I felt
> very fortunate to get them, because I am currently very antenna limited.
>
> 73, Gary - AG0N
>
> ___
> 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] RC-6 observations

2024-08-25 Thread Bill Barrett via wsjt-devel
The Improved version does not control the Flex SSDR SW properly.

Bill W2PKY


On Sun, Aug 25, 2024 at 6:29 PM Joe via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Is this the latest and greatest version?
> https://sourceforge.net/projects/wsjt-x-improved/files/latest/download
> I have sooo many on this machine, probably 4 different versions. it's time
> to clear them all out and install fresh so want to install the latest and
> greatest and best.
>
> Joe WB9SBD
>
> On 8/25/2024 4:59 PM, Black Michael via wsjt-devel wrote:
>
> Configuration setups will restart the program.
>
> If you want to try wsjtx-improved it's a simple matter of clicking or 
> right-clicking the FT8 
> button.https://sourceforge.net/projects/wsjt-x-improved/
>
> Mike W9MDB
>
>
>
>
>
>
>
>
>
>
>
> On Sunday, August 25, 2024 at 04:29:57 PM CDT, Dave Bernheisel via wsjt-devel 
>   wrote:
>
>
>
>
>
>
>
> I have been using WSJT-X v2.7.0-rc6 for a few weeks and have found it to be 
> stable and predictable.
>
> I have a configuration file for Regular Fox mode and another for Super Fox 
> mode.  Changing from one configuration
>
> to another causes the program to exit and restart itself in the selected mode.
>
> Is it possible, when the program is released to production, that the change 
> from one Hound  mode to another can be made without the
>
> restart of the program?
>
>  Are there plans to make the transition more 'seamless'?   Would it be 
> possible to have the software attempt to decode the Fox situation and 
> determine
>
> if the Fox is operating in Super mode or Legacy mode?  Is it possible for the 
> legacy hound software to coexist in the same executable module?
>
>
>
> Thank you all for the  fine work and talent you have given the Amateur Radio 
> community!
>
>
>
> 73,
>
> Dave Bernheisel, N2DPF
>
>
> ___
> wsjt-devel mailing 
> listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> wsjt-devel mailing 
> listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> 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] Comment on Superfox/hound release rc6

2024-08-11 Thread Bill Barrett via wsjt-devel
Hello Tom-
You have a good point about the possibility of QRM on the Hounds frequency
when returning the signal report transmission.
Perhaps they will modify the protocol to include the Hound shifting
frequency on that transmission.
Earlier in the thread it was suggested some receivers need to have their
AGC disabled for maximum decoding efficiency.
However, the number of successful Qs/min completed is phenomenal compared
to previous multiple stns decoding.
73;
Bill W2PKY


On Sun, Aug 11, 2024 at 12:08 PM Tom Hauer via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> First,  This is an awesome addition to FT8 capability.  It works great on
> the hound end, and having up to 9 streams on the fox end is amazing.  The
> best part is the verification, that is a home run.  Thank you to all on the
> team for an amazing effort.
>
> Second, an observation.  I have been watching N5J on multiple bands as
> they work this new mode (and have worked them on all my active bands on
> FT8).  I noticed that the first time success rate for them completing a QSO
> seems to be lower than on standard Fox/Hound, they have 2, 3 or more
> retransmits of the S/N and quite a few that drop off because they don't
> appear to decode a response even when the S/N they send is well above -10.
> And, as a result this is lowering their successful QSO rate. I am wondering
> if this has to do with the fact that the hound frequency is not shifted and
> that there is the potential for much more interference from other signals
> on and around the hound frequency. Here is STX even my waterfall can get
> quite crowded with strong signals overlapping.  I can't imagine what they
> see!!  Don't know if that is having an impact but just my thought!
>
> Thanks again for an awesome job.
>
> Tom Hauer, K0YA
> ARES Emergency Coordinator
> Blanco, Burnet, Llano Counties
> ARRL ARES District 8, STX Section
> TDEM RACES District 12-053
> 319 551-9788
> rdrnr...@gmail.com
> PO Box 1522 (mailing ADR)
> 11700 E FM 1431 R37
> Marble Falls, Tx 78654
> EM00wn
> Latitude:  30.568805
> Longitude:  -98.140287
>
> ___
> 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] -rc6 transmit disable

2024-07-20 Thread Bill Barrett via wsjt-devel
I had something similar with RC5 on my Flex Radio where:
Called FOX
FOX Answered with report.
RC5 commanded the radio into transmit but no RF output.
Two replies from  the FOX passed with no RF reply from my rig. Was looking
around to learn the problem.
Finally clicked the DAX TX icon on the DAX panel to restore the audio
connection.
Fortunately the FOX K8R completed the Q and I was in the log.
Never had anything like this happen in all the years on WSJT-X or after
this incident.

Bill W2PKY




On Sat, Jul 20, 2024 at 12:25 AM Jim Shorney via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

>
> Thanks to Joe and the team for the work on -rc6. I worked K8R on 15m today
> at -10 with consistent decodes. However his signal report to me was printed
> after the TX Enable had turned itself off an it did not re-enable when it
> saw the fox reply as I have seen classic F/H do in the past. I was quick
> enough to save the Q but I was wondering if this is intended behavior?
>
> --
>
> 73
>
> -Jim
> NU0C
>
>
> ___
> 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] Flex slice/hamlib rc5

2024-07-02 Thread Bill Barrett via wsjt-devel
Hello Al-

Great idea, tnx fer the idea.

73;
Bill W2PKY

On Tue, Jul 2, 2024 at 12:25 PM k0vm via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

>
> Hint to Flex users...
>To make life easier in the future.. Set a DHCP ip address reservation
> for your radio in your LAN router.
>Otherwise, the next time you boot up the radio, the DHCP may assign a
> different ip address and you'll forever be updating the address in WSJT..
>
> AL, K0VM
>
>
>
>
> On 7/2/2024 10:39 AM, Black Michael via wsjt-devel wrote:
>
> Maybe I can make the error message a bit better -- yes -- you do need the
> radio's IP address
>
> Do you mean it doesn't work if you append the port 4992 too?
>
> Mike W9MDB
>
>
>
>
> On Tuesday, July 2, 2024 at 10:35:52 AM CDT, Michael Morgan via wsjt-devel
>  
> wrote:
>
>
> When I installed the new rc5 software last night I tried the 6000 Slice
> A.  Based on the message i received I entered just the IP address of my
> radio no port (looks like it was appending port 4992) and it seemed to work
> from there.
>
> Michael, AA5SH
>
> On Tue, Jul 2, 2024 at 10:07 AM Bill Barrett via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> Hello Mike-
>
> Good to know there are settings for SSDR, is there a tutorial on how to
> use these new settings.
> Could not find anything in the Ver 2.7 User Guide.
>
> Thanks;
> Bill W2PKY
>
> On Tue, Jul 2, 2024 at 10:15 AM Black Michael via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> What software are you using for the Flex?
>
> This was made for the current version of SmartSDR.
>
> Mike W9MDB
>
>
>
>
>
>
>
>
> On Tuesday, July 2, 2024 at 09:08:44 AM CDT, k0vm via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>
>
>
>
>
>
>
> Mike,
>It fails with the same error message if "Network Server" is blank.
> Localhost (127.0.0.1) is not a valid ip address for a radio and port 4992
> is not serviced by either SSDR or SSDR CAT on the PC.
>Radio ip address:4992 or radiohostname:4992 does work.
> AL, K0VM
>
>
> On 7/1/2024 4:40 PM, Black Michael via wsjt-devel wrote:
>
>
> >
> >
> >
> > It sounds like you have a value in the "Network Server" box which you
> should not need for the Slice rigs.
> >
> >
> >
> >
> > Mike W9MDB
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >  On Monday, July 1, 2024 at 04:31:15 PM CDT, Bill Barrett via wsjt-devel
>  wrote:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hello Al-
> >
> >
> >
> > I had the same error when selecting the Slice A option.
> >
> > Went back to Flex XXX
> >
> >
> >
> >
> > Hope this helps.
> >
> >
> >
> >
> > Bill W2PKY
> >
> >
> >
> >
> >
> > On Mon, Jul 1, 2024 at 5:20 PM k0vm via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
> >
> >
> >>
> >>  ( wsjt-x-rc5/Hamlib 2024-06-30-T21:25Z, Flex 6600, SSDR 3.7.4)
> >>
> >> 1) When upgrading from RC4 ( which was running Flex 6xxx hamlib), rig
> selection was changed from Flex 6600 to ADT-200A.
> >>
> >> 2) Selecting SmartSDR slice A for rig results in Hamlib error..
> >>
> >>
> >> Setting network ser5ver to 192.168.7.166:4992 does work...
> >>
> >> 3) selecting rig flex 6xxx does work with original server ip/port
> >>
> >> AL, K0VM
> >> ___
> >> 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
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ___
> > 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://li

Re: [wsjt-devel] Flex slice/hamlib rc5

2024-07-02 Thread Bill Barrett via wsjt-devel
Hello Mike-
Instead of Network Server, how about Radio IP?

Thanks;
Bill W2PKY

On Tue, Jul 2, 2024 at 11:47 AM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Maybe I can make the error message a bit better -- yes -- you do need the
> radio's IP address
>
> Do you mean it doesn't work if you append the port 4992 too?
>
> Mike W9MDB
>
>
>
>
> On Tuesday, July 2, 2024 at 10:35:52 AM CDT, Michael Morgan via wsjt-devel
>  wrote:
>
>
> When I installed the new rc5 software last night I tried the 6000 Slice
> A.  Based on the message i received I entered just the IP address of my
> radio no port (looks like it was appending port 4992) and it seemed to work
> from there.
>
> Michael, AA5SH
>
> On Tue, Jul 2, 2024 at 10:07 AM Bill Barrett via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> Hello Mike-
>
> Good to know there are settings for SSDR, is there a tutorial on how to
> use these new settings.
> Could not find anything in the Ver 2.7 User Guide.
>
> Thanks;
> Bill W2PKY
>
> On Tue, Jul 2, 2024 at 10:15 AM Black Michael via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> What software are you using for the Flex?
>
> This was made for the current version of SmartSDR.
>
> Mike W9MDB
>
>
>
>
>
>
>
>
> On Tuesday, July 2, 2024 at 09:08:44 AM CDT, k0vm via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>
>
>
>
>
>
>
> Mike,
>It fails with the same error message if "Network Server" is blank.
> Localhost (127.0.0.1) is not a valid ip address for a radio and port 4992
> is not serviced by either SSDR or SSDR CAT on the PC.
>Radio ip address:4992 or radiohostname:4992 does work.
> AL, K0VM
>
>
> On 7/1/2024 4:40 PM, Black Michael via wsjt-devel wrote:
>
>
> >
> >
> >
> > It sounds like you have a value in the "Network Server" box which you
> should not need for the Slice rigs.
> >
> >
> >
> >
> > Mike W9MDB
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >  On Monday, July 1, 2024 at 04:31:15 PM CDT, Bill Barrett via wsjt-devel
>  wrote:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hello Al-
> >
> >
> >
> > I had the same error when selecting the Slice A option.
> >
> > Went back to Flex XXX
> >
> >
> >
> >
> > Hope this helps.
> >
> >
> >
> >
> > Bill W2PKY
> >
> >
> >
> >
> >
> > On Mon, Jul 1, 2024 at 5:20 PM k0vm via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
> >
> >
> >>
> >>  ( wsjt-x-rc5/Hamlib 2024-06-30-T21:25Z, Flex 6600, SSDR 3.7.4)
> >>
> >> 1) When upgrading from RC4 ( which was running Flex 6xxx hamlib), rig
> selection was changed from Flex 6600 to ADT-200A.
> >>
> >> 2) Selecting SmartSDR slice A for rig results in Hamlib error..
> >>
> >>
> >> Setting network ser5ver to 192.168.7.166:4992 does work...
> >>
> >> 3) selecting rig flex 6xxx does work with original server ip/port
> >>
> >> AL, K0VM
> >> ___
> >> 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
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ___
> > 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
>
>
> ___
> 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
>
> ___
> 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
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Flex slice/hamlib rc5

2024-07-02 Thread Bill Barrett via wsjt-devel
Hello Mike-

Good to know there are settings for SSDR, is there a tutorial on how to use
these new settings.
Could not find anything in the Ver 2.7 User Guide.

Thanks;
Bill W2PKY

On Tue, Jul 2, 2024 at 10:15 AM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> What software are you using for the Flex?
>
> This was made for the current version of SmartSDR.
>
> Mike W9MDB
>
>
>
>
>
>
>
>
> On Tuesday, July 2, 2024 at 09:08:44 AM CDT, k0vm via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>
>
>
>
>
>
>
> Mike,
>It fails with the same error message if "Network Server" is blank.
> Localhost (127.0.0.1) is not a valid ip address for a radio and port 4992
> is not serviced by either SSDR or SSDR CAT on the PC.
>Radio ip address:4992 or radiohostname:4992 does work.
> AL, K0VM
>
>
> On 7/1/2024 4:40 PM, Black Michael via wsjt-devel wrote:
>
>
> >
> >
> >
> > It sounds like you have a value in the "Network Server" box which you
> should not need for the Slice rigs.
> >
> >
> >
> >
> > Mike W9MDB
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >  On Monday, July 1, 2024 at 04:31:15 PM CDT, Bill Barrett via wsjt-devel
>  wrote:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hello Al-
> >
> >
> >
> > I had the same error when selecting the Slice A option.
> >
> > Went back to Flex XXX
> >
> >
> >
> >
> > Hope this helps.
> >
> >
> >
> >
> > Bill W2PKY
> >
> >
> >
> >
> >
> > On Mon, Jul 1, 2024 at 5:20 PM k0vm via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
> >
> >
> >>
> >>  ( wsjt-x-rc5/Hamlib 2024-06-30-T21:25Z, Flex 6600, SSDR 3.7.4)
> >>
> >> 1) When upgrading from RC4 ( which was running Flex 6xxx hamlib), rig
> selection was changed from Flex 6600 to ADT-200A.
> >>
> >> 2) Selecting SmartSDR slice A for rig results in Hamlib error..
> >>
> >>
> >> Setting network ser5ver to 192.168.7.166:4992 does work...
> >>
> >> 3) selecting rig flex 6xxx does work with original server ip/port
> >>
> >> AL, K0VM
> >> ___
> >> 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
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ___
> > 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
>
>
> ___
> 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] 160m S/N needs advanced mode

2023-12-07 Thread Bill Barrett via wsjt-devel
A few days ago I worked a ZL stn with 80 watts to a 40ft vertical with just
a few long radials. My report was -11 on FT8.
>From time to time 160M propagation is amazing even during strong Sun Spot
cycle times.

Bill
W2PKY Tampa Fl.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] FT8 on 160m with Beverage antenna

2023-11-13 Thread Bill Barrett via wsjt-devel
May want to browse the W8JI website for a lot of interesting information on
all phases of ham radio.
Here's a link to the Beverage antenna section:
https://www.w8ji.com/beverages.htm
Have a look at his antenna comparison spreadsheet to get an idea of
performance of various receive antennas. https://www.w8ji.com/receiving.htm

Best DX

Bill W2PKY

On Mon, Nov 13, 2023 at 6:12 PM Neil via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Hi Glenn, I've only been using Beverages on 160m for 40 years, so this is
> a somewhat partial and subjective view, but they certainly increase the S/N
> ratio considerably for human ear reception of extremely weak signals *when
> terminated correctly*.  Usual gain is around -20 dBi, but irrelevant
> because I use carefully-designed preamps to increase the signal level back
> to the receivers to overwhelm locally-generates noises from my neighbours
> properties.
>
> I found that I could get almost as good results with phased rotatable
> terminated loops, using Vactrols and phasing networks to tune the
> characteristics, mainly null steering to reduce high-angle local signals,
> and reducing human-generated noise and noise from the auroral curtain up
> here at 54 degrees north. Those loops have a gain around -32 dBi when
> phased, but the gain in S/N is definitely worthwhile.  Beverages work
> *because* of the lossy dielectric soil beneath them, not despite it.
>
> E-field probe antennas and small loops also work very well to improve the
> S/N on some paths.  You need a selection of different antennas to get best
> results for all directions. I also use multiple receivers concurrently.
>
> You also have to detune and terminated any transmit antennas within a few
> wavelengths while you are on receive, avoid putting a station near any
> large wire arrays such as power grid feeds or electric fences or strained
> wire fences.
>
> I agree that Beverages and other specialist receive antennas are difficult
> to model, but luckily folks have been getting excellent results since
> FOREVER without worrying about whether they can be modelled.  Having a way
> to adjust the terminating resistor is helpful, and having the wire elevated
> the right distance above ground and having it multiple wavelengths long is
> also helpful. but I've used Beverage-on-ground antennas over poor soil with
> some success.
>
> Using my receive antennas often bring signals up that are entirely
> invisible and undecodable on the waterfall on transmit antennas.
>
> --
> Neil G4DBN
> https://youtube.com/MachiningandMicrowaves
>
> On 13/11/2023 21:41, robert evans LAST_NAME via wsjt-devel wrote:
>
> When they built and installed the beverages they noticed they
> had just as much noise as the other antennas if not more.
>
> I modeled the Beverage and discovered it was a very high
> loss antenna. The soil was the lossy element and if you
> tried to reduce the loss by tuning the termination and
> matching networks you compromised the front to back
> ratios and lost directionality.
>
> The performance of the Beverage was dependent on soil
> characteristics and difficult to model and variable to
> to due to rain etc.
>
> We put an oscillator in the undesired direction.
> Before a contest the termination and matching was
> tweaked to null the oscillator in the park while favoring
> European stations.
>
> The Beverage is a lossy antenna with the least loss
> in the desired direction when correctly terminated and
> matched for the soil conditions.
>
> BCNU DE N2LO~>
>
>
> On 11/13/2023 11:45 AM EST Glenn Williams via wsjt-devel 
>   wrote:
>
>
> This is a theory question. There is a bit of FT8 on 160m.  Does use of a
> Beverage Antenna to get more signal raise the S/N value? Would that
> antenna help with receiving weaker signals (a variation of that S/N
> question)?
> --73, Glenn, AF8C
>
>
>
> ___
> 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] WSJT-X 2.6.1 GA Release

2023-02-14 Thread Bill Barrett via wsjt-devel
The error was due to an instance of WSJT-X running while trying to update.
Sri;
Bill W2PKY

On Tue, Feb 14, 2023 at 7:49 PM Bill Barrett 
wrote:

> Stuck on this error, Am I doing something wrong?
>
>
> Bill W2PKY
>
> On Tue, Feb 14, 2023 at 6:28 PM Joe Taylor via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>> Hi Barry,
>>
>> There have been *many* announcements in a variety of places about our
>> switch from the Princeton University site to SourceForge.  The tarfile
>> you want is now linked at the bottom of this web page:
>>
>> https://wsjt.sourceforge.io/wsjtx.html
>>
>> The direct link to the tarfile is:
>>
>> https://sourceforge.net/projects/wsjt/files/wsjtx-2.6.1/wsjtx-2.6.1.tgz
>>
>> -- Joe, K1JT
>>
>> On 2/13/2023 5:35 PM, Barry Jackson via wsjt-devel wrote:
>> > On 16/01/2023 14:22, Joe Taylor via wsjt-devel wrote:
>> >> The WSJT Development Team is pleased to announce that today the Solar
>> >> Flux Index is 234 and Sunspot Number is 195.
>> >>
>> >> Oh, yes: and the WSJT-X 2.6.1 General Availability (GA) release is now
>> >> available for free download from SourceForge.
>> >>
>> >
>> > Hi Joe,
>> >
>> > error: Could not download file
>> > https://www.physics.princeton.edu/pulsar/K1JT/wsjtx-2.6.1.tgz
>> >
>> > I maintain wsjtx for Mageia and we have always used the above URL path
>> > for downloading the official sources.
>> >
>> > Has this changed permanently, or is this an oversight, or a server
>> issue?
>> >
>> > Barry
>> >
>> >
>> >
>> > ___
>> > 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
>>
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSJT-X 2.6.1 GA Release

2023-02-14 Thread Bill Barrett via wsjt-devel
Stuck on this error, Am I doing something wrong?


Bill W2PKY

On Tue, Feb 14, 2023 at 6:28 PM Joe Taylor via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Hi Barry,
>
> There have been *many* announcements in a variety of places about our
> switch from the Princeton University site to SourceForge.  The tarfile
> you want is now linked at the bottom of this web page:
>
> https://wsjt.sourceforge.io/wsjtx.html
>
> The direct link to the tarfile is:
>
> https://sourceforge.net/projects/wsjt/files/wsjtx-2.6.1/wsjtx-2.6.1.tgz
>
> -- Joe, K1JT
>
> On 2/13/2023 5:35 PM, Barry Jackson via wsjt-devel wrote:
> > On 16/01/2023 14:22, Joe Taylor via wsjt-devel wrote:
> >> The WSJT Development Team is pleased to announce that today the Solar
> >> Flux Index is 234 and Sunspot Number is 195.
> >>
> >> Oh, yes: and the WSJT-X 2.6.1 General Availability (GA) release is now
> >> available for free download from SourceForge.
> >>
> >
> > Hi Joe,
> >
> > error: Could not download file
> > https://www.physics.princeton.edu/pulsar/K1JT/wsjtx-2.6.1.tgz
> >
> > I maintain wsjtx for Mageia and we have always used the above URL path
> > for downloading the official sources.
> >
> > Has this changed permanently, or is this an oversight, or a server issue?
> >
> > Barry
> >
> >
> >
> > ___
> > 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
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Decodes with strong QRM

2022-09-08 Thread Bill Barrett via wsjt-devel
Hello Sam-
Thanks for the explanation and reply to my post.
73;

Bill

On Thu, Sep 8, 2022 at 7:57 AM Sam W2JDB via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Hi Bill,
>
> I will quote an email passage from Reino OH3M
>
> "there are three dimensions that affect to the decoding probability of two
> signals on the same frequency slot. Everybody knows signal strength and
> frequency difference, but also time difference has a strong effect. A time
> difference of more than a symbol length 160 ms may be enough even, when
> signal strengths are the same and there is no frequency difference."
>
> It is amazing. Look at the screen shot at the DT and SNR values of the two
> other stations.
>
> You also have a duplicated decode look at the 2  "KP3WR K3RW FN00" decodes
> both occurring at 0115 in the display.
>
> 73,
>
> Sam W2JDB
>
>
>
> -Original Message-
> From: Bill Barrett via wsjt-devel 
> To: WSJT software development 
> Cc: Bill Barrett 
> Sent: Wed, Sep 7, 2022 8:57 pm
> Subject: [wsjt-devel] Decodes with strong QRM
>
> D2UY was interfered with by stns previously worked. The decoder picked out
> both stns. Amazing!
>
> Bill W2PKY
>
>
> ___
> 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
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Decodes with strong QRM

2022-09-07 Thread Bill Barrett via wsjt-devel
D2UY was interfered with by stns previously worked. The decoder picked out
both stns. Amazing!

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


Re: [wsjt-devel] Regressions in WSJT-X ver 2.5.0

2022-01-27 Thread Bill Barrett via wsjt-devel
Hello Team-

Running 2.5.2 "deep decode" recently saw 90-100 decodes posted on 40M in
the evening but the waterfall and JTAlert show about 1/2.
Finally the Band Activity section shows about 1/2 the large count. Anyone
else seeing this?

Thanks;
Bill W2PKY

On Thu, Jan 27, 2022 at 11:53 AM Andy Durbin via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> I updated from WSJT-X ver 2.3.0 to ver 2.5.0 both Win 64 bit and I noticed
> the following changes.  I used the term regressions in the title because I
> think they are.  The developers may not agree that this characterization is
> correct.
>
>
>1. Main window size is no longer remembered through a shut down and
>restart.
>2. First time used after start the frequency/band select window opens
>about double normal width
>3. Interaction with JTAlert has changed for single clicked callsigns.
>In 2.3.0 any decoded call would move the RX frequency cursor and populate
>the Received frequency pane with the decode.  In 2.5.0 only a subset of
>decoded calls is responsive. (See HamApps thread "No click response if CQ
>only).
>
> None of these changes prevents use of ver 2.5.0. but I have reverted to
> 2.3.0 because I prefer the way that it works.
>
> 73,
> Andy, k3wyc
>
>
> ___
> 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] WSJT-X settings Reporting tab

2021-11-04 Thread Bill Barrett via wsjt-devel
Hello Laurie-

I finally found the "WSJT-X UDP Multicast on Loopback" on the initial
clicking of the settings tab.
Thought it was somewhere in Managing Settings. Realize now there is a
brief clue in the help file.
Maybe a picture of the whole settings tab with an arrow to the top position
would be more helpful.
I have programmed plenty of UIs, interesting to see how users trip over the
simplest of situations.
Obviously enjoying the panel options on the Call Signs Window. Terrific
app, could not operate digital without it.

73;

Bill W2PKY



On Wed, Nov 3, 2021 at 11:53 PM Laurie, VK3AMA via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

>
>
> On 4/11/2021 1:52 pm, Bill Barrett via wsjt-devel wrote:
> > Used TCP/IP connection and 224.0.0.1 and ethernet outgoing interface.
> > That works!
> >
> > Bill W2PKY
>
> That tells me you didn't have the "WSJT-X UDP Multicast on Loopback"
> menu set in JTAlert which is needed if you have the WSJT-X UDP Server
> interface set to the loopback device. If WSJT-X is bound to the loopback
> device for the UDP Server settings then you need to tell JTAlert to
> explicitly to look for the UDP traffic on the loopback interface.
>
> de Laurie VK3AMA
>
>
>
> ___
> 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] WSJT-X settings Reporting tab

2021-11-03 Thread Bill Barrett via wsjt-devel
Hello Laurie-

Used TCP/IP connection and 224.0.0.1 and ethernet outgoing interface. That
works!

Bill W2PKY

On Wed, Nov 3, 2021 at 10:46 PM Bill Barrett 
wrote:

> Hello Laurie-
> Is it 244 or 224? either on does not work on the initial instance.
> 244 does not reveal the extra fields. 224 reveals the extra fields but
> does not work.
> see ??? for band data on initial instance and no decodes in Call Signs
> window.
> Where am I going wrong?
> Thanks;
> Bill
>
> On Wed, Nov 3, 2021 at 10:32 PM Laurie, VK3AMA via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>>
>>
>> On 4/11/2021 12:43 pm, Bill Barrett via wsjt-devel wrote:
>>
>> This is from 2.5.0, first and second instance on Win11
>> does anyone know why they are different?
>>
>> Thanks;
>> Bill W2PKY
>>
>> You're running multiple WSJT-X instances with incompatible udp server
>> settings. You have one instance running unicast (127.0.0.1) and the other
>> multicast (244.0.0.1). JTAlert when running in a multi-instance environment
>> requires that all WSJT-X instances be set to use multicast. You need to
>> change your unicast WSJT-X instance to multicast for the UDP server
>> settings.
>>
>> de Laurie VK3AMA
>> ___
>> 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] WSJT-X settings Reporting tab

2021-11-03 Thread Bill Barrett via wsjt-devel
Hello Laurie-
Is it 244 or 224? either on does not work on the initial instance.
244 does not reveal the extra fields. 224 reveals the extra fields but does
not work.
see ??? for band data on initial instance and no decodes in Call Signs
window.
Where am I going wrong?
Thanks;
Bill

On Wed, Nov 3, 2021 at 10:32 PM Laurie, VK3AMA via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

>
>
> On 4/11/2021 12:43 pm, Bill Barrett via wsjt-devel wrote:
>
> This is from 2.5.0, first and second instance on Win11
> does anyone know why they are different?
>
> Thanks;
> Bill W2PKY
>
> You're running multiple WSJT-X instances with incompatible udp server
> settings. You have one instance running unicast (127.0.0.1) and the other
> multicast (244.0.0.1). JTAlert when running in a multi-instance environment
> requires that all WSJT-X instances be set to use multicast. You need to
> change your unicast WSJT-X instance to multicast for the UDP server
> settings.
>
> de Laurie VK3AMA
> ___
> 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] WSJT-X settings Reporting tab

2021-11-03 Thread Bill Barrett via wsjt-devel
Hello Peter-

Thanks, yes, if 224 and the extra fields are present and 127 is entered the
extra fields go away.



On Wed, Nov 3, 2021 at 10:08 PM Peter Sumner via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Hello Bill,
>  yes those displays are indeed different as on one you have defined a UDP
> broadcast address of 244.0.0.1 which then prompts the WSJT software to
> offer you a selection for an interface to apply this to. Ethrnet or
> loopback normally, plus the multicast TTL, whereas the other version is the
> STOCK config.
>
> You can make them look the same by putting in the broadcast address of
> 127.0.0.1 and all the other options will go away after you hit OK
>
> All of my instances of WSJT-X have the 244.0.0.1 setup so I can use the
> monitoring software across my farm of PC's
>
> Regards,
> Peter, vk5pj
>
> On Thu, Nov 4, 2021 at 12:20 PM Bill Barrett via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>> This is from 2.5.0, first and second instance on Win11
>> does anyone know why they are different?
>>
>> Thanks;
>> Bill W2PKY
>> ___
>> 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
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] WSJT-X settings Reporting tab

2021-11-03 Thread Bill Barrett via wsjt-devel
This is from 2.5.0, first and second instance on Win11
does anyone know why they are different?

Thanks;
Bill W2PKY
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSJT-X not recognising multiple Virtual Audio Cables

2021-11-01 Thread Bill Barrett via wsjt-devel
Hello Bill-
Thanks for taking the time to explain the complexity of dealing with SDR
Digital Data.
Bill W2PKY

On Mon, Nov 1, 2021 at 10:38 AM Bill Somerville via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Bill,
>
> typical SDR console applications deliver samples via audio devices, some
> have other mechanisms but most of those are not to a common standard. What
> is actually passed over an audio device stream need not be audio, for
> example many (most) SDR consoles are capable of producing (and consuming in
> a few transceiver cases) I/Q sample data as a stereo pair of interleaved I
> and Q data streams. This is usually necessary since consuming applications
> wish to constrain the sample rate and do not want the full bandwidth of the
> SDR sampling circuits - this is what the SDR console application should be
> doing to provide the sample rate the consumer requests. Nor do consuming
> applications wish to control the ever increasing number of SDRs, e.g. to
> set the centre frequency, filter settings, gain settings, etc., each with
> their own proprietary mechanism.
>
> WSJT-X is not a general purpose SDR console, currently it consumes a
> baseband 16-bit PCM audio sample stream at 48,000 Hz sample rate. In future
> it may have a wide-band option to consume something along the lines of a
> 96,000 Hz I/Q data stream pair. Note this is a non-trivial change as the
> DSP processing in WSJT-X is built on the assumption that the input data is
> 48,000 Hz bandwidth, and furthermore the first processing step is a
> downsample and LPF to 12,000 Hz. It is not really relevant that the data
> arrives a baseband PCM audio, rather it is the bandwidth requirement that
> determines the following processing steps to decode signals.
>
> So to answer your question, no to the first, WSJT-X is not trying to be a
> general purpose SDR console. As to the second, it is not really relevant
> how the sample stream is delivered, but as PCM data, perhaps misused
> repurposed to covey I/Q data, it is a very convenient cross-platform data
> transfer mechanism for sample data. Note there should be no "Windows audio
> processing" if the sample rate is consistent throughout and the levels are
> set to 0 dB (FS) throughout.
>
> 73
> Bill
> G4WJS.
>
> On 01/11/2021 13:59, Bill Barrett via wsjt-devel wrote:
>
> Hello Bill-
> Do you see a possibility that WSJT-X might one day have a direct
> connection to SDR Digital Data Stream input bypassing the typical DAX
> module and Windows audio processing?
>
> Thanks;
>
> Bill W2PKY
>
> On Mon, Nov 1, 2021 at 9:48 AM Bill Somerville via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>> On 01/11/2021 12:22, Dave Fitches via wsjt-devel wrote:
>> > I recently got another RTL-SDR to hook up to my system. (Win 10)
>> >
>> > I was planning to run one using WSJT-X running FT8, the other another
>> > running WSPR
>> >
>> > However... it seems that WSJT-X will only recognise ONE Virtual Audio
>> > Cable (VAC)...
>> >
>> > I recently set up two additional VAC's (for a total of three) and they
>> > work perfectly - unless I'm using WSXT-X which will only recognise ONE
>> > on the Soundcard Input feed, though it DOES show all THREE VAC's on
>> > the OUTBOUND sound card selection...
>> >
>> > Similarly (and no surprise because it's using the same code) JS8Call
>> > has the same issues.
>> >
>> > I'm using the VAC software from V.Burel / JS-Loezic -
>> > https://vb-audio.com/Cable/
>> >
>> > --
>> >
>> >
>> >   = Dave Fitches =
>>
>> Hi Dave,
>>
>> no one else has reported a similar issue. I have VAC installed (not
>> VB-Cable but similar) with 8 devices and that all show up in both WSJT-X
>> audio input and out devices as expected. do other applications that use
>> audio devices via the MME audio sub-subsystem like Audacity show them?
>>
>>
>> 73
>> Bill
>> G4WJS.
>
>
> ___
> 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] WSJT-X not recognising multiple Virtual Audio Cables

2021-11-01 Thread Bill Barrett via wsjt-devel
Hello Bill-
Do you see a possibility that WSJT-X might one day have a direct connection
to SDR Digital Data Stream input bypassing the typical DAX module and
Windows audio processing?

Thanks;

Bill W2PKY

On Mon, Nov 1, 2021 at 9:48 AM Bill Somerville via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> On 01/11/2021 12:22, Dave Fitches via wsjt-devel wrote:
> > I recently got another RTL-SDR to hook up to my system. (Win 10)
> >
> > I was planning to run one using WSJT-X running FT8, the other another
> > running WSPR
> >
> > However... it seems that WSJT-X will only recognise ONE Virtual Audio
> > Cable (VAC)...
> >
> > I recently set up two additional VAC's (for a total of three) and they
> > work perfectly - unless I'm using WSXT-X which will only recognise ONE
> > on the Soundcard Input feed, though it DOES show all THREE VAC's on
> > the OUTBOUND sound card selection...
> >
> > Similarly (and no surprise because it's using the same code) JS8Call
> > has the same issues.
> >
> > I'm using the VAC software from V.Burel / JS-Loezic -
> > https://vb-audio.com/Cable/
> >
> > --
> >
> >
> >   = Dave Fitches =
>
> Hi Dave,
>
> no one else has reported a similar issue. I have VAC installed (not
> VB-Cable but similar) with 8 devices and that all show up in both WSJT-X
> audio input and out devices as expected. do other applications that use
> audio devices via the MME audio sub-subsystem like Audacity show them?
>
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> 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