Re: [wsjt-devel] /150 Compound Calls

2019-08-28 Thread WB5JJJ 
Don:

We have tested CQ HPM callsign gridsq and it seems to work as a "directed
call".  Maybe this will be adopted once folks figure out /150 won't work in
FT8/FT4.

On Wed, Aug 28, 2019 at 1:09 PM Don AA5AU  wrote:

> In anticipation of seeing callsigns with /150 added for the ARRL sponsored
> Hiram Percy Maxim Birthday Celebration, how will this affect FT4 & FT8
> operations and especially the upcoming WW Digi Contest?
>
> I see this in the WSJT-X online help file "Compound callsigns like
> xx/K1ABC or K1ABC/x and special event callsigns like YW18FIFA are supported
> for normal QSOs but not for contest-style messages."
>
> I don't see where we recommended not using non-standard in WW-DIGI.
>
> Thanks,
> Don AA5AU
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
George - WB5JJJ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] /150 Compound Calls

2019-08-28 Thread Don AA5AU 
In anticipation of seeing callsigns with /150 added for the ARRL sponsored 
Hiram Percy Maxim Birthday Celebration, how will this affect FT4 & FT8 
operations and especially the upcoming WW Digi Contest?
I see this in the WSJT-X online help file "Compound callsigns like xx/K1ABC or 
K1ABC/x and special event callsigns like YW18FIFA are supported for normal QSOs 
but not for contest-style messages."
I don't see where we recommended not using non-standard in WW-DIGI.
Thanks,Don AA5AU___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] v2.1.0 randomly stops decoding ft8

2019-08-28 Thread akirby03049 
Tom & Bill:

Thank you for your response.  I certainly do *not* expect my reported problem 
to be given priority treatment.  WSJT-X is a great piece of software and I 
appreciate that it requires a lot of work, done by volunteers, to improve and 
maintain it. 

The issue I was trying to raise is one of process.  The documentation says to 
report bugs to the reflector.  What happens to emailed bug reports? Can I 
search open issues to see if others have seen a similar issue and what 
additional information the developers would like?  Can I update the bug when I 
have more information to add?  How can I even know if the developer who knows 
that part of the system read the description of my issue?  Are all open issues 
triaged periodically?  Unless someone responds, it’s an information black hole 
which can be frustrating for people who report bugs.

Having done engineering for more than 40 years, I know how difficult it can be 
to debug intermittent problems.  That’s why I offered to collect data to help 
isolate the problem.  In your responses, you have given me some things to look 
for when the problem recurs.  Thank you.

More people might be willing to get involved in fixing bugs if we could see the 
open issues.

Thanks,

Alan / NX1W

> On Aug 28, 2019, at 11:49 AM, Tom Melvin  wrote:
> 
> Alan
> 
> Just an observation - for many many people the software works well, the fact 
> you cannot reproduce the issue does suggest IF it is an actual wsjtx bug it 
> is pretty obscure.  
> 
> From doing software development in a different life these are the worst sort 
> of issues - it could be rig setup, it could be other applications on the PC, 
> could be latest windows (or whatever) update, supplier codex, etc. etc. - how 
> much time is justified in tracking it down - you said it is a small team.
> 
> One option is to log the details, and then see how any others have issues 
> over time, if more and more appear - is it same Rig? is it same version of 
> the OS, is it the 32 or 64 bit version of the software (there are known 
> issues with the 64 bit that are tied to some dev libs) - you never actually 
> mentioned which version you were using - if 64 have you tried the 32 bit?
> 
> While it may appear dev team are doing nothing it could be they are waiting 
> to see if some common factor pops up - 1 week, 1 month, 1 year …  Your email 
> seems to suggest you sort of expect the team to give it a higher priority 
> (may be wrong but that was way I read the mail)
> 
> As to a bug list - yes there are a couple of issues I would like to see fixed 
> - I know if a list was published there would be a flurry of activity (myself 
> included)  ‘debating’ the severity/fix time scale - almost everyone would 
> want their perceived bug higher up the list. All the dev team would end up 
> doing is justifying the details.  I can see why no list is publicly available.
> 
> I’m sure when it can be reproduced it will be fixed.
> 
> Collect info, what is happening around the time of the freeze, are .wav files 
> saved, anything running on PC at the time, time of day - how random is 
> random, daily, weekly - collecting info in a little text file may provide 
> pointers you can report to the team that may help.
> 
> Regards
> 
> Tom
> 
> --
> 73’s
> 
> Tom
> GM8MJV (IO85)
> 
> 
> 
> 
> 
> On 28 Aug 2019, at 15:48, akirby03...@hotmail.com 
>  wrote:
> 
>> I assume that the development team uses some bug tracking package.  Is this 
>> correct?
>> 
>> If so, was there a defect logged for the issue that I reported here?  If so, 
>> what is the assigned severity and expected fix release?  If not, why not?
>> 
>> I, and many others, really appreciate the volunteer work done by the 
>> development team on WSJT-X, but it would be really nice for users who report 
>> a problem to know the status of their issue…
>> 
>> Thanks,
>> 
>> Alan / NX1W
>> 
>>> On Aug 26, 2019, at 4:02 PM, akirby03...@hotmail.com 
>>>  wrote:
>>> 
>>> Radio is an IC-7000. 
>>> Audio is via USB audio dongle to radio ACC socket.  
>>> 
>>> 73
>>> 
 On Aug 26, 2019, at 3:04 PM, Bill Somerville >>> > wrote:
 
 On 26/08/2019 19:19, Alan Kirby wrote:
