Re: [wsjt-devel] Windows 10 24 bit audio rx + split code into twoprojects?

[Virginia Greene via wsjt-devel]

On Apr 24, 2023, at 8:36 AM, K9RX  wrote:
> 
> Not to belabor the point…. I too was rejected although I’m still able to see 
> posts – just can’t respond. My failing? I posted a comment saying how I had 
> 92 decodes in one sequence using WSJT and I congratulated the creators of the 
> program – kudos I said. I followed by the benign statement “JTDX had 94 the 
> following sequence – essentially the same” … the whole post was not posted. I 
> asked why – he responded with this tirade of how he has stated time and again 
> NOT to post about derivatives… I apologized and said I was unaware of that – 
> that I was a casual poster. He called me a liar. I told him I believe 
> sincerely in honesty and integrity – apologized again - he doubled down. 
> After that he wouldn’t respond. So YES – there IS someone there and HE alone 
> is making these decisions. My suggestion to him: get a life. Stop being an 
> ass to others who sincerely are not trying to disrespect WSJT. 
>  
> Gary
> K9RX
>  
> Sent from Mail  for Windows
>  

Hmmm…. That explains something I experienced.

A few weeks ago I posted a comment about how I’d just decoded 100 stations for 
the first time in a single sequence.  I thought that was pretty amazing and 
said so.  There was no mention of any alternative software or any of that.  
Just plain straight praise.

I should say that I *tried* to post that comment.  It never made it and I had 
no idea why.  

Oh well…

73,

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

Re: [wsjt-devel] Windows 10 24 bit audio rx + split code into twoprojects?

[Adrian via wsjt-devel]

I recommend someone sane start a new wsjtx group and we all migrate.


73


vk4tux

On 24/4/23 22:36, K9RX via wsjt-devel wrote:


Not to belabor the point…. I too was rejected although I’m still able 
to see posts – just can’t respond. My failing? I posted a comment 
saying how I had 92 decodes in one sequence using WSJT and I 
congratulated the creators of the program – kudos I said. I followed 
by the benign statement “JTDX had 94 the following sequence – 
essentially the same” … the whole post was not posted. I asked why – 
he responded with this tirade of how he has stated time and again NOT 
to post about derivatives… I apologized and said I was unaware of that 
– that I was a casual poster. He called me a liar. I told him I 
believe sincerely in honesty and integrity – apologized again - he 
doubled down. After that he wouldn’t respond. So YES – there IS 
someone there and HE alone is making these decisions. My suggestion to 
him: get a life. Stop being an ass to others who sincerely are not 
trying to disrespect WSJT.


Gary

K9RX

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for 
Windows


*From: *Virginia Greene via wsjt-devel 
<mailto:wsjt-devel@lists.sourceforge.net>

*Sent: *Monday, April 24, 2023 8:21 AM
*To: *marting0...@gmail.com; WSJT software development 
<mailto:wsjt-devel@lists.sourceforge.net>

*Cc: *Virginia Greene <mailto:cvgre...@icloud.com>
*Subject: *Re: [wsjt-devel] Windows 10 24 bit audio rx + split code 
into twoprojects?


On Apr 24, 2023, at 7:49 AM, Martin Davies G0HDB via wsjt-devel 
 wrote:


>

> Commiserations, Jim, Willie and Virginia (and anyone else whose 
membership of the


> WSJT-X group on groups.io has been terminated!).

Martin,

Perhaps the moderation is at least partially automated, with people 
being dropped for using one of several banned phrases or terms.  Who 
knows.  It does seem rather draconian to just drop forum members for a 
violation rather than just telling them that their post violates this 
or that forum rule.


I’m sure they have their reasons for moderating as they do.  At some 
point the job becomes really easy when there’s no members left to post.


73,

Clarke  K1JX

___

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] Windows 10 24 bit audio rx + split code into twoprojects?

[K9RX via wsjt-devel]

Not to belabor the point…. I too was rejected although I’m still able to see 
posts – just can’t respond. My failing? I posted a comment saying how I had 92 
decodes in one sequence using WSJT and I congratulated the creators of the 
program – kudos I said. I followed by the benign statement “JTDX had 94 the 
following sequence – essentially the same” … the whole post was not posted. I 
asked why – he responded with this tirade of how he has stated time and again 
NOT to post about derivatives… I apologized and said I was unaware of that – 
that I was a casual poster. He called me a liar. I told him I believe sincerely 
in honesty and integrity – apologized again - he doubled down. After that he 
wouldn’t respond. So YES – there IS someone there and HE alone is making these 
decisions. My suggestion to him: get a life. Stop being an ass to others who 
sincerely are not trying to disrespect WSJT. 

Gary 
K9RX 

Sent from Mail for Windows

