Re: [wsjt-devel] r6758 wide graph opens instead of fast graph

[Steven Franke]

Hi Bill,
I found another symptom. When I open wsjt-x, the wide graph appears, as I 
stated. It turns out that there is also a small “orphan” window that stays 
around even after I close the wide graph. The screen shot shows the state of my 
screen just after opening wsjt-x. Note the small orphan window just under the 
“UTC” label on the main window.
Steve




> On Jun 10, 2016, at 10:18 PM, Steven Franke  wrote:
> 
> Hi Bill - 
> I experiencing some unusual behavior in r6758. When I open the app after 
> having last used MSK144, the wide graph opens instead of the fast graph. This 
> is after exiting the program normally with the wide graph closed and the fast 
> graph visible.
> 
> I’m also seeing different results from the MSK144 decoder (syncmsk144) when 
> it is run from wsjt-x and when it is run from the command-line program 
> msk144d.f90. This last is my problem - likely an array overrun, as the 
> decoder does a bunch of array manipulations, and I have probably made a 
> mistake somewhere.  I thought that I should mention it on the chance that it 
> may have something to do with the first observation.
> Steve

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] r6758 wide graph opens instead of fast graph

[Steven Franke]

Hi Bill - 
I experiencing some unusual behavior in r6758. When I open the app after having 
last used MSK144, the wide graph opens instead of the fast graph. This is after 
exiting the program normally with the wide graph closed and the fast graph 
visible.

I’m also seeing different results from the MSK144 decoder (syncmsk144) when it 
is run from wsjt-x and when it is run from the command-line program 
msk144d.f90. This last is my problem - likely an array overrun, as the decoder 
does a bunch of array manipulations, and I have probably made a mistake 
somewhere.  I thought that I should mention it on the chance that it may have 
something to do with the first observation.
Steve


> On Jun 10, 2016, at 6:01 PM, Bill Somerville  wrote:
> 
> On 10/06/2016 20:51, Bill Somerville wrote:
>> the defect that was stopping WAV files being saved reliably when 
>> WSJT-X "Save Decoded" was selected has been resolved. Also any errors 
>> that occur writing the WAV files are now reported in a message box. 
>> These changes are in r6750, r6751 & r6752.
> 
> Hi Mike & all,
> 
> I fooled myself that it was fixed, but r6757 should be OK now.
> 
> 73
> Bill
> G4WJS.
> 
> 
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are 
> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
> J-Flow, sFlow and other flows. Make informed decisions using capacity 
> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] save_wave_file

[Bill Somerville]

On 10/06/2016 20:51, Bill Somerville wrote:
> the defect that was stopping WAV files being saved reliably when 
> WSJT-X "Save Decoded" was selected has been resolved. Also any errors 
> that occur writing the WAV files are now reported in a message box. 
> These changes are in r6750, r6751 & r6752.

Hi Mike & all,

I fooled myself that it was fixed, but r6757 should be OK now.

73
Bill
G4WJS.


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Tx & Rx audio frequency

[Bill Somerville]

On 10/06/2016 21:50, Alessandro Gorobey wrote:
> I perfectly understood that some questions are premature and OOT.
> But I cannot understood 500+-1 Hz frequency difference from transmit and
> receive.
>
> Imagine a PC with real 3 audio boards and Ubuntu Xenial. Two of them are
> connected together IN to OUT and vice versa. Two separate instance of
> program are running.
>
> Selecting MKS144 as mode I obtain several lines with a 1000 that I
> presume the audio TX frequency
>
> 200815  Tx  1000 &  CQ IW3RAB JN65
>
> on receive side
>
> 202705  -1  1.3 1498 & CQ IW3RAB JN65 !Italy
> 202715  -1  1.3 1499 & CQ IW3RAB JN65 !Italy
> 202725  -1  3.0 1499 & CQ IW3RAB JN65 !Italy
> 202735   1  2.1 1496 & CQ IW3RAB JN65 !Italy
>
> despite the couple of Hz but the other 500 ??

Hi Sandro,

in the WSJT-X MainWindow class there is a member variable m_bSimplex, 
when set to true it disables the Tx frequency and tone offsetting that 
is used to cover the necessary bandwidth for HF JT9+JT65 operation. It 
looks like it is not being set for the "fast" modes where it should be. 
Setting "Settings->General->Enable VHF/UHF/Microwave features" to 
checked should also turn off the unwanted behaviour.

73
Bill
G4WJS.


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Tx & Rx audio frequency

[Alessandro Gorobey]

Hi All,

I perfectly understood that some questions are premature and OOT.
But I cannot understood 500+-1 Hz frequency difference from transmit and 
receive.

Imagine a PC with real 3 audio boards and Ubuntu Xenial. Two of them are 
connected together IN to OUT and vice versa. Two separate instance of 
program are running.

Selecting MKS144 as mode I obtain several lines with a 1000 that I 
presume the audio TX frequency

200815  Tx  1000 &  CQ IW3RAB JN65

on receive side

202705  -1  1.3 1498 & CQ IW3RAB JN65 !Italy
202715  -1  1.3 1499 & CQ IW3RAB JN65 !Italy
202725  -1  3.0 1499 & CQ IW3RAB JN65 !Italy
202735   1  2.1 1496 & CQ IW3RAB JN65 !Italy

despite the couple of Hz but the other 500 ??

Thank in advance

-- 
73
Sandro
IW3RAB

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] save_wave_file

[Bill Somerville]

On 06/06/2016 17:27, Black Michael wrote:
Bill,  don't know if you saw the post on the wsjtx list but one person 
was reporting a missing wav file after a strong decode.


Looking at save_wave_file I see the wav.open doesn't do anything with 
the return code so would fail silently if there's a problem opening 
the file.


Shouldn't there be a pop-up or such with the correct error message in 
case of failure?  Is thread access to the GUI any problem?


HI Mike & all,

the defect that was stopping WAV files being saved reliably when WSJT-X 
"Save Decoded" was selected has been resolved. Also any errors that 
occur writing the WAV files are now reported in a message box. These 
changes are in r6750, r6751 & r6752.


73
Bill
G4WJS.

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X: Potential breakages

[Bill Somerville]

Hi All,

I have just committed a bunch of changes (r6755) that came out of a 
lengthy session preparing and running WSJT-X under the valgrind MemCheck 
tool. These changes eliminate several memory leaks, mostly trivial but 
removing them makes the output of MemCheck far more useful. They also 
include many changes to fix uses of uninitialized variables, mostly 
these are changes in the order of statements where there are subtle 
underlying dependencies. It is quite possible that these statement 
re-orderings have broken something that my testing did not reveal; so be 
on the lookout for for unexpected behaviour changes, especially at start up.

73
Bill
G4WJS.


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Start Monitor when switching modes?

[Black Michael]

Not sure of the applicability of the car metaphor...more like the car will only 
start when the radio is on.  Who would think to turn the radio on?But as a more 
cogent example...neither you nor Joe initially knew what caused this...what 
hope do the rest of us have?
You said this ability was "potentially useful" -- but only useful when 
switching to some modes?
RRRMike W9MDB

  From: Bill Somerville 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Friday, June 10, 2016 10:48 AM
 Subject: Re: [wsjt-devel] Start Monitor when switching modes?
   
 On 10/06/2016 16:42, Black Michael wrote:
  
 The remaining question is the inconsistency...whether or not one has a working 
freq for a mode doesn't seem like it should change the behavior...quite 
non-intuitive. Either all mode changes do it or none do it.  That seems logical 
to me. So it's either monitor=true in mode change or delete the one in freq 
change, isn't it?  Either would make it consistent. 
 Hi Mike, it's not the mode change that causes monitor to turn on, it's the 
frequency change that gets invoked automatically when the mode change finds a 
working frequency available. That's no more inconsistent than, for example, 
being able to drive your car after you turn the key (press the button), or not 
if there is no fuel/charge available. 73
 Bill
 G4WJS.
  
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


  --
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Start Monitor when switching modes?

[Bill Somerville]

On 10/06/2016 16:42, Black Michael wrote:
The remaining question is the inconsistency...whether or not one has a 
working freq for a mode doesn't seem like it should change the 
behavior...quite non-intuitive.

Either all mode changes do it or none do it.  That seems logical to me.
So it's either monitor=true in mode change or delete the one in freq 
change, isn't it?  Either would make it consistent.


Hi Mike,

it's not the mode change that causes monitor to turn on, it's the 
frequency change that gets invoked automatically when the mode change 
finds a working frequency available. That's no more inconsistent than, 
for example, being able to drive your car after you turn the key (press 
the button), or not if there is no fuel/charge available.


73
Bill
G4WJS.

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Start Monitor when switching modes?

[Black Michael]

I've not run into this problem as I just leave monitor on.  I'm just being an 
advocate here...(or just stubborn as my wife says) 
The remaining question is the inconsistency...whether or not one has a working 
freq for a mode doesn't seem like it should change the behavior...quite 
non-intuitive.Either all mode changes do it or none do it.  That seems logical 
to me.So it's either monitor=true in mode change or delete the one in freq 
change, isn't it?  Either would make it consistent.
Mike W9MDB

  From: Bill Somerville 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Friday, June 10, 2016 10:31 AM
 Subject: Re: [wsjt-devel] Start Monitor when switching modes?
   
