Re: [wsjt-devel] Hound mode stops decodes?

On 8/7/19 12:06 AM, Bill Richter wrote: Hi Bill, Bill, decoding other transmissions can be helpful in assessing propagation. Using tools such as PSKreporter is more useful because you can see where and how your own signal can be received. Of course, PSKreporter cannot be used if there is no

Re: [wsjt-devel] Hound mode stops decodes?

On 8/6/19 2:44 PM, jarmo wrote: Hi Jarmo & all, There is no advantage to decoding other hound stations when they are not in QSO with the Fox. Except you want to find free place for TX :) If any... To find a free place for TX, it's not necessary to decode the other hound stations, because

Re: [wsjt-devel] Hound mode stops decodes?

Oops, i meant fastest of course. N Avg 1. 73 -Jim NU0C On Tue, 6 Aug 2019 23:11:40 -0500 Jim Shorney wrote: > run the waterfall at it's slowest speed ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/list

Re: [wsjt-devel] Hound mode stops decodes?

And, not all are decoded either! Either way you will miss some but in the waterfall you will see a signal there even with no decode. I find that when I run the waterfall at it's slowest speed I can as well actually see things that are happening to the signals instead of just blotches of color.

Re: [wsjt-devel] Hound mode stops decodes?

Tue, 6 Aug 2019 20:43:46 -0500 Jim Shorney kirjoitti: > I must be weird, I just use the waterfall for this. > > 73 > > -Jim > NU0C Yup, mostly that way, but, not all seen in waterfall. I don't want gain waterfall so, that it's like snofall to see these -20 stations.. Jarmo __

Re: [wsjt-devel] Hound mode stops decodes?

I must be weird, I just use the waterfall for this. 73 -Jim NU0C On Tue, 6 Aug 2019 11:52:42 -0400 Eric Spero via wsjt-devel wrote: > I had to > figure out why I was not seeing the others decoded signalsso I could > insure I was not TX on another ham using the same offset I was.

Re: [wsjt-devel] Hound mode stops decodes?

Yeah, that's the same thing I saw. Bill, decoding other transmissions can be helpful in assessing propagation. -- Thanks, Bill > On August 6, 2019 at 8:52 AM Eric Spero via wsjt-devel > wrote: > > > I too had this issue, on the latest release, when I updated.  I think in > the latest relea

Re: [wsjt-devel] WSJT-X Audio dropout issue

Hi Bill, This is the way it works fine in the VM: WSJT-X Audio settings Connect Audio interface with the Mac host machine; Windows 10 in Parallels menu -> sound output and microphone -> in and out by Audio interface connected to Mac host machine; WSTJ-X audio in en out by Default audio in and ou

Re: [wsjt-devel] WSJT-X Audio dropout issue

Hi Hans, thanks for the update and glad you have a solution. In general using virtualization often adds extra layers of virtual device drivers, these will not necessarily perform as well as running the operating system and drivers directly on the bare metal CPU. 73 Bill G4WJS. On 06/08/2019

Re: [wsjt-devel] WSJT-X Audio dropout issue

Hi OMs! Interesting! I’m using Parallels on Mac OSX and running W10 When I use the soundcard directly in windows, its dropping audio When I use the sc with the parallels as default and allocate it within OSX as sc, no problem!! It seems that the issue is Parallels, passing the direct audio thr

Re: [wsjt-devel] WSJT-X Audio dropout issue

On 06/08/2019 20:55, Black Michael via wsjt-devel wrote: Can you check LatencyMon and see if you have some ill-behaving interrupts? The default buffer size for Wnidows audio is supposed to be 4.16 seconds (200*1000)/48000 though Qt claims it's not guaranteed. https://doc.qt.io/qt-5/qaudioinpu

Re: [wsjt-devel] Two recommendations

On 06/08/2019 15:57, Black Michael via wsjt-devel wrote: The solution to prevent extra files and extra program entries is to NOT put the version # in the installer application name.  It should just be "WSJTX" and not "WSJT x.x.x". That's what causes the multiple program entries that are difficul

Re: [wsjt-devel] WSJT-X Audio dropout issue

Can you check LatencyMon and see if you have some ill-behaving interrupts? The default buffer size for Wnidows audio is supposed to be 4.16 seconds (200*1000)/48000 though Qt claims it's not guaranteed. https://doc.qt.io/qt-5/qaudioinput.html#setBufferSize Mike On Tuesday, August 6, 2019,

Re: [wsjt-devel] WSJT-X Audio dropout issue

Hi Mike, Yes, it is 48Khz. It is using Standard Microsoft USB Audio CODEC driver. Playing audio from a audio generator in Windows via this soundcard works fine. https://www.nch.com.au/tonegen/index.html Playing continuous audio while testing with ’TU

Re: [wsjt-devel] WSJT-X Audio dropout issue

What's does the Behringer's USB driver show for the data rate?  Should be 48kHz de Mike W9MDB On Tuesday, August 6, 2019, 02:10:45 PM CDT, Hans Schiessl wrote: WSJT-X version: 2.10Platform: Windows 10Audio interface: USB Behringer UCA222Both on 32 and 64 bit tested Issue:When sendin

