Peak meter-- what does change is what the dB is measuring...peak vs RMS...it's
about 12dB more or so for peak. The peak meter should quell all the question
about how to set audio...with whatever level we determine is best. I don't
know why we need more then 30dB head room above peak level...is there some
reason not to take advantage of the more of the dynamic range of 16 bits?I also
tend to believe that the dB problem being reported < 500 Hz offset is due to
the low RMS level getting into quantization error territory. My testing shows
that 50dB peak gets rid of most of that problem..more testing is needed.
The 60M JT9 offset was moving the blue line...but not the actual offset in the
spinner.
I found having the time widget meant not having to worry about the log window
(which at times one is in a but of a hurry to keep on operating)...perhaps it
could go elsewhere on the main window. I always tend to minimize width and
whatevers unless it makes sense to have them. The progress bar on the window
shrinking is no big loss.
I had been submitting individual patches but got no feedback....gets a bit hard
to keep them all separate.But if you insist I'll split them up again so we can
discuss each individually.
de Mike W9MDB
From: Joe Taylor <j...@princeton.edu>
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Sent: Thursday, March 2, 2017 1:36 PM
Subject: Re: [wsjt-devel] Cumulative patch
Mike --
> Peak signal meter shows when clipping occurs. Based on my testing
> recommending 50-60dB on peak meter...subject to change.
Unless your patch changes what "0 dB" means, the recommended level for
background noise --no signals present -- should remain 30 dB.
Why do you recommend 20-30 dB higher ??
> Fix 60M JT9 offset
?? What does this mean?
> Update TIME_ON method to use transmit messages and adds widget on status
> bar to allow TIME_ON setting
Input widget on status bar does NOT seem like a good idea. Shouldn't
logging information be entered on on the Log QSO window?
Were you not in favor of minimizing the number and size of status bar
widgets?
Finally: it is much easier to evaluate and decide on proposed patches if
you keep each one to a single purpose. That way, we can discuss and in
due course agree on the advisability of each one, as a coherent topic.
Your "cumulative.patch" seems to address five wholly unrelated topics.
-- Joe, K1JT
------------------------------------------------------------------------------
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