On 10/06/2016 16:23, Black Michael wrote:
> Under what condition do you have monitor off and then want it to come 
> on outside of your control?  Don't the vast majority just keep monitor 
> on 24x7?

Hi Mike,

as I said above: some users, including myself, start WSJT-X 
automatically before they wish to use it. The option to not turn on 
monitor at startup is needed otherwise WSJT-X seizes control of the rig. 
Some time later when WSJT-X is required, one can select a band or mode 
in WSJT-X and everything is set ready to go. The converse is true in 
that disabling monitor relinquishes active control of the rig allowing 
operation in other modes and on other frequencies. One click to start 
using WSJT-X (well two to select from the band drop down), one click to 
stop using WSJT-X.

I have explained how a configuration with no working frequencies will 
achieve what you ask for, doesn't that satisfy both camps?

73
Bill
G4WJS.


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


  --
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Start Monitor when switching modes?

[Bill Somerville]

On 10/06/2016 16:23, Black Michael wrote:
> Under what condition do you have monitor off and then want it to come 
> on outside of your control?  Don't the vast majority just keep monitor 
> on 24x7?

Hi Mike,

as I said above: some users, including myself, start WSJT-X 
automatically before they wish to use it. The option to not turn on 
monitor at startup is needed otherwise WSJT-X seizes control of the rig. 
Some time later when WSJT-X is required, one can select a band or mode 
in WSJT-X and everything is set ready to go. The converse is true in 
that disabling monitor relinquishes active control of the rig allowing 
operation in other modes and on other frequencies. One click to start 
using WSJT-X (well two to select from the band drop down), one click to 
stop using WSJT-X.

I have explained how a configuration with no working frequencies will 
achieve what you ask for, doesn't that satisfy both camps?

73
Bill
G4WJS.


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Start Monitor when switching modes?

[Black Michael]

Am I confused?  This is how I would expect it to behave...
Monitor on -> change mode -> Monitor still onMonitor off -> change mode -> 
Monitor stays off

Under what condition do you have monitor off and then want it to come on 
outside of your control?  Don't the vast majority just keep monitor on 24x7?
Mike W9MDB

  From: Bill Somerville 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Friday, June 10, 2016 10:18 AM
 Subject: Re: [wsjt-devel] Start Monitor when switching modes?
   
On 10/06/2016 16:06, Joe Taylor wrote:
> I think I see it the way Mike does: just leave monitor alone, let it
> stay the way it was set when doing a band change.

Hi Joe & Mike,

the thinking was that changing frequency in WSJT-X must mean that you 
want to listen to that frequency. I can't think of a good reason not to 
turn on monitor for a frequency change. OTOH because WSJT-X changes 
frequency automatically to the first defined working frequency for a 
mode when changing mode; this has the downstream consequence of enabling 
monitor.

I'm not sure that a testing requirement to not have monitor come on 
while changing modes between playing back WAV files justifies disabling 
a potentially useful feature. As a possible alternative you could set up 
a configuration with no working frequencies defined. To do that:

1) clone the current configuration,
2) rename the clone to "testing" or whatever you wish,
3) switch to the new configuration,
4) in "Settings->Frequencies" click a working frequency, type CTRL+A, 
right-click and select "Delete".

That will mean that whenever that configuration is selected mode changes 
will have no impact on rig control nor monitor state.

73
Bill
G4WJS.


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


  --
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Start Monitor when switching modes?

[Bill Somerville]

On 10/06/2016 16:06, Joe Taylor wrote:
> I think I see it the way Mike does: just leave monitor alone, let it
> stay the way it was set when doing a band change.

Hi Joe & Mike,

the thinking was that changing frequency in WSJT-X must mean that you 
want to listen to that frequency. I can't think of a good reason not to 
turn on monitor for a frequency change. OTOH because WSJT-X changes 
frequency automatically to the first defined working frequency for a 
mode when changing mode; this has the downstream consequence of enabling 
monitor.

I'm not sure that a testing requirement to not have monitor come on 
while changing modes between playing back WAV files justifies disabling 
a potentially useful feature. As a possible alternative you could set up 
a configuration with no working frequencies defined. To do that:

1) clone the current configuration,
2) rename the clone to "testing" or whatever you wish,
3) switch to the new configuration,
4) in "Settings->Frequencies" click a working frequency, type CTRL+A, 
right-click and select "Delete".

