Steve, First of all....a large group of people had migrated to 280. We ran a bunch yesterday, and this showed up out of the blue this morning...and it "infected" everyone who heard those tones.
So, I was in a hurry to let someone know that this was happening on 280 where a lot of people were using V2. It literally took over the entire country. Everywhere those tones were heard, the software on the listening computer, immediately (on next transmission) caused that computer to transmit the offending or corrupted tones. It did it to me in the middle of a CQ sequence (in other words, I was calling CQ , listened one seq, heard the corrupt tones, and my next TX seq of CQ was composed of the offending tones, ....and thus infecting everyone on freq that heard me...) This was not a "bug report" as much as a warning that this was going to produce a mass infection of tone corruption and to try to get it stopped. People were trying to figure out what happened to their computers... I wouldn't have said a thing if this only affected a few people beta testing...well it was far more than that because so many people switched to V2, and it was causing havoc. In any case, it appears that it may be connected to the auto-contest mode correction code. I was not in contest mode, btw. Normal MSK144 setup, 6 meters. I installed V2 in wsjtx\v2 and it remembered all my prior settings. It was behaving perfectly for me around 6 p.m. last night. First thing this morning, all hell broke loose as soon as KB7IJ transmitted those corrupt tones. Then I started transmitting them, then others and others. If it didn't seem urgent to me, I would have tried to provide more info... Since I did not see myself originate the tones (KB7IJ was the source ...at least for my infection), my conditions were just my everyday operation on 6m msk144. I was listening...that's it. That's all I can provide ... But, no worries, I will no longer post anything, or comment on the performance of the software at all. I'm sure it will get sorted out, and I'm off 280 anyway. 73, N0AN Hasan On Wed, Sep 19, 2018 at 7:13 AM Steven Franke via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hasan, > > Unfortunately, your report isn’t very useful as it stands. To you and > others who are testing the recent beta release of v2.0: when making a bug > report, please carefully document and report a sequence of steps needed to > reproduce the problem. When running a beta release, always run with “Save > all” turned on and, as in this case, if the problem involves behavior that > is triggered by receiving a certain type of signal or message, please > submit a saved wav file that triggers the problem with your bug report. > > If you are not willing or able to do the careful documentation that is > necessary to help us find and debug problems then, like Hasan, I recommend > that you follow his lead: > > > > Going back to 1.9 on 260, V2 abandoned until fixed. > > > > > 73 Steve k9an > > > On Sep 19, 2018, at 10:52 AM, Hasan al-Basri <hbasri.schie...@gmail.com> > wrote: > > > > When running MSK144, the program will start tx'ing some weird sounding > tones...they will "infect" any V2 MSK144 station that hears them and they > will start sending the same strange tones. > > > > 5 of us have experienced this same bug...all simultaneously upon hearing > those "odd" tones. > > > > I'm betting it is connected to the CM auto-correct code. > > > > If you TX for a bit with v2 msk144, you WILL infect other listemers/ > > > > Going back to 1.9 on 260, V2 abandoned until fixed. > > > > 73, N0AN > > Hasan > > _______________________________________________ > > 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 >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