[wsjt-devel] WSJT-X Audio dropout issue

WSJT-X version: 2.10 Platform: Windows 10 Audio interface: USB Behringer UCA222 Both on 32 and 64 bit tested Issue: When sending FT8 signals or testing with TUNE, with this UCA222 audio interface I get dropouts on the audiosignal randomly. Eg: sending 3 seconds, 0,5 s dropout, sending 5 seconds,

Re: [wsjt-devel] Hound mode stops decodes?

I too had this issue, on the latest release, when I updated.  I think in the latest release the box might have gotten uncheck somehow. I had to figure out why I was not seeing the others decoded signalsso I could insure I was not TX on another ham using the same offset I was. On 8/6/2019 8:44

Re: [wsjt-devel] Two recommendations

I have been working and helping other hams who are using wsjt-x since it came out. I noticed many of the hams who have the OS "Windows", will end up with parts of the older versions listed  of wsjt-x in their installed App listings. If the users click on one of the older versions to uninstall i

Re: [wsjt-devel] Patch Submission: Log Window : MainWindow::aceptQSO()

I just confirmed this behavior.  If you re-enable during the LogQSO popup it gets turned of when you click OK. de Mike W9MDB On Tuesday, August 6, 2019, 09:40:29 AM CDT, Dave Slotter, W3DJS wrote: No, it's not happening because of 73 messages. Please re-read what I wrote before and

Re: [wsjt-devel] Two recommendations

The solution to prevent extra files and extra program entries is to NOT put the version # in the installer application name.  It should just be "WSJTX" and not "WSJT x.x.x".That's what causes the multiple program entries that are difficult to remove. I don't what's being used an installer but ei

Re: [wsjt-devel] Patch Submission: Log Window : MainWindow::aceptQSO()

No, it's not happening because of 73 messages. Please re-read what I wrote before and it should become clear to you that it is happening due to the Logging window code. -- Dave Slotter, W3DJS On Tue, Aug 6, 2019 at 8:50 AM Matthew Miller wrote: > Are you sure its

Re: [wsjt-devel] Two recommendations

On 8/5/2019 12:07 PM, Black Michael via wsjt-devel wrote: If you install 2.1.0 over 2.0.0 for example you end up with two listings in the App manager. If you try to uninstall 2.0.0 it fails.  The only fix is to reinstall 2.0.0 so you can uninstall itthen reinstall 2.1.0 It's the setup that

Re: [wsjt-devel] Patch Submission: Log Window : MainWindow::aceptQSO()

Are you sure its when you hit OK and not the next 7.5 sec interval with the other station still sending 73? I have frequently had problems where the Enable button is shut iff repeatedly because the station I just worked keeps sending the 73 message over and over and every time it disables my TX

Re: [wsjt-devel] Hound mode stops decodes?

Tue, 6 Aug 2019 13:14:28 +0100 Bill Somerville kirjoitti: > Hi Mike, > > correct and it has always been unchecked by default. There is no > advantage to decoding other hound stations when they are not in QSO > with the Fox. > > 73 > Bill > G4WJS. Except you want to find free place for TX :) I

Re: [wsjt-devel] Hound mode stops decodes?

Hi Mike, correct and it has always been unchecked by default. There is no advantage to decoding other hound stations when they are not in QSO with the Fox. 73 Bill G4WJS. On 06/08/2019 13:03, Black Michael via wsjt-devel wrote: Been there for quite a while...couldn't tell you exactly when it

Re: [wsjt-devel] Hound mode stops decodes?

Been there for quite a while...couldn't tell you exactly when it was added but I'm pretty sure it was early in the Fox/Hound development. Mike On Tuesday, August 6, 2019, 12:26:53 AM CDT, Bill Richter wrote: Is it new or did it just get unchecked during an update? I know it was wor

Re: [wsjt-devel] Hound mode stops decodes?

Tnx, Kari! 73 de Tom OH6VDA > 6. aug. 2019 kl. 12:58 skrev Kari : > >> On 6.8.2019 12.19, Tom Ramberg via wsjt-devel wrote: >> I have wondered about the same, and I cannot find any "Rx all freqs" >> anywhere in the settings. Please point me in the right direction. >> 73 de Tom OH6VDA > > Tom,

Re: [wsjt-devel] Hound mode stops decodes?

On 6.8.2019 12.19, Tom Ramberg via wsjt-devel wrote: I have wondered about the same, and I cannot find any "Rx all freqs" anywhere in the settings. Please point me in the right direction. 73 de Tom OH6VDA Tom, when in 'Hound' mode ( File => Settings => Advanced ) ... ..the option  "Rx All F

Re: [wsjt-devel] Hound mode stops decodes?

I have wondered about the same, and I cannot find any "Rx all freqs" anywhere in the settings. Please point me in the right direction. 73 de Tom OH6VDA > 6. aug. 2019 kl. 08:26 skrev Bill Richter : > > Is it new or did it just get unchecked during an update? I know it was > working before, but