> I have a PC continuously running WSJT-X FT8.  Once or twice each week, it 
> stops decoding all messages.  The clock is accurate to within 100ms and 
> the waterfall shows many signals.
>  
> Restarting the program immediately fixes the problem.. I have observed 
> this issue with earlier versions of WSJT-X but had hoped the new version 
> would have fixed it.
>  
> I cannot reproduce this at will – it appears to happen randomly.  I would 
> be happy to help the dev team collect data to diagnose this.
>  
> Windows 10 (64 bit), Intel i5-6400, 2.7GHz 8GB DRAM
> WSJT-X v2.1.0
>  
> Thanks,
>  
> Alan (NX1W)
 Hi Alan,
 
 which rig and how

Re: [wsjt-devel] v2.1.0 randomly stops decoding ft8

2019-08-28 Thread Tom Melvin 
Alan

Just an observation - for many many people the software works well, the fact 
you cannot reproduce the issue does suggest IF it is an actual wsjtx bug it is 
pretty obscure.  

From doing software development in a different life these are the worst sort of 
issues - it could be rig setup, it could be other applications on the PC, could 
be latest windows (or whatever) update, supplier codex, etc. etc. - how much 
time is justified in tracking it down - you said it is a small team.

One option is to log the details, and then see how any others have issues over 
time, if more and more appear - is it same Rig? is it same version of the OS, 
is it the 32 or 64 bit version of the software (there are known issues with the 
64 bit that are tied to some dev libs) - you never actually mentioned which 
version you were using - if 64 have you tried the 32 bit?

While it may appear dev team are doing nothing it could be they are waiting to 
see if some common factor pops up - 1 week, 1 month, 1 year …  Your email seems 
to suggest you sort of expect the team to give it a higher priority (may be 
wrong but that was way I read the mail)

As to a bug list - yes there are a couple of issues I would like to see fixed - 
I know if a list was published there would be a flurry of activity (myself 
included)  ‘debating’ the severity/fix time scale - almost everyone would want 
their perceived bug higher up the list. All the dev team would end up doing is 
justifying the details.  I can see why no list is publicly available.

I’m sure when it can be reproduced it will be fixed.

Collect info, what is happening around the time of the freeze, are .wav files 
saved, anything running on PC at the time, time of day - how random is random, 
daily, weekly - collecting info in a little text file may provide pointers you 
can report to the team that may help.

Regards

Tom

--
73’s

Tom
GM8MJV (IO85)





On 28 Aug 2019, at 15:48, akirby03...@hotmail.com wrote:

> I assume that the development team uses some bug tracking package.  Is this 
> correct?
> 
> If so, was there a defect logged for the issue that I reported here?  If so, 
> what is the assigned severity and expected fix release?  If not, why not?
> 
> I, and many others, really appreciate the volunteer work done by the 
> development team on WSJT-X, but it would be really nice for users who report 
> a problem to know the status of their issue…
> 
> Thanks,
> 
> Alan / NX1W
> 
>> On Aug 26, 2019, at 4:02 PM, akirby03...@hotmail.com wrote:
>> 
>> Radio is an IC-7000. 
>> Audio is via USB audio dongle to radio ACC socket.  
>> 
>> 73
>> 
>>> On Aug 26, 2019, at 3:04 PM, Bill Somerville  wrote:
>>> 
>>> On 26/08/2019 19:19, Alan Kirby wrote:
 I have a PC continuously running WSJT-X FT8.  Once or twice each week, it 
 stops decoding all messages.  The clock is accurate to within 100ms and 
 the waterfall shows many signals.
  
 Restarting the program immediately fixes the problem.. I have observed 
 this issue with earlier versions of WSJT-X but had hoped the new version 
 would have fixed it.
  
 I cannot reproduce this at will – it appears to happen randomly.  I would 
 be happy to help the dev team collect data to diagnose this.
  
 Windows 10 (64 bit), Intel i5-6400, 2.7GHz 8GB DRAM
 WSJT-X v2.1.0
  
 Thanks,
  
 Alan (NX1W)