From: Virginia Greene via wsjt-devel
Sent: Monday, April 24, 2023 8:21 AM
To: marting0...@gmail.com; WSJT software development
Cc: Virginia Greene
Subject: Re: [wsjt-devel] Windows 10 24 bit audio rx + split code into 
twoprojects?

On Apr 24, 2023, at 7:49 AM, Martin Davies G0HDB via wsjt-devel 
 wrote:
> 
> Commiserations, Jim, Willie and Virginia (and anyone else whose membership of 
> the 
> WSJT-X group on groups.io has been terminated!).


Martin,

Perhaps the moderation is at least partially automated, with people being 
dropped for using one of several banned phrases or terms.  Who knows.  It does 
seem rather draconian to just drop forum members for a violation rather than 
just telling them that their post violates this or that forum rule.

I’m sure they have their reasons for moderating as they do.  At some point the 
job becomes really easy when there’s no members left to post.

73,

Clarke  K1JX

___
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] Windows 10 24 bit audio rx + split code into two projects?

[Adrian via wsjt-devel]

The moderator there 'Roger' is a control freak, and very self sensitive.

Last week a poster had trouble decoding, and I referred him to time.is ,

however Roger completely misunderstood the relevance and arrogantly told 
me to try the website  myself,


if i wanted to know what result it gave  I asked if he was talking 
to me in disbelief that anyone would respond in that fashion.


When he said yes , I educated him on the value of time.is for time sync 
checks, and for my trouble he told me I was rude


for letting him know and placed me on permanent moderation. I just left. 
I don't recommend the group, as the admin is inept.



73


vk4tux

On 24/4/23 22:15, Virginia Greene via wsjt-devel wrote:

On Apr 24, 2023, at 7:49 AM, Martin Davies G0HDB via wsjt-devel 
 wrote:

Commiserations, Jim, Willie and Virginia (and anyone else whose membership of 
the
WSJT-X group on groups.io has been terminated!).


Martin,

Perhaps the moderation is at least partially automated, with people being 
dropped for using one of several banned phrases or terms.  Who knows.  It does 
seem rather draconian to just drop forum members for a violation rather than 
just telling them that their post violates this or that forum rule.

I’m sure they have their reasons for moderating as they do.  At some point the 
job becomes really easy when there’s no members left to post.

73,

Clarke  K1JX

___
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] Windows 10 24 bit audio rx + split code into two projects?

[Virginia Greene via wsjt-devel]

On Apr 24, 2023, at 7:49 AM, Martin Davies G0HDB via wsjt-devel 
 wrote:
> 
> Commiserations, Jim, Willie and Virginia (and anyone else whose membership of 
> the 
> WSJT-X group on groups.io has been terminated!).


Martin,

Perhaps the moderation is at least partially automated, with people being 
dropped for using one of several banned phrases or terms.  Who knows.  It does 
seem rather draconian to just drop forum members for a violation rather than 
just telling them that their post violates this or that forum rule.

I’m sure they have their reasons for moderating as they do.  At some point the 
job becomes really easy when there’s no members left to post.

73,

Clarke  K1JX

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

Re: [wsjt-devel] Windows 10 24 bit audio rx + split code into two projects?

[Martin Davies G0HDB via wsjt-devel]

On 23 Apr 2023 at 12:39, Jim Brown via wsjt-devel wrote:

> If I'm not mistaken, what the original poster is requesting was 
> implemented in the latest full release of JTDX. But since even the 
> slightest mention of software other than WSJT-X results in getting 
> bounced from the WSJT-X reflector, we never hear about stuff like this, 
> nor about whether it works, or provides useful benefit under real world 
> conditions. I am one of those who got bounced.

On 23 Apr 2023 at 18:11, Virginia Greene via wsjt-devel wrote:

> I am amongst the most recent exiles.  I mentioned that a current
> DXpedition may be using one of WSJT-X variants - variant not named -
> running MSHV, so it would probably be better to call that station
> using Normal mode instead of Hound mode. 
> 
> Boom!  

Commiserations, Jim, Willie and Virginia (and anyone else whose membership of 
the 
WSJT-X group on groups.io has been terminated!).

I also fell foul of the WSJT-X group moderator a few weeks ago - I had had the 
temerity to 
send a single-word response to a posting that had included the term 'MSHV' in 
its title and 
subsequently had my membership of the group terminated, yet the moderator had 
neither 
sanctioned the original posting nor another response to it that had also 
repeated the term 
'MSHV' in the title.

I emailed the moderator pointing out that his sanctioning of postings that 
included any 
reference to, for example, MSHV in either the posting's title or in the body 
text was very 
inconsistent - I provided a list of recent postings to the group that had been 
permitted to be 
promulgated despite them clearly contravening the policy of not permitting any 
reference 
whatsoever to the derivative apps.  I also pointed out that simply replying to 
a posting that 
included the name of a derivative app in its title in no way constituted a 
discussion of that 
derivative app.

I didn't even receive the courtesy of a reply to my email from the moderator...

--
73, Martin G0HDB



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

Re: [wsjt-devel] Windows 10 24 bit audio rx + split code into two projects?

[Genadi V . Zawidowski via wsjt-devel]

In my  radio filtered 48 kHz i/q stream (pairs of 28 bit samples) provided from 
fpga (122.88 MHz on input) converted to 32bit floats processed by Weaver method 
and can be routed trough 24 or 16 bit  usb audio to wsjt. If wsjt not truncate 
24 bit to 16 before processing,  I can switch off AGC for these modes.
Ep4ce22e22 and allwinner t113-s3 is a heart of radio.
-
Sent from Mail.ru app for Android Monday, 24 April 2023, 01:14AM +03:00 from 
Virginia Greene via wsjt-devel  wsjt-devel@lists.sourceforge.net :

>I am amongst the most recent exiles.  I mentioned that a current DXpedition 
>may be using one of WSJT-X variants - variant not named - running MSHV, so it 
>would probably be better to call that station using Normal mode instead of 
>Hound mode.
>
>Boom! 
>
>Anyway, the current state of the practical art in audio ADCs is an ESS part.  
>It has about 20 bits of real resolution.  (I have an ADC product using that 
>part and it does do that).  So, if you used a part like that in your 
>conversion from the analog audio out of the radio into the digital domain, 
>that’d be an improvement over 16 bits.  Assuming the data processing will do 
>24 bits, to pick a common number.
>
>But, that assumes a lot.  Most radios don’t use A-D or D-A converters in their 
>internal processing that are much beyond 16 bits.  In a lot of radios, you 
>have the detected audio converted into digital with 16 bit converters, 
>processed in the DSP, and then converted back into analog audio with 16 bit 
>converters.
>
>That’s hardly ideal.
>
>It’d be much nicer if we had access to the digital stream coming out of the 
>DSP system before it was converted to analog.  Ideally, the sample rate would 
>be 48 KHz, because that’s what WSJT-X uses.  I think that’d go a long way to 
>improving receive performance in crowded bands.  Plus, improve the transmit 
>signals, too - less chance for RF problems and other goblins.
>
>73,
>
>Clarke  K1JX
>
> On Apr 23, 2023, at 3:39 PM, Jim Brown via wsjt-devel < 
> wsjt-devel@lists.sourceforge.net> wrote:
>
> On 4/23/2023 11:20 AM, Daniel Uppström via wsjt-devel wrote:
>> Isn't that obvious why he wants more than 16 bits? With a receiver using 
>> more than that it could be possible to eliminate AGC all together and just 
>> feed something with 100 dB of dynamics into WSJT.
>
> If I'm not mistaken, what the original poster is requesting was implemented 
> in the latest full release of JTDX. But since even the slightest mention of 
> software other than WSJT-X results in getting bounced from the WSJT-X 
> reflector, we never hear about stuff like this, nor about whether it works, 
> or provides useful benefit under real world conditions. I am one of those who 
> got bounced.
>
> 73, Jim K9YC
>
>
>
>
>
>
> ___
> 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] Windows 10 24 bit audio rx + split code into two projects?

[Virginia Greene via wsjt-devel]

I am amongst the most recent exiles.  I mentioned that a current DXpedition may 
be using one of WSJT-X variants - variant not named - running MSHV, so it would 
probably be better to call that station using Normal mode instead of Hound mode.

Boom!  

Anyway, the current state of the practical art in audio ADCs is an ESS part.  
It has about 20 bits of real resolution.  (I have an ADC product using that 
part and it does do that).  So, if you used a part like that in your conversion 
from the analog audio out of the radio into the digital domain, that’d be an 
improvement over 16 bits.  Assuming the data processing will do 24 bits, to 
pick a common number.

But, that assumes a lot.  Most radios don’t use A-D or D-A converters in their 
internal processing that are much beyond 16 bits.  In a lot of radios, you have 
the detected audio converted into digital with 16 bit converters, processed in 
the DSP, and then converted back into analog audio with 16 bit converters.

That’s hardly ideal.

It’d be much nicer if we had access to the digital stream coming out of the DSP 
system before it was converted to analog.  Ideally, the sample rate would be 48 
KHz, because that’s what WSJT-X uses.  I think that’d go a long way to 
improving receive performance in crowded bands.  Plus, improve the transmit 
signals, too - less chance for RF problems and other goblins.

73,

Clarke  K1JX

> On Apr 23, 2023, at 3:39 PM, Jim Brown via wsjt-devel 
>  wrote:
> 
> On 4/23/2023 11:20 AM, Daniel Uppström via wsjt-devel wrote:
>> Isn't that obvious why he wants more than 16 bits? With a receiver using 
>> more than that it could be possible to eliminate AGC all together and just 
>> feed something with 100 dB of dynamics into WSJT.
> 
> If I'm not mistaken, what the original poster is requesting was implemented 
> in the latest full release of JTDX. But since even the slightest mention of 
> software other than WSJT-X results in getting bounced from the WSJT-X 
> reflector, we never hear about stuff like this, nor about whether it works, 
> or provides useful benefit under real world conditions. I am one of those who 
> got bounced.
> 
> 73, Jim K9YC
> 
> 
> 
> 
> 
> 
> ___
> 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] Windows 10 24 bit audio rx + split code into two projects?

[William Smith via wsjt-devel]

Ditto, but I can’t be too fussed about it, I’ve got other forums to be helpful 
on. 

I hope the moderator of the groups.io forum for wsjt gets some time to 
decompress.  Moderating anything on the Internet nowadays is not a job I would 
wish on my worst enemy.

73, Willie N1JBJ

> On Apr 23, 2023, at 3:59 PM, Jim Brown via wsjt-devel 
>  wrote:
> […]
> But since even the slightest mention of software other than WSJT-X results in 
> getting bounced from the WSJT-X reflector, we never hear about stuff like 
> this, nor about whether it works, or provides useful benefit under real world 
> conditions. I am one of those who got bounced.
> 
> 73, Jim K9YC



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

Re: [wsjt-devel] Windows 10 24 bit audio rx + split code into two projects?

[Jim Brown via wsjt-devel]

On 4/23/2023 11:20 AM, Daniel Uppström via wsjt-devel wrote:
Isn't that obvious why he wants more than 16 bits? With a receiver using 
more than that it could be possible to eliminate AGC all together and 
just feed something with 100 dB of dynamics into WSJT.


If I'm not mistaken, what the original poster is requesting was 
implemented in the latest full release of JTDX. But since even the 
slightest mention of software other than WSJT-X results in getting 
bounced from the WSJT-X reflector, we never hear about stuff like this, 
nor about whether it works, or provides useful benefit under real world 
conditions. I am one of those who got bounced.


73, Jim K9YC






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

Re: [wsjt-devel] Windows 10 24 bit audio rx + split code into two projects?

[Daniel Uppström via wsjt-devel]

Isn't that obvious why he wants more than 16 bits? With a receiver using 
more than that it could be possible to eliminate AGC all together and 
just feed something with 100 dB of dynamics into WSJT. That would be 
great. But if the code is written such that it only uses 16 bits that 
would of course require some serious coding efforts.


I have asked here earlier, but not got any reply; Wouldn't it be wise to 
split the code into two projects? A library for underlying DSP and then 
a GUI application as a separate project?


That would benefit experiments with the signal processing, it would also 
make it possible to fix GUI bugs independent of the DSP stuff. And it 
would make it easier to integrate the "WSJT-X modes" into other 
applications while on the other hand it would be easier to get new modes 
and/or improvements into WSJT-X.

A no-brainer, I think...

73 Daniel SM6VFZ



On 4/23/23 14:11, Black Michael via wsjt-devel wrote:

Why do you want more than 16-bit?  That would increase dynamic range.   
Currently WSJT-X will only use 16-bit.

Our current recommendation is to set the audio level in WSJT-X at 60dB and use 
slow AGC.  Slow AGC should prevent the AGC from increasing the signal level 
during the quiet periods in FT8.

Mike W9MDB









On Sunday, April 23, 2023 at 12:49:14 AM CDT, Genadi V. Zawidowski via wsjt-devel 
 wrote:






Hello. Who knows about internals wsjt-x - can I get benefits then using 24 bit 
audio format on duc/develop radio (I want to moderate AGC slope and pass to ft8 
decoder more then 16 bit audio signal).

Ua1arn


--
Sent from Mail.ru app for Android


___
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] Windows 10 24 bit audio rx

[Black Michael via wsjt-devel]

Why do you want more than 16-bit?  That would increase dynamic range.   
Currently WSJT-X will only use 16-bit.

Our current recommendation is to set the audio level in WSJT-X at 60dB and use 
slow AGC.  Slow AGC should prevent the AGC from increasing the signal level 
during the quiet periods in FT8.

Mike W9MDB









On Sunday, April 23, 2023 at 12:49:14 AM CDT, Genadi V. Zawidowski via 
wsjt-devel  wrote: 






