On 10/27/2015 08:05 PM, Joe Taylor wrote: Hi Joe,
> The SVN revision number is not enough, since a single revision number > can apply to WSJT, WSJT-X v1.6.0, WSJT-X v1.6.1, etc. Are you running > v1.6.0, or v1.6.1? "./wsjtx --version" says "1.6.1-devel". > In this case, a minimum number of steps to reproduce the problem > requires a *.wav file that, when opened from within WSJT-X, will produce > at least one of the double decodes you are talking about. I have started "./wsjtx --test-mode" and I have tried to decode the cycles at 1618 and 1620, as you can see in my ALL.TXT. Now, there is no double decoded lines in the window. > Since you are building yourself from the SVN, you could also do some > simple tests to determine exactly what revision caused the undesired > behavior. For example, tests with your .wav file might show the problem > exists in r5993 but not in r5992 (or whatever). I have not used r5993 and r5992, but 5995, 5998, 6001 and 6004. I have not found such double decodes while using these revisions. > Such tests can isolate the cause of a bug very quickly -- and you can do > it yourself, even if you are not closely familiar with the code > internals. Such input can be a big help to the project. I hope that this little contribution will help a little bit. > Thanks for your continued interest! Many thanks to you and to all other contributors which make such excellent projects possible. Best 88 de Claude ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