That will mean that whenever that configuration is selected mode changes 
will have no impact on rig control nor monitor state.

73
Bill
G4WJS.


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Start Monitor when switching modes?

[Joe Taylor]

Hi Bill,

I think I see it the way Mike does: just leave monitor alone, let it 
stay the way it was set when doing a band change.

-- Joe

On 6/10/2016 11:01 AM, Bill Somerville wrote:
> On 10/06/2016 15:40, Joe Taylor wrote:
>> I frequently run with Monitor off at startup, most commonly when working
>> on decoder development or optimization.  In those circumstances I'm
>> generally using pre-recorded .wav files, and I don't want Monitor to
>> mess up the waterfall or call the decoders at the end of a UTC minute, etc.
>
> Hi Joe,
>
> I was looking at this from the wrong end of the telescope. Are you
> looking for WSJT-X not to turn on monitor when you change mode, even
> where there is a working frequency defined for the target mode?
>
> 73
> Bill
> G4WJS.
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Start Monitor when switching modes?

[Bill Somerville]

On 10/06/2016 15:40, Joe Taylor wrote:
> I frequently run with Monitor off at startup, most commonly when working
> on decoder development or optimization.  In those circumstances I'm
> generally using pre-recorded .wav files, and I don't want Monitor to
> mess up the waterfall or call the decoders at the end of a UTC minute, etc.

Hi Joe,

I was looking at this from the wrong end of the telescope. Are you 
looking for WSJT-X not to turn on monitor when you change mode, even 
where there is a working frequency defined for the target mode?

73
Bill
G4WJS.


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Start Monitor when switching modes?

[Joe Taylor]

Hi all,

On 6/10/2016 10:18 AM, Black Michael wrote:
> I can't think of a reason to not start monitor...but shouldn't it
> be consistent across mode changes then?  I would think any change
> from mode-to-mode should behave the same.  Maybe Joe has a reason
> to not want to start it since he brought it up.

I frequently run with Monitor off at startup, most commonly when working 
on decoder development or optimization.  In those circumstances I'm 
generally using pre-recorded .wav files, and I don't want Monitor to 
mess up the waterfall or call the decoders at the end of a UTC minute, etc.

-- Joe

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Request: WSJT-X UDP protocol extension to identify decodes to will accept UDP reply command.

[Black Michael]

Yeah...I agree it's a step towards TCP but the stateless nature is still handy 
for our use.  And UDP over local network is quite reliable (via loopback and 
typically good over LAN too).I wasn't thinking of ack/nak for all 
packets...just the request from the client that Laurie is talking about.
I did work on a project many years ago where they started with UDP and 
eventually reinvented TCP with hundreds of lines of code that was unstable 
which I replaced with something like a 10-line program for TCP that was rock 
solid.  It was a job for the White House Communication Agency. RRRMike W9MDB
  From: Bill Somerville 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Friday, June 10, 2016 9:25 AM
 Subject: Re: [wsjt-devel] Request: WSJT-X UDP protocol extension to identify 
decodes to will accept UDP reply command.
   
 On 10/06/2016 13:24, Black Michael wrote:
  
One possible solution is a simple ack/nak packet.
 Hi Mike, that doesn't really sit well with the fire and forget nature of UDP 
messages. Once you start adding conversational protocols you might as well use 
TCP/IP but that requires asynchronous processing or threads and a whole lot of 
state for each "client". The current UDP message infrastructure in WSJT-X is 
stateless at the connection level and synchronous, very simple and no waiting 
for network replies. 73
 Bill
 G4WJS.
  
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


  --
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Request: WSJT-X UDP protocol extension to identify decodes to will accept UDP reply command.

[Bill Somerville]

On 10/06/2016 13:24, Black Michael wrote:

One possible solution is a simple ack/nak packet.


Hi Mike,

that doesn't really sit well with the fire and forget nature of UDP 
messages. Once you start adding conversational protocols you might as 
well use TCP/IP but that requires asynchronous processing or threads and 
a whole lot of state for each "client". The current UDP message 
infrastructure in WSJT-X is stateless at the connection level and 
synchronous, very simple and no waiting for network replies.


73
Bill
G4WJS.

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Start Monitor when switching modes?

[Black Michael]

