>From JTSDK-MSYS prompt 'which perl' yields '/bin/perl.exe'
_
Dan Malcolm CFI/II
K4SHQ
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Friday, March 03, 2017 9:22 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel]
On 04/03/2017 02:51, Dan Malcolm wrote:
> The very first error encountered is "Win32 error 998" which is translated as
> "Invalid access to memory location". Reading the Win10 Application log I
> find the faulting application is perl.exe and faulting module is
> msys-perl5_8.dll subsequent errors
All,
The very first error encountered is "Win32 error 998" which is translated as
"Invalid access to memory location". Reading the Win10 Application log I
find the faulting application is perl.exe and faulting module is
msys-perl5_8.dll subsequent errors fault the same file or state 'unknown'.
So
Hi Dan, All,
I'm not sure what's going on here either. My version of Perl, via MSYS,
is 5.8.8. I was able to build Hamlib3 from MSYS directly, and JTSDK-QT
via QT 5.2 and 5.5 without error.
As Bill suggested, log the build and post it. To eliminate JTSDK-QT ENV,
use the JTSDK-MSYS terminal, th
End of show .
El 02/03/17 a las 19:11, wsjt-devel-requ...@lists.sourceforge.net escribió:
> #4 You still haven't sent us enough of the log to see what was going on
> what it stopped...
rig_register (372)
icom_init: civ_version=1
rig_set_conf: civaddr='0x94'
rig:rig_open called
s
Hi Bill,
Some definitely do. During the time I've experimented with quadrature
sampling detectors and SDR software development I've tried a number of
soundcards. Some did have hardware attenuators and preamplifiers in the
line inputs and these needed to be offline in order to have decent dynamic
r
On 03/03/2017 19:17, Edson W. R. Pereira wrote:
> The way the signal level meter works is also very good as it measures
> the signal at the wxjt-x input in relation to the ADC floor. This, in
> my view, is the best indicator to correctly set the audio levels (at ~
> 30 dB).
Hi Edson,
that is n
On 03/03/2017 19:07, Joe Taylor wrote:
> As general statement, setting the audio level is simply not very critical.
Hi Joe,
it certainly doesn't justify the >30dB noise level on the forums -- hi
hi. Still I think every time it comes up, a few more users both
understand a bit better and realize
On 03/03/2017 19:17, Edson W. R. Pereira wrote:
> Also, some soundcards have no hardware fader control (the best ones).
Hi Edson,
I would be a little surprise if any soundcard had a hardware level
control other that mic boost. Do you know otherwise?
73
Bill
G4WJS.
Hi Joe,
I entirely agree!
73, Edson PY2SDR
On Fri, Mar 3, 2017 at 4:07 PM, Joe Taylor wrote:
> Hi Bill,
>
> Reasonable suggestion... though I suspect many users would have the
> consternation you mention, when we alter a control setting they thought
> they had control over.
>
> As for your las
Hi Bill,
The concern I have is if the control of the OS fader would be OS agnostic.
Also, some multi input/output soundcards have a collection of controls --
some independent some not. Also, some soundcards have no hardware fader
control (the best ones).
The way WXJT-X works today seems quite ade
Hi Bill,
Reasonable suggestion... though I suspect many users would have the
consternation you mention, when we alter a control setting they thought
they had control over.
As for your last question: I don't have a reference link handy, but Leif
(SM5BSZ) has shown that most "24-bit" soundcards
On 03/03/2017 18:47, Dan Malcolm wrote:
I still have the question: Are these two failures (Hamlib3 and WSJTX)
related?
Hi Dan,
I don't know. Your instinct to examine the first error message is
correct, I explained how you can do that.
73
Bill
G4WJS.
On 03/03/2017 18:30, char...@sucklingfamily.free-online.co.uk wrote:
Another option is that we could also switch the WSJT-X level control to
actually change the o/s / driver fader but note the value is in the
range 0.0 to 1.0 and I assume that 1.0 is 0 dB FS so maybe only
attenuation is available
On 03/03/2017 18:17, Clemens Heese wrote:
> Somehow I have a similar issue. Using an SDR (RedPitaya) with a variable
> gain amplifier as preamp (and a 30 MHz low pass). I am wondering how to
> best set the preamp. Currently I have just experimentally set the gain
> to get most decodes in 24h (weigh
I know its my specific to my system. Just not sure what it is. There were
no install errors. I still have the question: Are these two failures
(Hamlib3 and WSJTX) related? I think not, but you know the architecture
better than I do.
Dan Malcolm CFI/II
K4SHQ
Hi Bill and all
> Another option is that we could also switch the WSJT-X level control to
> actually change the o/s / driver fader but note the value is in the
> range 0.0 to 1.0 and I assume that 1.0 is 0 dB FS so maybe only
> attenuation is available.
>
I think this a good idea, as it makes it
Dear all,
I just followed the discussion on how to set the right background noise
level.
Somehow I have a similar issue. Using an SDR (RedPitaya) with a variable
gain amplifier as preamp (and a 30 MHz low pass). I am wondering how to
best set the preamp. Currently I have just experimentally se
On 03/03/2017 17:58, Dan Malcolm wrote:
There were so many error lines that I could not scroll back far enough
to see the first one. Experience has taught me to fix the first
reported failure first. Are these problems related?
Hi Dan,
this is something specific to your system, no one else i
On 03/03/2017 15:38, Joe Taylor wrote:
> 2. The slider should not affect the meter reading.
>
HI Joe & all,
we have another enhancement possibility available to us. WSJT-X could
set the operating system/driver fader to 0 dB as well. This may cause
some consternation amongst users who have tweake
Hi Edson,
On 3/3/2017 11:09 AM, Edson W. R. Pereira wrote:
> Hello Joe and Mike,
>
> Since I was the one who implemented the level meter, I have a
> suggestion: Please don't make the level meter change colors depending of
> the dB level. It makes it rather difficult to read for those of us with
On 03/03/2017 16:37, Joe Taylor wrote:
... But you won't gain more than about 0.005 dB in your quest to decode weak
signals.
adding to that, no one here has come close to an experiment to show that
effect. You would need to record hundreds of on air reception periods
with separate parallel i
Thanks for the explanation...helps a lot.
What about after the 2nd pass on JT65? How does that affect the noise floor?
de Mike W9MDB
From: Joe Taylor
To: WSJT software development
Sent: Friday, March 3, 2017 10:37 AM
Subject: Re: [wsjt-devel] Cumulative patch
Hi all,
For the recor
I was thinking about that too...we could also add an indicator to the dB text
so it's "+" if too high, "-" if too low, and "*" if clipping has occurred.
Those would then reset on band change or restart.
de Mike W9MDB
From: John Nelson
To: Black Michael ; WSJT software development
S
Hi all,
For the record, I want to clarify once again why it's a good idea to set
the audio level so low that 16-bit digitized samples of pure background
noise have an rms range around 30.
Seemingly very reasonably, Mike asked why would we not want to set the
level higher, thereby using more bi
On the topic of colors could I just mention that the inability to distinguish
between red and green is a common problem that occurs to many.
— John G4KLA
--
Check out the vibrant tech community on one of the world's most
Wouldn't the text color be even harder to see?Under normal ops you'd never see
the meter in yellow or red which is the goal.
de Mike W9MDB
From: Edson W. R. Pereira
To: WSJT software development
Sent: Friday, March 3, 2017 10:09 AM
Subject: Re: [wsjt-devel] Cumulative patch
Hell
Ok...gotchya'...you really think < 15dB is where we should warn if we keep
saying 30 is the target? de Mike W9MDB
From: Joe Taylor
To: WSJT software development
Sent: Friday, March 3, 2017 10:01 AM
Subject: Re: [wsjt-devel] Cumulative patch
On 3/3/2017 10:51 AM, Black Michael wrote
Hello Joe and Mike,
Since I was the one who implemented the level meter, I have a suggestion:
Please don't make the level meter change colors depending of the dB level.
It makes it rather difficult to read for those of us with not so good eyes.
It is perhaps better to change the color of the text
On 3/3/2017 10:51 AM, Black Michael wrote:
> OK...I'll do it that way. So the idea is that the colors represent
> peak values then but the meter is noise. That works.
>
> 15dB peak value though is something like 5dB RMS on my system.
> Shouldn't that be a fair bit higher for a warning? Peak wi
OK...I'll do it that way. So the idea is that the colors represent peak
values then but the meter is noise. That works.
15dB peak value though is something like 5dB RMS on my system. Shouldn't
that be a fair bit higher for a warning? Peak will alway be well above noise.
de Mike W9MDB
Mike --
I'm trying my best to make good use of your recent hard work on coding.
I think if you change the level-meter portion your "cumulative.patch" in
the following ways, it will be an improvement to the program:
1. The definition of dB level should remain as it is now, namely
pxdb=20.0*log10
On 02/03/2017 19:36, Joe Taylor wrote:
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 mi
33 matches
Mail list logo