Hello. Who knows about internals wsjt-x - can I get benefits then using 24 bit 
audio format on duc/develop radio (I want to moderate AGC slope and pass to ft8 
decoder more then 16 bit audio signal).

Ua1arn


--
Sent from Mail.ru app for Android


___
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] Windows 10 Pro time test

[ai4fu]

Please bear the following in mind while considering why you are seeing 
DT ≠ 0:



From Bill (G4WJS) a bit further back in this same thread...


"The DT figure is the measured difference between your PC clock and the 
sync of a decoded signal. A positive DT implies that the signal clock 
is behind yours. Positive components of the DT are the sender's clock 
being slow, and propagation delay. Also contributing are latencies 
including audio buffering and other processing delay which can be at 
either of both ends of the link and like propagation delay can only 
increase the DT, net clock difference can contribute a negative or a 
positive DT component."


I would be most interested to hear if you tried pushing the limits of 
how far out of sync you could push things and still manage decodes. The 
guide indicates "A means for synchronizing the computer clock to UTC 
within ±1 second". I wonder how far that boundary could be pushed and 
what the DT readings would be for, say, someone up to 900ms off. Maybe 
I should try it for myself...


Pardon my idle musings. I would be inclined to agree, even before the 
testing, that this falls under the "tempest in a teapot" category.


Best,
AI4FU(Jim)
 
On Wednesday, December 5, 2018 at 6:48 PM, John Kludt 
 wrote:

 
Yeah, the one thing I have wondered about is all the the version to 
version -X variance in protocols that are out there right now.  How 
does everyone know the decode failures are related  to DT and not   
72/75/77 bit issues?  Checking against Time.Is my computer's are 
always spot on and I almost never see a DT of  zero.  I also don't 
seem to have decoding problems.

 
I use Net Time Sync on both Win 7 and Win 10 machines for both 
terrestrial and EME FT8/JT65.

 
Anyway, following the thread with interest and hoping we do not 
over,- engineer the solution when the cause is a bit unclear

 
John
 
Sent from my Verizon Motorola Smartphone
On Dec 5, 2018 6:30 PM, David Fisher  wrote:

Since I apparently put the match to this issue, I’m going to run an 
experiment.


I normally run my Win 10 Pro (homebuilt) computer with the Meinberg 
NTP service. It has worked extremely well. But, it has also been 
said that the Windows service may be fine. So, let’s find out.


I’ve disabled Meinberg on my computer and reenabled the WTS. I’ve 
verified, and will continue to verify, that these setting stick 
across reboots. They are. The hardware clock on this computer has 
some miles on it and runs a bit slow, so whatever time service I 
use, it has some work to do.


Before someone jumps on it – this is Windows 10 PRO, not Home. It’s 
running 1809, and updates regularly as the patches come out. The 
system runs will and is reliable.


I’ll keep an eye on “DT” readings and compare the system clock with 
WWV from time to time. I’ll report what I find. Maybe this is a 
tempest in a teapot.


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

Re: [wsjt-devel] Windows 10 NTP configuration (was Re: use of NTP with WSJT-X disrupted by Windows 10 updates)

[Bill Somerville]

On 05/12/2018 21:07, Dana Myers wrote:

Here are the original settings for the W32Time registry values:

MinPollInterval: 10
MaxPollInterval: 15
UpdateInterval: 36
FrequencyCorrectRate: 4

and the NTP Client:

SpecialPollInterval: 604800


Hi Dana,

the Min and Max PollInterval configuration parameters are most relevant. 
The units are log^2 seconds, so 6 is 64 seconds, 10 is 1024 seconds and 
15 is 32768 seconds. So the default will poll the server between ~17 
minutes and ~9 hours. I don't now what determines which end of the range 
is used but I would guess it polls more often if it is having to make 
large corrections. Once every 17 min isn't bad and should be good enough 
for WSJT-X for most hardware, but if it waits 9 hr for a correction then 
that is unlikely to be good enough.


For comparison, I believe the Meinberg  NTP Client, by default, self 
adjusts with a minimum poll interval of 64s and the interval increases 
by powers of 2 up to 1024s once stability is established to keep the 
clock within tolerance with the minimum rate of server polls.


Full details of W32Time service configuration here: 
https://docs.microsoft.com/en-us/windows-server/networking/windows-time-service/windows-time-service-tools-and-settings#Configuration


73
Bill
G4WJS.

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

Re: [wsjt-devel] Windows 10 Pro time test

[John Kludt]

Yeah, the one thing I have wondered about is all the the version to version -X 
variance in protocols that are out there right now.  How does everyone know the 
decode failures are related  to DT and not   72/75/77 bit issues?  Checking 
against Time.Is my computer's are always spot on and I almost never see a DT of 
 zero.  I also don't seem to have decoding problems.