>>> Hi Alan,
>>> 
>>> which rig and how is it connected to your PC for audio?
>>> 
>>> 73
>>> Bill
>>> G4WJS.
>>> ___
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-develdata=02%7C01%7C%7Cc9b2173181844d73251c08d72a588c50%7C84df9e7fe9f640afb435%7C1%7C0%7C637024432130899006sdata=0jj5QtA%2Bna8d33AtgV4fg3ZED6Vc2XKH7Qu9xyHVysU%3Dreserved=0
>> 
> 
> ___
> 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] v2.1.0 randomly stops decoding ft8

2019-08-28 Thread Bill Somerville 

On 28/08/2019 15:48, akirby03...@hotmail.com wrote:
I assume that the development team uses some bug tracking package.  Is 
this correct?


If so, was there a defect logged for the issue that I reported here? 
 If so, what is the assigned severity and expected fix release?  If 
not, why not?


I, and many others, really appreciate the volunteer work done by the 
development team on WSJT-X, but it would be really nice for users who 
report a problem to know the status of their issue…


Thanks,

Alan / NX1W


Alan,

WSJT-X is an Open Source project, if you have any suggested changes we 
accept patches for consideration.


The most likely cause of failures to decode are:

1) The jt9 sub-process has crashed, this is normally picked up by the 
main executable and an error message is popped up.


2) Clock synchronization to UTC is insufficiently accurate, a general 
drift of reported DT values just before decoding stops may indicate this 
type of issue.


3) Incoming audio samples are disrupted or delayed. Delayed input 
samples may be due to some upstream overload, perhaps by not having all 
digital stages at the same or better sample rate and format that WSJT-X 
expects, i.e. 48,000 Hz 16-bit. Disruption to audio samples can be due 
to system overload causing dropouts or other discontinuities which are 
normally fatal for decoding. Checking your system is suitable and 
suitably tuned for real-time audio can be helpful by using one of the 
popular DPC analysis tools.


The very first check you should make is that WSJT-X still records .WAV 
files when it appears to stop decoding. A saved .WAV file often reveals 
the source of the problem if you can provide one. OTOH .WAV files not 
being saved is a good indication that audio dropouts are regularly 
occurring. In the latter case a recording of the same audio device input 
stream that WSJT-X is using while it is failing to decode may reveal 
upstream issues (the free Audacity audio tool is a good way to do this).


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] v2.1.0 randomly stops decoding ft8

2019-08-28 Thread akirby03049 
I assume that the development team uses some bug tracking package.  Is this 
correct?

If so, was there a defect logged for the issue that I reported here?  If so, 
what is the assigned severity and expected fix release?  If not, why not?

I, and many others, really appreciate the volunteer work done by the 
development team on WSJT-X, but it would be really nice for users who report a 
problem to know the status of their issue…

Thanks,

Alan / NX1W

> On Aug 26, 2019, at 4:02 PM, akirby03...@hotmail.com wrote:
> 
> Radio is an IC-7000. 
> Audio is via USB audio dongle to radio ACC socket.  
> 
> 73
> 
>> On Aug 26, 2019, at 3:04 PM, Bill Somerville > > wrote:
>> 
>> On 26/08/2019 19:19, Alan Kirby wrote:
>>> I have a PC continuously running WSJT-X FT8.  Once or twice each week, it 
>>> stops decoding all messages.  The clock is accurate to within 100ms and the 
>>> waterfall shows many signals.
>>>  
>>> Restarting the program immediately fixes the problem.. I have observed this 
>>> issue with earlier versions of WSJT-X but had hoped the new version would 
>>> have fixed it.
>>>  
>>> I cannot reproduce this at will – it appears to happen randomly.  I would 
>>> be happy to help the dev team collect data to diagnose this.
>>>  
>>> Windows 10 (64 bit), Intel i5-6400, 2.7GHz 8GB DRAM
>>> WSJT-X v2.1.0
>>>  
>>> Thanks,
>>>  
>>> Alan (NX1W)
>> Hi Alan,
>> 
>> which rig and how is it connected to your PC for audio?
>> 
>> 73
>> Bill
>> G4WJS.
>> 
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net 
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-develdata=02%7C01%7C%7Cc9b2173181844d73251c08d72a588c50%7C84df9e7fe9f640afb435%7C1%7C0%7C637024432130899006sdata=0jj5QtA%2Bna8d33AtgV4fg3ZED6Vc2XKH7Qu9xyHVysU%3Dreserved=0
> 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel