[wsjt-devel] Possible V 2.0 rc3 issue ?

2018-10-28 Thread Mark Spencer
Changing focus between WSJT-X 2.0 RC 3 and other windows apps can cause dropouts in Tx Audio at times. PC is running Windows 7. Am sending audio to the transmitter via the PC sound card. I noticed this while calling CQ with MSK144 in North American Contest Mode. If there is any interest I

Re: [wsjt-devel] wsjt-x 2 wspr SNR

2018-10-28 Thread Rob Robinett
Hi Steve, I was not aware of the additional command line flags until your email and a chat from Jim. It does increase CPU utilization enough that a Pi can no longer perform two wsprd decodes on each of the 11 bands, so I have divided the bands across 2 Pis. In addition, I have modified my script

Re: [wsjt-devel] Flex Split Operation Setup with WSJT-X

2018-10-28 Thread Marco Calistri via wsjt-devel
Il 28/10/18 10:45, Black Michael via wsjt-devel ha scritto: > The directions are missing the phrase "if your rig is capable of it".  > Kind of assumes everybody understands this stuff. Probably I'm not "so smart as_"everybody_ is to _understand this stuff"_. I'm sorry to bore the ML with obvious

Re: [wsjt-devel] Flex Split Operation Setup with WSJT-X

2018-10-28 Thread Marco Calistri via wsjt-devel
Il 28/10/18 12:29, Bill Somerville ha scritto: > On 28/10/2018 13:45, Black Michael via wsjt-devel wrote: >> The directions are missing the phrase "if your rig is capable of >> it".  Kind of assumes everybody understands this stuff. >> >> Bandwidth settings are on of the big variables on rigs

Re: [wsjt-devel] failure WSJT-X 2.0.0 rc3

2018-10-28 Thread Saku
Hi ! - Now as Mike has reported a bug below I will release this mail that I was writing a while ago. I did not sent it as I could not reproduce bug for sure. Difference to Mike's observation was that I did not initiate qsos from wsjtx main window but from companion

Re: [wsjt-devel] wsjt-x 2 wspr SNR

2018-10-28 Thread Steven Franke via wsjt-devel
Jim, The number in question is the total Fano path metric for the returned codeword. When the last number is 1, that means that the Fano algorithm failed. In such cases, the path metric is just set to its maximum possible value, 810. Steve k9an > On Oct 28, 2018, at 11:31 AM, Jim Lill wrote:

Re: [wsjt-devel] wsjt-x 2 wspr SNR

2018-10-28 Thread Jim Lill
Steve, What does the number before the 0 or 1 in ALL_WSPR.TXT represent? I see it as 810 when there's a 1 (new algo) decode -Jim wa2zkd On 10/28/2018 12:28 AM, Steven Franke via wsjt-devel wrote: Hi Rob - Are you using the same command-line arguments that WSJT-X uses when it calls the

Re: [wsjt-devel] Flex Split Operation Setup with WSJT-X

2018-10-28 Thread Bill Somerville
On 28/10/2018 13:45, Black Michael via wsjt-devel wrote: The directions are missing the phrase "if your rig is capable of it".  Kind of assumes everybody understands this stuff. Bandwidth settings are on of the big variables on rigs and have generally gotten wider as the years have gone on.

Re: [wsjt-devel] failure WSJT-X 2.0.0 rc3

2018-10-28 Thread Black Michael via wsjt-devel
That would (should) have no bearing.Mike On Sunday, October 28, 2018, 8:42:19 AM CDT, Mike wrote: More on previous reply, I will using hold tx frequency if that could have any bearing. Mike On 10/28/2018 6:03 AM, Black Michael via wsjt-devel wrote: You must be

Re: [wsjt-devel] Flex Split Operation Setup with WSJT-X

2018-10-28 Thread Black Michael via wsjt-devel
The directions are missing the phrase "if your rig is capable of it".  Kind of assumes everybody understands this stuff. Bandwidth settings are on of the big variables on rigs and have generally gotten wider as the years have gone on. So...if your FT-100 cannot widen bandwidth you are stuck

Re: [wsjt-devel] failure WSJT-X 2.0.0 rc3

2018-10-28 Thread Mike
More on previous reply, I will using hold tx frequency if that could have any bearing. Mike On 10/28/2018 6:03 AM, Black Michael via wsjt-devel wrote: You must be double-clicking the wrong message. If this was a bug we'd have all sorts of complaints. Can you give an example of what you are

Re: [wsjt-devel] failure WSJT-X 2.0.0 rc3

2018-10-28 Thread Mike
It was a transient thing. I clicked on a station on the band activity list, which should change the messages down below, but they did not change. The messages stayed the same, even though I clicked on another station in the list. I went back to the current version and it did not show the

Re: [wsjt-devel] Flex Split Operation Setup with WSJT-X

2018-10-28 Thread Marco Calistri via wsjt-devel
Il 27/10/18 21:58, Bill Somerville ha scritto: > On 28/10/2018 01:30, Morris Wideman via wsjt-devel wrote: >> My MP does not put out full power but if you have a way to increase >> the TX audio level such as mic gain then this is not that big a problem. > > Morris, > > this is a very bad idea.

Re: [wsjt-devel] failure WSJT-X 2.0.0 rc3

2018-10-28 Thread Black Michael via wsjt-devel
You must be double-clicking the wrong message.If this was a bug we'd have all sorts of complaints. Can you give an example of what you are clicking on, what you expect, and what you get? de Mike W9MDB On Sunday, October 28, 2018, 5:08:59 AM CDT, Mike wrote: When I was using it

Re: [wsjt-devel] FTdx3000

2018-10-28 Thread Tom Ramberg via wsjt-devel
I'm using the FTdx5000 definition for JW6VDA and JW5E, JQ78tf. Works great. 73 de Tom OH6VDA > 26. okt. 2018 kl. 05:24 skrev Black Michael via wsjt-devel > : > > Have you tried any others? Maybe the FTdx5000? > > Looks like the 3000 has the same command set. > > If it does work we can add

[wsjt-devel] failure WSJT-X 2.0.0 rc3

2018-10-28 Thread Mike
When I was using it with the tx fq locked, when I double clicked on a new station, the information below did not update and transmitted the previous station information instead of the station I had just double clicked. Haven't succeed making any contacts, but station is not power house and

[wsjt-devel] WSJT-X v2.0.0 rc3... JT4 SNR dependant on Tol

2018-10-28 Thread Allan Downie
Firstly, thanks to Joe for increasing the JT4 SNR to something more usable. Our local beacons run JT4D on 70cm and JT4F on 23cm. I have noticed that if I choose a Tol of less than 100Hz I get a realistic SNR. 100Hz Tol or greater results in something 15 or 20dB weaker reported. I have tested