Greg Beam writes:
>
> Hello All,
>
> I've put together the rough draft / preliminary release-notes that will
> accompany the JTSDK-Win32 v2.0.4 release. The upgrade section is not yet
> functional, as I've not performed the final svn --reintegration from the
> ^/cli-test branch. This will be
Hi Joe and All,
Last couple months I have been seeing multiple occurencies of the 50Hz
amplitude modulation of the JT9
signals, that combined with the intermodulation products causes multiple
decodes of the same JT9 message with 50Hz step.
During resolution of these interference issues I have fo
I played with watching the difference and I don't see any difference if I
have the Xonar at -58dB or 0. The waterfall looks exactly the same. I
don't see anything that doesn't decode either way. Have to wait and get
some low-level signals to test some more. Too band I can't run it
side-by-side
As another data point for potential comparison. I've been running some
tests comparing the Xonar and SignaLink and never saw a problem with the
Xonar at the -58dB level. Pretty much identical sig reports between the two.
I'm doing a mod on the audio transformer on the SignaLink and when I get
that
On 20/01/2016 15:16, Bill Somerville wrote:
> I do not think either of the above are linear adjustments, they both
> amount to multiplication I believe.
Sorry, I meant to type:
I do not think either of the above are linear adjustments, they both
amount to more than multiplication I believe.
73
Bi
On 20/01/2016 14:24, Michael Black wrote:
> Isn't that all digital gain? Wouldn't you want that closer to zero?
> I see the ingain getting passed to symspec and hspec_ so what is the
> purpose of changing the scale inside symspec?
> Does this linear rescaling in symspec really matter?
Hi Mike,
t
I'll run some tests comparing the Xonar to SiganLink with the Xonar a few
points to see if it makes any difference.
In my world multiplication is a linear adjustment. The relative level
between points is exactly the same regardless of level.
1,2,3,4,5 - y=mx+b = y=1x+0
2,4,6,8,10 y=mx+b = y=2x+0
On 20/01/2016 15:47, Michael Black wrote:
> So I don't see how the scaling helps SNR or quantization since that
> should be unaffected by linear rescaling
It hinders not helps. Remember that the sample stream before it gets to
WSJT-X is 16-bit signed integer and dividing those samples by a co
Hi Guy,
QT5 (which should really say 5.2) and QT 5.5 are QT version numbers.
Just like WSJT-X, the QT folks change version numbers as they update
their Framework tools / GCC tool chains.
We were using QT version 5.2 when JTSDK v2 was first released. Then as
time progressed, QT version 5.5 was
On 20/01/2016 16:28, Greg Beam wrote:
> At present, I believe Joe / Bill are still releasing WSJT-X built with
> QT 5.2 on Windows, but a number of folks are using QT 5.5 for testing.
> This may change over the next couple releases, but when is up to Joe and
> Bill.
Hi Greg,
you may have missed my
Hi Bill,
Yes, I did not see your reply on this and I was not aware v1.6.0 was
released with QT 5.5, though I probably should have been. I must have
missed that in the shuffle somewhere.
Thanks for the Info.
73's
Greg, KI7MT
On 1/20/2016 09:33, Bill Somerville wrote:
> On 20/01/2016 16:28, Gr
On Tue,1/19/2016 4:53 PM, Joe Taylor wrote:
> Sure, we could set the level higher. WSJT-X works OK with the noise
> level set anywhere between about 20 dB (rms=10) and 60 dB (rms=1000).
> But the 16-bit A/D converter necessarily clips at ± 32767, about 90
> dB. If you set the background noise lev
Helping out somebody and he seems to have periodic problems decoding.
These 3 wav files don't decode at all.
He does have good time sync
He does have 48kHz sampling.
Apparently things go well for him for a while and then decoding fails. So
there has to be something funky with the audio here that
I didn't think to check his system for CPU usage or such. He's using a
RigBlaster.
A test procedure would very nice Joe
RRR
Mike W9MDB
On Wed, Jan 20, 2016 at 1:46 PM, Joe Taylor wrote:
> Hi Mike,
>
> W9MDB wrote:
>
> Helping out somebody and he seems to have periodic problems decoding.
>>
>>
On 20/01/2016 19:46, Joe Taylor wrote:
> The effect is similar to "key clicks". In this case the
> discontinuities are caused by gaps in the audio input.
In addition to the discontinuities I hear a buzzing noise on the signals
and I would get him to check the physical audio connections. It may
On 20/01/2016 19:46, Joe Taylor wrote:
> On close inspection, these signals do NOT look like they should decode.
> There are frequent glitches (interruptions) in the audio input stream,
> and this is bad.
Another thing of note is a strong peak at 4kHz on the last file but no
sign of that on the f
Igor, Bill, Mike --
UA3DJY wrote:
>> Hello Mike,
>>
>> Width of the tones is the reason behind it: each single tone
>> occupying spectrum of the several tones, it is Doppler effect.
>>
>> I wrote message on it to Joe K1JT some time ago, this propagation
>> issue had not high priority in the WSJT-X
Looks like he's got some 1kHz interval birdies in his audio chain
(RigBlaster).
He only has about 2500Hz bandwidth so it's not from the rig.
He has a TS-590S
I worked with him some more...he has a dual-core dual-monitor with 4gig
memory and it seemed a little stressed out.
So I bumped up wsjtx to
On 20/01/2016 22:14, Michael Black wrote:
> He has a TS-590S
Hi Mike,
you need to do Joe's test or similar. You can do this:
Set the following on the transceiver:
• Mode: CW
• AF control: Center
• Menu No. 34 (CW RX pitch): 800 Hz
• SHIFT control: 800 Hz
• RIT function: OFF
• Break-in function (V
On 20/01/2016 19:46, Joe Taylor wrote:
> On close inspection, these signals do NOT look like they should decode.
> There are frequent glitches (interruptions) in the audio input stream,
> and this is bad.
Hi Mike & all,
another cause of audio glitches is USB hubs. The USB audio streaming
protoco
That's a good one to check...along with looking at DPC Latency and ensuring
background process have priority.
I'll let you know what we find.
RRR
Mike W9MDB
On Wed, Jan 20, 2016 at 4:58 PM, Bill Somerville
wrote:
> On 20/01/2016 19:46, Joe Taylor wrote:
> > On close inspection, these signals d
Hi All,
It looks like such glitches is usual behaviour for loud JT signals, while it is
not clear if it caused by TX side, receiver, RX sound card or WSJT-X RX
processing.
Spectrum of the glitches is concentrated around the loud signal there.
73 Igor UA3DJY
>
>Date: Wed, 20 Jan 2016 17:48:39
22 matches
Mail list logo