I can't think of a reason to not start monitor...but shouldn't it be consistent 
across mode changes then?  I would think any change from mode-to-mode should 
behave the same.Maybe Joe has a reason to not want to start it since he brought 
it up. 
RRRMike W9MDB


   

   From: Bill Somerville 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Friday, June 10, 2016 9:10 AM
 Subject: Re: [wsjt-devel] Start Monitor when switching modes?
  
 On 09/06/2016 22:20, Black Michael wrote:
  
 Is there some reason monitor should get turned on with frequency change? 
  
 Hi Mike, the rational is that if the user has the "Monitor off at startup" 
option then WSJT-X should leave the rig alone until some action in WSJT-X is 
made, i.e. indicating that WSJT-X is being used. This allows WSJT-X to be 
started before it is needed which is a common arrangement, for example started 
when the PC is started. Changing frequency, or changing mode where there is a 
working frequency defined (working frequencies may be generic i.e. for all 
modes if desired) is taken to mean start operating and therefore enables 
monitor. Why would you not want monitor enabled when changing frequency from 
WSJT-X? 73
 Bill
 G4WJS.
  
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


  --
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Request: WSJT-X UDP protocol extension to identify decodes to will accept UDP reply command.

[Black Michael]

One possible solution is a simple ack/nak packet.
RRRMike W9MDB

  From: Bill Somerville 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Friday, June 10, 2016 6:17 AM
 Subject: Re: [wsjt-devel] Request: WSJT-X UDP protocol extension to identify 
decodes to will accept UDP reply command.
   
 On 10/06/2016 05:10, Laurie, VK3AMA wrote:
  
I propose that the UDP protocol, specifically the decode packet, be extended to 
include a Boolean flag that identifies if the decode will respond to a UDP 
Reply command.
 
 Not all CQ/QRZ decodes are supported by the UDP Reply command and it would be 
beneficial if those decodes are easily identified (within the decode packet) as 
not being acceptable by WSJT-X, rather than performing exception tests or 
analysis of the decode string structure as is currently needed to identify 
these unsuitable decodes.
 Hi Laurie, that is not very easy, for example if the decodes are erased then 
they are no longer capable of being replied. Bottom line is that the decision 
to react to a decode on double click (or UDP reply message) is made at the time 
it is done, not when the decode is received.
  Yesterday I committed a change that will make the highlighting and the 
response to UDP reply messages more consistent. Other than that you should just 
send the reply packets and if WSJT-X does not respond then it should be safe to 
assume that double clicking the same decode in WSJT-X would not do anything 
either, with the exception that only general call *standard messages* will be 
responded to via the UDP reply message. No one to my knowledge has complained 
that double clicking some decodes in WSJT-X does not cause WSJT-X to react. If 
JTAlert users are finding that a general call message is not being responded to 
then they must put forward a case for making them standard messages. That is a 
very difficult case to make because we cannot change the protocol without major 
disruption. There are edge cases like the possible use of the E9 prefixes for 
more flexible CQ calls, this is where change should be requested rather than 
expecting WSJT-X guess the intent of various free text messages.
  73
 Bill
 G4WJS.
  
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


  --
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Request: WSJT-X UDP protocol extension to identify decodes to will accept UDP reply command.

[Bill Somerville]

On 10/06/2016 05:10, Laurie, VK3AMA wrote:
I propose that the UDP protocol, specifically the decode packet, be 
extended to include a Boolean flag that identifies if the decode will 
respond to a UDP Reply command.


Not all CQ/QRZ decodes are supported by the UDP Replycommand and it 
would be beneficial if those decodes are easily identified (within the 
decode packet) as not being acceptable by WSJT-X, rather than 
performing exception tests or analysis of the decode string 
structureas is currently neededto identify these unsuitable decodes.


Hi Laurie,

that is not very easy, for example if the decodes are erased then they 
are no longer capable of being replied. Bottom line is that the decision 
to react to a decode on double click (or UDP reply message) is made at 
the time it is done, not when the decode is received.


Yesterday I committed a change that will make the highlighting and the 
response to UDP reply messages more consistent. Other than that you 
should just send the reply packets and if WSJT-X does not respond then 
it should be safe to assume that double clicking the same decode in 
WSJT-X would not do anything either, with the exception that only 
general call *standard messages* will be responded to via the UDP reply 
message. No one to my knowledge has complained that double clicking some 
decodes in WSJT-X does not cause WSJT-X to react.


If JTAlert users are finding that a general call message is not being 
responded to then they must put forward a case for making them standard 
messages. That is a very difficult case to make because we cannot change 
the protocol without major disruption. There are edge cases like the 
possible use of the E9 prefixes for more flexible CQ calls, this is 
where change should be requested rather than expecting WSJT-X guess the 
intent of various free text messages.


73
Bill
G4WJS.

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel