Re: [wsjt-devel] PulseAudio null sink monitor gives distorted audio randomly
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 heavily distorted (I was finally able to > > record it) and that is the reason why WSJT-X is unable to decode the > > signals. > > > > On the other hand, the distortion issue does not occur always and I was > > able to keep WSJT-X decoding FT8 in the background for several hours > > without any sync issues. Complete QSOs via bidirectional WebRTC connection > > to a transceiver (using an IC-7300) work very well also! The software I'm > > testing is a ham radio remote control server written by me... > > > > Thanks for the quick answers! > > > > -Mikael > > Hi Mikael, > > let's hope the pulseaudio developers can fix this quickly as correctly > working audio loopbacks are essential for SDR users also. Do you know > the "certain cases" are that cause the issue? > > 73 > Bill > G4WJS. Hi Bill, They seem to have an idea of what the underlying bug is, see discussion here: https://lists.freedesktop.org/archives/pulseaudio-discuss/2018-November/030608.html I was not able to find a clear pattern. Sometimes it works, sometimes restarting PulseAudio, the browser and WSJT-X helps, sometimes it doesn't. Not exactly sure what they mean with "rewinding" the monitor ... sounds like it may have something to do with latency/jitter buffers. 73, Mikael OH3BHX ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X stops decoding: Found out why
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 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 hit swap. > > 73 > > -Jim > NU0C > > On Thu, 8 Nov 2018 22:52:57 -0600, Stan Gammons wrote: > >> 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 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 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. I use Firefox.Ã Have you tried to duplicate the problem with Firefox? 73 Stan KM4HQE On 11/8/18 9:48 PM, Richard Zwirko - K1HTV wrote: > 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.. > > The cause was traced to my Chrome browser. After not closing the > browser for many days, Chrome continued to hog more and more memory. > Eventually there came a point that so much memory was being used by > Chrome that WSJT-X would not decode. The fix was to close Chrome, then > restart it. With all of the URLs that previously were running started > up again, WSJT-X would once again decode.normally. > > Just thought I'd share this with other Chrome users that may have > experienced the same decoding failure. > > 73, > Rich - K1HTV > > -- > > "Good men dont need rules. Today is not the day to find out why I have so > many." - Doctor Who > > > > > ___ > 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] WSJT-X stops decoding: Found out why
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 hit swap. 73 -Jim NU0C On Thu, 8 Nov 2018 22:52:57 -0600, Stan Gammons wrote: >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 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 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. I use Firefox.Ã Have you tried to duplicate the problem >>> with Firefox? >>> >>> >>> 73 >>> >>> Stan >>> KM4HQE >>> >>> >>> On 11/8/18 9:48 PM, Richard Zwirko - K1HTV wrote: 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.. The cause was traced to my Chrome browser. After not closing the browser for many days, Chrome continued to hog more and more memory. Eventually there came a point that so much memory was being used by Chrome that WSJT-X would not decode. The fix was to close Chrome, then restart it. With all of the URLs that previously were running started up again, WSJT-X would once again decode.normally. Just thought I'd share this with other Chrome users that may have experienced the same decoding failure. 73, Rich - K1HTV -- "Good men dont need rules. Today is not the day to find out why I have so many." - Doctor Who ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X stops decoding: Found out why
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 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 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. I use Firefox. Have you tried to duplicate the problem with Firefox? 73 Stan KM4HQE On 11/8/18 9:48 PM, Richard Zwirko - K1HTV wrote: 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.. The cause was traced to my Chrome browser. After not closing the browser for many days, Chrome continued to hog more and more memory. Eventually there came a point that so much memory was being used by Chrome that WSJT-X would not decode. The fix was to close Chrome, then restart it. With all of the URLs that previously were running started up again, WSJT-X would once again decode.normally. Just thought I'd share this with other Chrome users that may have experienced the same decoding failure. 73, Rich - K1HTV -- The universe we're in will reach absolute zero in three hours. Safe is relative. - Idris, "The Doctor's Wife" ___ 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] WSJT-X stops decoding: Found out why
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 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. I use Firefox. Have you tried to duplicate the problem >with Firefox? > > >73 > >Stan >KM4HQE > > >On 11/8/18 9:48 PM, Richard Zwirko - K1HTV wrote: >> 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.. >> >> The cause was traced to my Chrome browser. After not closing the >> browser for many days, Chrome continued to hog more and more memory. >> Eventually there came a point that so much memory was being used by >> Chrome that WSJT-X would not decode. The fix was to close Chrome, then >> restart it. With all of the URLs that previously were running started >> up again, WSJT-X would once again decode.normally. >> >> Just thought I'd share this with other Chrome users that may have >> experienced the same decoding failure. >> >> 73, >> Rich - K1HTV -- The universe we're in will reach absolute zero in three hours. Safe is relative. - Idris, "The Doctor's Wife" ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X stops decoding: Found out why
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. I use Firefox. Have you tried to duplicate the problem with Firefox? 73 Stan KM4HQE On 11/8/18 9:48 PM, Richard Zwirko - K1HTV wrote: 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.. The cause was traced to my Chrome browser. After not closing the browser for many days, Chrome continued to hog more and more memory. Eventually there came a point that so much memory was being used by Chrome that WSJT-X would not decode. The fix was to close Chrome, then restart it. With all of the URLs that previously were running started up again, WSJT-X would once again decode.normally. Just thought I'd share this with other Chrome users that may have experienced the same decoding failure. 73, Rich - K1HTV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] WSJT-X stops decoding: Found out why
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.. The cause was traced to my Chrome browser. After not closing the browser for many days, Chrome continued to hog more and more memory. Eventually there came a point that so much memory was being used by Chrome that WSJT-X would not decode. The fix was to close Chrome, then restart it. With all of the URLs that previously were running started up again, WSJT-X would once again decode.normally. Just thought I'd share this with other Chrome users that may have experienced the same decoding failure. 73, Rich - K1HTV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Auto Seq hic-cup
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 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. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Auto Seq hic-cup
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. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Auto Seq hic-cup
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 and 1.8 versions, and on multiple computers.(I would guess that one of the program threads is dying.) Hi Russ, this is common with USB connected audio devices and is usually due to Windows powering down the USB hub to save energy. You can stop this happening, firstly go to Device Manager and right-click each USB hub device and navigate to the power settings and disallow Windows powering it down, secondly go to Windows power settings and in the power plan advanced properties disallow Windows selective suspend in USB settings. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Auto Seq hic-cup
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 FTOL there is now at 50. It took me quite a while to discover why I was not decoding pings on MSK144… 2. On both of the above modes the SH and Auto Sequence checkboxes keep getting unchecked. This is particularly true in JT65 mode, but it happens in MSK as well. They get unchecked while using the program (don’t have a tested scenario), and they sometimes do not stay checked after a restart. 3. In JT65 mode the auto sequencing does not work right. For example, when a station answers by sending calls and an OOO report, the next sequence for me would be to send just RO (when SH is checked). But the program starts sending calls and OOO report instead. Then when advancing from RO to 73, it just continues sending RO. 4. 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 and 1.8 versions, and on multiple computers. (I would guess that one of the program threads is dying.) 5. Sometimes, in JT65 (and maybe in MSK144), the ability to double click on a received call and have the messages auto generate stops working. Hope this helps, 73 – Russ K2TXB ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Next Generation Decoder
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 sources were available, sync'd in time, I wonder if some type of "bit combining" could be done? I have been running tests between different types of antennas, each on its own identical type receiver, and see that there may be some gain from spacial diversity. Just thinking out loud!! -Jim WA2ZKD ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] RC3 HamLib Error
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), 8 Logical Processor(s) Symptoms: When calling CQ, program would randomly stop keying the radio (but the display would still show that it was commanding transmit. Then, when I went to shut down the application and restart, it would refuse to restart due to a stale lock file. wsjtx.exe*32 was still a running process (as was jt9.exe), and task manager would shut down jt9.exe but not wsjt.exe*32. I had to reboot the computer to clear the lock file and restart the application. Tonight, the application immediately brought up the Rig Control Error. While all the settings are unchanged, it will not respond to the Test CAT button, and the details on the Rig Control Error show: Hamlib error: IO error while opening connection to rig. The only way to recover from this error is to load WSJT-X v 1.9.1. All of the radio settings remain the same, but the communications between the application and the radio now work. Installed rc3 over top of 1.9.1 again, and now I have (for now) the ability to continue running RC3 and finding some additional corner cases. I have no additional applications loaded ... I did load one software package, and when I noticed this issue, uninstalled it and cleaned the registry, and then reinstalled RC3; but no change. While I suspect an issue with Hamlib, I can't be certain. If you need additional information, please let me know. As a postscript, while I was writing this message, the application (wsjtx v2.0 rc3) has once again locked up. I now have to reboot to clear the lock file again, as attempts to reinstall fail (can't terminate the wsjtx.exe*32 process, and installation fails with a multitude of QT*dll errors. 73, Rick NM3G ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Fox at 7074 ?
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 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 Tx 752 ~ KH2F ZP4KFX R-12 > > ___ > 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] Fox at 7074 ?
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 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 Tx 752 ~ KH2F ZP4KFX R-12 > ___ > 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] Fox at 7074 ?
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 Tx 752 ~ KH2F ZP4KFX R-12 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] PulseAudio null sink monitor gives distorted audio randomly
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 reason why WSJT-X is unable to decode the signals. On the other hand, the distortion issue does not occur always and I was able to keep WSJT-X decoding FT8 in the background for several hours without any sync issues. Complete QSOs via bidirectional WebRTC connection to a transceiver (using an IC-7300) work very well also! The software I'm testing is a ham radio remote control server written by me... Thanks for the quick answers! -Mikael Hi Mikael, let's hope the pulseaudio developers can fix this quickly as correctly working audio loopbacks are essential for SDR users also. Do you know the "certain cases" are that cause the issue? 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] PulseAudio null sink monitor gives distorted audio randomly
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, > > I can only suggest you take this up with the pulseaudio developers. A > null sync loopback with no rate conversion should be a trivial buffer > copying exercise and certainly should not be introducing any distortion > apart from maybe a tiny extra bit of latency. > > It may be worth recording the null sync monitor device and looking at > the time domain spectrum in detail around the periods when artefacts are > visible on the WSJT-X waterfall. > > 73 > Bill > G4WJS. 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 reason why WSJT-X is unable to decode the signals. On the other hand, the distortion issue does not occur always and I was able to keep WSJT-X decoding FT8 in the background for several hours without any sync issues. Complete QSOs via bidirectional WebRTC connection to a transceiver (using an IC-7300) work very well also! The software I'm testing is a ham radio remote control server written by me... Thanks for the quick answers! -Mikael ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] PulseAudio null sink monitor gives distorted audio randomly
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 sync loopback with no rate conversion should be a trivial buffer copying exercise and certainly should not be introducing any distortion apart from maybe a tiny extra bit of latency. It may be worth recording the null sync monitor device and looking at the time domain spectrum in detail around the periods when artefacts are visible on the WSJT-X waterfall. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] PulseAudio null sink monitor gives distorted audio randomly
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 all narrow-band digital modes. An additional reason to why I'm being optimistic is that this setup works very reliably in Windows with VB Audio Virtual Cable and I also usually get 100% successful decoding when playing through speakers and using microphone as audio input -> and I assume going through sound hardware introduces even more artifacts and higher latency than loopback internally in PulseAudio. So there is definitely something weird going on with loopback audio and I can't figure out what. I've tried to disable sample rate conversion and remixing in PulseAudio daemon.conf (and restart PulseAudio after that, of course), but neither would help. 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 On Thu, Nov 8, 2018, at 13:17, Bill Somerville wrote: > 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 receiving audio from a radio transceiver through a WebRTC > > connection and I'm feeding it to WSJT-X to decode the data in the audio > > signal. > > Hi Mikael, > > you are being very optimistic to expect audio delivered from a remote > web SDR receiver will decode reliably in WSJT-X. There are several > factors that are likely to contribute to unreliability. Firstly as you > imply latency in the connection may exceed the allowable time offset for > the mode being decoded. The web link likely uses aggressive and variable > audio compression that will leave artefacts after expansion. Glitches > will occur when latency changes and the stream is re-aligned. It may > also be as simple as rate conversions being applied through the > pulseaudio loopback hookup (the null sinks) that do not respond well in > the presence of the above distortions. > > 73 > Bill > G4WJS. > > > > ___ > 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] PulseAudio null sink monitor gives distorted audio randomly
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 receiving audio from a radio transceiver through a WebRTC connection and I'm feeding it to WSJT-X to decode the data in the audio signal. Hi Mikael, you are being very optimistic to expect audio delivered from a remote web SDR receiver will decode reliably in WSJT-X. There are several factors that are likely to contribute to unreliability. Firstly as you imply latency in the connection may exceed the allowable time offset for the mode being decoded. The web link likely uses aggressive and variable audio compression that will leave artefacts after expansion. Glitches will occur when latency changes and the stream is re-aligned. It may also be as simple as rate conversions being applied through the pulseaudio loopback hookup (the null sinks) that do not respond well in the presence of the above distortions. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] PulseAudio null sink monitor gives distorted audio randomly
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 > too). > The browser is receiving audio from a radio transceiver through a WebRTC > connection and I'm feeding it to WSJT-X to decode the data in the audio > signal. > > I'm using two module-null-sink modules to transfer the audio between > the browser and WSJT-X. I use a simpler approach: using pavucontrol I set the input of wsjt-x to 'monitor of PC internal audio' which is the sound output device used by my browser. This works forwarding audio from the utwente websdr from firefox. This fails with a local gqrx decoding a local rtl-sdr with HF upconvertor. I see the FT8 trails wobble too much within the 15 second period. I can change the frequency wobble by touching the rtl-sdr, so the source of the problem is very clear. Koos PE4KH -- Amateur station PE4KH https://pe4kh.idefix.net/ ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] PulseAudio null sink monitor gives distorted audio randomly
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 WebRTC connection and I'm feeding it to WSJT-X to decode the data in the audio signal. I'm using two module-null-sink modules to transfer the audio between the browser and WSJT-X. I use pavucontrol to make the browser play audio to null sink called "radio-output" and then let WSJT-X listen to the audio via "radio-output.monitor". The kind of setup exists for transmitted audio where WSJT-X feeds audio to the browser through a null sink called "radio-input". However, the issue her is that WSJT-X is mostly not able to decode the data when it's using "radio-output.monitor" as audio input. Sometimes it works and sometimes it does not. As a technical detail, I'm trying to decode FT8 digital mode traffic and I've confirmed that the reason is not related to bad time sync (which FT8 requires), because I can even play the browser audio through laptop speakers and let WSJT-X use the laptop microphone as audio input and it decodes the data just fine -- the audio sounds clean and strong with no audible artifacts. By looking at the waterfall display of WSJT-X when using "radio-output.monitor" as audio input, I can see some artifacts appearing randomly in the frequency domain data -- I would call this distortion, but it's hard to know as I cannot hear it. I can set up a loopback module to feed "radio-output.monitor" to the speakers and the audio sounds fine. Lowering the incoming volume radically, e.g. to 10-20% of the full volume, does not help. And occasionally, couple of times a minute -- and sometimes for a longer period of time -- these artifacts disappear and WSJT-X is able to decode all data flawlessly. Please see this screenshot for details: https://ibb.co/eiEo0A I'm using a powerful PC (a quad-core Xeon with 48GB RAM) running Fedora 28 with latest updates applied and CPU usage is quite low (20-30%) during decoding. PulseAudio version is 12.2-rebootstrapped packaged by Fedora 28. Pulseaudio daemon.conf has default settings, except for the sample rate: default-sample-format = s16le default-sample-rate = 48000 Also, I have the following null sink / loopback setup in default.pa file: # Loopback devices load-module module-null-sink sink_name=radio-output sink_properties=device.description="radio-output" load-module module-null-sink sink_name=radio-input sink_properties=device.description="radio-input" load-module module-loopback source=radio-output.monitor latency_msec=100 adjust_time=0 rate=48000 load-module module-loopback source=radio-input.monitor latency_msec=100 adjust_time=0 rate=48000 The latter loopback modules are there so that I can hear what is being fed into the null sinks, but I've confirmed the same behavior even *WITHOUT* the loopback modules. I've also set up a fixed latency range for the hardware sound cards, but I believe this should not have any effect on the null sinks or loopback modules: load-module module-udev-detect tsched=yes tsched_buffer_size=65536 fixed_latency_range=yes I am not sure if these audio artifacts are caused by PulseAudio, WSJT-X or some specific configuration issue in my system. Any ideas? ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