I use Net Time Sync on both Win 7 and Win 10 machines for both terrestrial and 
EME FT8/JT65.

Anyway, following the thread with interest and hoping we do not over,- engineer 
the solution when the cause is a bit unclear

John

Sent from my Verizon Motorola Smartphone
On Dec 5, 2018 6:30 PM, David Fisher  wrote:
>
> Since I apparently put the match to this issue, I’m going to run an 
> experiment.
>
> I normally run my Win 10 Pro (homebuilt) computer with the Meinberg NTP 
> service. It has worked extremely well. But, it has also been said that the 
> Windows service may be fine. So, let’s find out.
>
> I’ve disabled Meinberg on my computer and reenabled the WTS. I’ve verified, 
> and will continue to verify, that these setting stick across reboots. They 
> are. The hardware clock on this computer has some miles on it and runs a bit 
> slow, so whatever time service I use, it has some work to do.
>
> Before someone jumps on it – this is Windows 10 PRO, not Home. It’s running 
> 1809, and updates regularly as the patches come out. The system runs will and 
> is reliable.
>
> I’ll keep an eye on “DT” readings and compare the system clock with WWV from 
> time to time. I’ll report what I find. Maybe this is a tempest in a teapot.
>
> Dave / NX6D___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows 10 multiple problems and OS X 10.13.1 problems

[carcarx]

Hi, Bill,

On Windows 10, to see if the waterfall would "survive" I configured the
Setting->Radio->Rig to None.
Over multiple transmit cycles the waterfall never had a problem.

On the Mac side I did the same thing, upped my rig power to 40 watts,  and
starting making QSOs.

I did verify that the radio was set for 4800 bps speed.

So, in the Win 10 side, CAT behaves better (but still times out after
xmit), and on the Mac side it never did work.

Thanks for the help! At least I made some contacts!



On Sun, Nov 26, 2017 at 7:38 AM, Bill Somerville 
wrote:

> On 26/11/2017 17:31, carc...@gmail.com wrote:
>
> OM,
>>
>> please read the ReadMe.txt file at the root directory of the installer
>> DMG, it contains important instructions needed to prepare you Mac for use
>> with WSJT-X.
>>
>>
> Thanks, Bill, that allowed me to configure things, but with the Yaesu
> FT-857 default configuration the software claims that the rig's frequency
> can't be read.
> (WSJT-X chose the Bluetooth device on its own.) CAT control is
> automatically set to VOX, com settings automatically set 4800,8,2
>
> Thanks!
>
> Hi OM,
>
> you must match the "Preferences->Radio" serial port settings to those of
> your rig. If the rig is set to 4800 baud then you set that in WSJT-X and so
> on. 8-bit 2 stop bits is correct for your rig. Also make sure that CAT port
> is set to CAT rather than external ATU control in the rig's menu. The
> Rigblaster Blue seems to have some sort of internal VOX but I would
> recommend selecting CAT for "Preferences->Radio->PTT Method" as it avoids
> issues with timing on these rigs.
>
> Are you able to select the required 48000 Hz sample rate for the audio
> interface using Audio MIDI Settings as described in the WSJT-X ReadMe.txt
> file?
>
> 73
> Bill
> G4WJS.
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows 10 multiple problems and OS X 10.13.1 problems

[carcarx]

On Sat, Nov 25, 2017 at 4:45 PM, Bill Somerville 
wrote:

> Hi OM,
>
>>
>> Hi, Bill,


> I suspect there is a problem with the reliability of your audio
> connections to your rig. How is your rig connected to your PC for audio?


Bluetooth low energy via a Rigblaster Blue. This morning the waterfall
stopped after two transmits.


> Make sure you do not have "Settings->Radio->Allow Tx frequency changes
> while transmitting" checked as that is not possible with the Yaesu
> FT-817/857/897(D) series of rigs.
>
>
Verified that "Allow TX frequency changes while transmitting" is NOT
checked. (Never has been.) This morning I changed the Rigblaster delay to
minimum. No change
in behavior. I note that the poll interval is automatically set to 1 second.
A recap, this problem manifested itself with the advent of WSJT-X 1.7.0,
with a USB direct link. I was using a Rigblaster Advantage at the time.



> If you are using some form of VOX, particularly the SignaLink USB for
> audio then reduce any VOX delay to the minimum. It can also help to switch
> to CAT PTT rather than VOX, even with the SignaLink USB.
>

Tried CAT PTT and the rig switched to transmit. Had to power it off and
back on to recover it.

Thanks for the suggestions, but no change.
73 de KH6CP, Craig.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows 10 multiple problems and OS X 10.13.1 problems

[Bill Somerville]

On 26/11/2017 02:34, carc...@gmail.com wrote:

So, on to Mac OS 10.13.1:

When I try and run WSJT-X the "splash screen" briefly appears then get 
"Shared Memory Error", unable to create shared memory segment. 
Followed by "Fatal error, shared memory error", yes, related.


OM,

please read the ReadMe.txt file at the root directory of the installer 
DMG, it contains important instructions needed to prepare you Mac for 
use with WSJT-X.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows 10 multiple problems and OS X 10.13.1 problems

[Bill Somerville]

Hi OM,

some comments in line below.

On 26/11/2017 02:34, carc...@gmail.com wrote:
Today I tried 1.8.0 release. After a few transmits the waterfall 
window would freeze.
Closing the program via the "X" in the upper right hand corner seemed 
to work, but
upon trying to start up WSJT-X again I'd get the lock file hadn't been 
deleted.


Task manager wouldn't find the executable running, but I still can't 
delete the lock file,

claiming that some program has it locked.
Boot, delete the lock file, start WSJT-X again, and eventually get the 
same results.
I seem to remember someone early-on suggesting using the "File" menu 
to exit

the program, so this problem still exists?
I suspect there is a problem with the reliability of your audio 
connections to your rig. How is your rig connected to your PC for audio?


Another problem, with the Yaesu FT-857d (4800 bps, eight bits, 1 stop 
bit) always
after transmitting the program would complain about timing out when 
trying to read
the frequency. This would occasionally also occur in 1.7.0. Now it 
happens after

every transmission.

When running FT8 retrying to establish communications with the radio 
would re-establish, but probably too late. I couldn't see if anyone 
was responding.


Make sure you do not have "Settings->Radio->Allow Tx frequency changes 
while transmitting" checked as that is not possible with the Yaesu 
FT-817/857/897(D) series of rigs.


If you are using some form of VOX, particularly the SignaLink USB for 
audio then reduce any VOX delay to the minimum. It can also help to 
switch to CAT PTT rather than VOX, even with the SignaLink USB.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows 10, PortAudio and my PC

[Bill Somerville]

On 15/06/2016 16:33, Ton PA0TBR wrote:
> I will certainly try to build WSJT-X with the port audio you provided. 
> I can do that in a few weeks after which I will let you know of the 
> results. At least I know that there might be a solution.

Hi Ton,

not WSJT-X, WSJT-X does not utilize PortAudio, it uses Qt which in turn 
access the Windows audio services directly. WSPR and WSJT use PortAudio.

73
Bill
G4WJS.


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421=/41014381
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows 10, PortAudio and my PC

[Ton PA0TBR]

Hi Bill,

Many thanks for your replies.
I had tried to rollback / reinstall / use the driver from Realtek and
booting after I deleted the driver.
I will certainly try to build WSJT-X with the port audio you provided. I
can do that in a few weeks after which I will let you know of the results.
At least I know that there might be a solution.

Many thanks!

73,
Ton pa0tbr




On 15 June 2016 at 00:05, <wsjt-devel-requ...@lists.sourceforge.net> wrote:

>From: Bill Somerville <g4...@classdesign.com>
> Subject: Re: [wsjt-devel] Windows 10, PortAudio and my PC
>
> On 14/06/2016 07:58, Ton PA0TBR wrote:
> > After I updated my PC from Windows 8.1 64 bit Pro to Windows 10 64 bit
> > Pro, when I start WSPRX 08r3058 I get the following messages:
> > - Unable to initialize PortAudio
> > - PortAudio says requested soundcard format not supported
> > - Failed to start audio input stream
> > WSPRX will then start, but without any audio devices, including no VAC's.
> >
> > My PC is a Zotac ID90 with i7-3770T CPU and uses a RealTek High
> > Definition Audio device.
> > I have reinstalled and also updated the driver but still have the same
> > result. I installed a USB Audio device as default but also with the
> > same result.
> >
> > It seems to be related to PortAudio as I also have a problem with
> > HPSDR which stops when it initializes PortAudiio. HPSDR appears to run
> > in compatibility mode though.
> > WSJTX works fine and I assume that it doesn't use the PortAudio library.
> >
> > Zotac offers no support Although they released their product only
> > 3 years ago, they claim it is discontinued and can't provide any help
> > related to Windows 10.
> >
> > Is there any experience here with such PortAudio problem and is there
> > a solution?
>
> Hi Ton,
>
> I am not aware of this issue but reading about it, it seems to be a
> driver issue and, if you have no updated sound card driver available for
> Windows 10, you may be stuck with this issue. The best advice seems to
> be to roll back the driver and use compatibility mode. Another
> possibility is to un-install the audio driver and let Windows re-install
> - some users have reported that the problem only occurs of systems that
> have been upgraded to Windows 10.
>
> If you can get to the point where you no longer get the first error
> "Unable to initialize PortAudio" then there are possible solutions by
> selecting only from the devices accessed via the DirectSound Windows
> audio API. It appears that the problem is related to the WSAPI audio API
> route to the sound devices.
>
> 73
> Bill
> G4WJS.
>
> On 14/06/2016 10:57, Bill Somerville wrote:
> > If you can get to the point where you no longer get the first error
> > "Unable to initialize PortAudio" then there are possible solutions by
> > selecting only from the devices accessed via the DirectSound Windows
> > audio API. It appears that the problem is related to the WSAPI audio
> > API route to the sound devices.
>
> Hi again Ton,
>
> here is a build of PortAudio for Windows with only the MME Audio API
> supported:
>
>
> https://dl.dropboxusercontent.com/u/4192709/portaudio-e111b3a-w32-MME-only.zip
>
> if you are able to build WSPRX then please do so using this package for
> PortAudio and see how it goes. If that doesn't work then I can provide
> versions of PortAudio with other single API support options to try.
>
> 73
> Bill
> G4WJS.
>
>
>
>
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421=/41014381___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows 10, PortAudio and my PC

