On Thu, Nov 8, 2018, at 23:16, Bill Somerville wrote:
> On 08/11/2018 19:56, Mikael Nousiainen wrote:
> > I've contacted PulseAudio developers and with them I was able to confirm
> > that this is indeed an issue in PulseAudio when using a monitor input in
> > certain cases. The audio does get hea
With me is the combination of Firefox and realtime scanning those two running
block everything specially when firefox is standby (no window open in browser)
Leo Bally
Ok8leo
> On 9 Nov 2018, at 06:24, Jim Shorney wrote:
>
>
> You haven't seen the way I browse. I can bring a quad core i5
You haven't seen the way I browse. I can bring a quad core i5 with 16G RAM to
its knees with 64 bit Waterfox. Easily. If I leave Firefox on the Kubuntu box
sitting on a couple of PSKReporter pages I can watch the memory usage creep up.
It's the only thing I've run on the 16G laptop that's ever hi
lol!
Firefox doesn't seem to eat up all 16 Gb of memory I have in this
Kubuntu 18.04 machine. Actually it's probably more like 8 Gb available
with VirtualBox running a win7 VM.
73
Stan
KM4HQE
On 11/8/18 10:41 PM, Jim Shorney wrote:
Web browsers leak memory. I've come to believe that it i
Web browsers leak memory. I've come to believe that it is a fundamental law of
the universe that a browser will expand until it consumes all available memory.
73
-Jim
NU0C
On Thu, 8 Nov 2018 22:05:19 -0600, Stan Gammons wrote:
>I've seen the same thing happen with Chrome and a web app we hav
I've seen the same thing happen with Chrome and a web app we have at
work. The app gets slower and slower and slower as the browser hogs up
more and more memory. Not sure which one to point the finger at. The web
app or Chrome. Were you using any web app at the time? I don't use
Chrome at home
Foe months, occasionally WSJT-X would stop decoding. The waterfall would
indicate plenty of signals and the clock was in sync but it wouldn't
decode. A restart of WSJT-X would not resolve the issue either. When it
happened, no matter which version of WSJT-X was run, none would decode any
signals..
RR Bill. I will try to record this the next time it happens.
Thanks & 73, Russ
From: Bill Somerville
Sent: Thursday, November 08, 2018 8:27 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Auto Seq hic-cup
On 09/11/2018 00:59, Russ wrote:
Sometimes, in JT65 (and maybe in MS
On 09/11/2018 00:59, Russ wrote:
Sometimes, in JT65 (and maybe in MSK144), the ability to double click
on a received call and have the messages auto generate stops working.
Hi Russ,
an example saved .WAV file that can be used to demonstrate this issue
would be helpful.
73
Bill
G4WJS.
_
On 09/11/2018 00:59, Russ wrote:
Periodically WSJT-X stops receiving.Everything seems to work, and the
noise level is still there, but the waterfall or graph does not
advance, and no signals are found.The program must be restarted to get
it working again.This has been happening even with 1.9 an
Hi All. Want to report some problems. Maybe they have been reported before but
it takes too long to go through all the messages on this forum.
I’m running RC3 on a windows 10 system.
1. I’m on MSK144 and have FTOL set to 200. I go to JT65 and set FTOL to
50. I return to MSK144 and FTO
I see a tangible improvement with the OSD decode on the newer versions,
but what comes next? The big guns in the commercial world do things
with the raw bits coming out of the modem. In this age of software,
modems tend to blend into decoders but they are separate functions.
If 2 receive s
Good evening all,
I have been chasing down an intermittent problem with RC3 as detailed below:
Rig = IC9100
PTT = CAT
Mode = MSK144
Win7 Pro Version 6.1 (Build 7601: Service Pack 1)
Installed Physical Memory (RAM 16.0 GB
Processor Intel(R) Core(TM) i7-6700K CPU @ 4.00 GHz, 4001 MHz, 4
Core(s),
It may be an older version of WSJT-X - couple of releases allowed that to
happen.
--
73’s
Tom
GM8MJV (IO85)
On 8 Nov 2018, at 21:25, Pino Zollo wrote:
> Wasn't it disabled on standard frequencies ?
>
> 73 ZP4KFX
>
>
> 212100 Tx 752 ~ KH2F ZP4KFX GG14
> 212045 -13 0.1 24
They’re running knock off software that bastardizes the F/H code. All they’re
doing is causing confusion instead.
> On Nov 8, 2018, at 4:25 PM, Pino Zollo wrote:
>
> Wasn't it disabled on standard frequencies ?
>
> 73 ZP4KFX
>
> 212100 Tx 752 ~ KH2F ZP4KFX GG14
> 212045 -13 0.1 2493 ~ ZP4KFX
Wasn't it disabled on standard frequencies ?
73 ZP4KFX
212100 Tx 752 ~ KH2F ZP4KFX GG14
212045 -13 0.1 2493 ~ ZP4KFX UN3GX MN83
212115 -12 0.4 695 ~ ZP4KFX KH2F -25
212130 Tx 752 ~ KH2F ZP4KFX R-12
212115 -10 0.1 2493 ~ ZP4KFX UN3GX MN83
212145 -9 0.3 695 ~ ZP4KFX RR73; SP9HZW -22
212200 T
On 08/11/2018 19:56, Mikael Nousiainen wrote:
I've contacted PulseAudio developers and with them I was able to confirm that
this is indeed an issue in PulseAudio when using a monitor input in certain
cases. The audio does get heavily distorted (I was finally able to record it)
and that is the
On Thu, Nov 8, 2018, at 13:47, Bill Somerville wrote:
> On 08/11/2018 11:36, Mikael Nousiainen wrote:
> > So considering these points, I would say that this is_certainly_ not about
> > the time offsets or about the quality of the audio received by the browser.
> >
> > -Mikael
>
> Hi Mikael,
>
>
On 08/11/2018 11:36, Mikael Nousiainen wrote:
So considering these points, I would say that this is_certainly_ not about the
time offsets or about the quality of the audio received by the browser.
-Mikael
Hi Mikael,
I can only suggest you take this up with the pulseaudio developers. A
null
Thanks for the comments. I do know that the network connection will be a factor
in unrealiability of FT8 decoding, however, I've measured the latency to be
very low, around 100-200ms all the time. The audio codec being used is Opus
with 64 kbps wide-band encoding, which is definitely enough for
On 08/11/2018 09:01, Mikael Nousiainen wrote:
I've got a very weird issue with PulseAudio when trying to route audio
from one application (Firefox 64.0b7 (64-bit)) to another one (WSJT-X v1.9.1).
I'm experiencing the same issue with different browsers (Chrome and Chromium
too).
The browser is re
On Thu, Nov 08, 2018 at 11:01:28AM +0200, Mikael Nousiainen wrote:
> I've got a very weird issue with PulseAudio when trying to route audio
> from one application (Firefox 64.0b7 (64-bit)) to another one (WSJT-X v1.9.1).
> I'm experiencing the same issue with different browsers (Chrome and Chromium
I've got a very weird issue with PulseAudio when trying to route audio
from one application (Firefox 64.0b7 (64-bit)) to another one (WSJT-X v1.9.1).
I'm experiencing the same issue with different browsers (Chrome and Chromium
too).
The browser is receiving audio from a radio transceiver through a
23 matches
Mail list logo