[Bill Somerville]

On 14/06/2016 10:57, Bill Somerville wrote:
> If you can get to the point where you no longer get the first error 
> "Unable to initialize PortAudio" then there are possible solutions by 
> selecting only from the devices accessed via the DirectSound Windows 
> audio API. It appears that the problem is related to the WSAPI audio 
> API route to the sound devices.

Hi again Ton,

here is a build of PortAudio for Windows with only the MME Audio API 
supported:

https://dl.dropboxusercontent.com/u/4192709/portaudio-e111b3a-w32-MME-only.zip

if you are able to build WSPRX then please do so using this package for 
PortAudio and see how it goes. If that doesn't work then I can provide 
versions of PortAudio with other single API support options to try.

73
Bill
G4WJS.


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows 10, PortAudio and my PC

[Bill Somerville]

On 14/06/2016 07:58, Ton PA0TBR wrote:
After I updated my PC from Windows 8.1 64 bit Pro to Windows 10 64 bit 
Pro, when I start WSPRX 08r3058 I get the following messages:

- Unable to initialize PortAudio
- PortAudio says requested soundcard format not supported
- Failed to start audio input stream
WSPRX will then start, but without any audio devices, including no VAC's.

My PC is a Zotac ID90 with i7-3770T CPU and uses a RealTek High 
Definition Audio device.
I have reinstalled and also updated the driver but still have the same 
result. I installed a USB Audio device as default but also with the 
same result.


It seems to be related to PortAudio as I also have a problem with 
HPSDR which stops when it initializes PortAudiio. HPSDR appears to run 
in compatibility mode though.

WSJTX works fine and I assume that it doesn't use the PortAudio library.

Zotac offers no support Although they released their product only 
3 years ago, they claim it is discontinued and can't provide any help 
related to Windows 10.


Is there any experience here with such PortAudio problem and is there 
a solution?


Hi Ton,

I am not aware of this issue but reading about it, it seems to be a 
driver issue and, if you have no updated sound card driver available for 
Windows 10, you may be stuck with this issue. The best advice seems to 
be to roll back the driver and use compatibility mode. Another 
possibility is to un-install the audio driver and let Windows re-install 
- some users have reported that the problem only occurs of systems that 
have been upgraded to Windows 10.


If you can get to the point where you no longer get the first error 
"Unable to initialize PortAudio" then there are possible solutions by 
selecting only from the devices accessed via the DirectSound Windows 
audio API. It appears that the problem is related to the WSAPI audio API 
route to the sound devices.


73
Bill
G4WJS.

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows 10

[Bill Somerville]

On 11/10/2014 21:37, Michael Black wrote:
Hi Mike,
 FYI...I'm testing Windows 10 Technical Preview and am happy to report that
 WSJT-X works fine (I'm running the 1.;5 branch but I'm quite sure 1.4 will
 work too since 1.5 is not a big departure from it).
Good to know.

 It reports Qt: Untested Wnidows version 6.4 detected which I do believe
 can now be considered tested though I suppose MS could eventually break
 the thing
That's a Qt thing, we had for ages with Qt 5. At some point they will 
release an officially supported installer for Windows 10 and that will 
not pop up that message.

 I'm running it with JTAlert and a USB Signalink.

 Haven't tested logging yet or cat control which is next on my list.  I use
 HRD for cat control and Log4OM for logging.

 FTDI drivers work...the prolific cable I have does notanother strike
 against Prolific.
So I think we can assume there's not much new in Windows 10 apart from 
some start screen fluff ;)

 Mike W9MDB
73
Bill
G4WJS.

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel