Dave, et. al., I'll do some more testing on this. After I observed this situation with PSK125, I tried the same thing with PSK31 and did not observe the problem. However, it might be difficult to test this since there are few PSK125 signals on the air.
Another observation: There were lightning crashes at the time this was happening, and even without the PSK browser open, I would occasionally lose characters due to the crashes, but then it would continue decoding. When I would open the browser window, I would usually get a few characters, then there would be a crash, then total scramble. It appeared that the cursor in the waterfall would drift off a little bit when the crash would occur, but even when I would click on it to get it back on trace (hence hoping to decode a few seconds of lost decoding), nothing would decode - total gibberish. I wonder if having the PSK browser window open was reducing the ability of the decoder engine to properly decode signals with low S/N, but may not be noticeable with signals with a high S/N. Another possibility: Even though I tried this opening/closing of the browser window about 5 times, and every time it blew the decoding, perhaps it was just poor conditions and my observation was coincidentally artifactual. Conditions were certainly marginal. If I observe this again, I'll try the suggestion by Mike, KL7MJ, to create a new preferences file. 73, -Joe- On Mon, Mar 22, 2010 at 6:46 AM, w1hkj <[email protected]> wrote: > Joseph A. Counsil wrote: > >> Greetings, >> >> I had the PSK browser open, and it work great when in BPSK31 mode. >> However, a station called in BPSK125 and I left the browser open but >> changed from 31 to 125 to copy and have a QSO with him. He had a 599 signal >> to my station, but I was only getting partial decodes. After several >> minutes of trying to figure out what was wrong, I closed the PSK browser >> window and suddenly got perfect decode, as I would expect with such a strong >> signal. While decoding him I re-opened the PSK browser window, and the >> decode immediately scrambled, but unscrambled when I again closed the >> browser window. >> >> Not too big a deal since the PSK browser window in mostly for BPSK31 >> anyway, but should probably be fixed. >> >> I'm running FLdigi 3.20.0b7 on Windows XP Pro SP3. >> >> 73, >> -Joe- >> > I just tested this on both Vista and Linux. The PSK browser open does not > effect the reception of any PSK mode in the Rx Panel. In fact the PSK > browser also receives in the selected PSK mode, ie PSK125 can be decoded in > both the Rx panel and the Browser. This is not true for the FEC psk modes, > PSK63F, PSK125R, PSK250R and PSK500R. The browser can be left open and the > Rx panel decoding performs correctly. The browser is just not designed to > decode those modes. > > 73, Dave, W1HKJ > > > _______________________________________________ > fldigi-alpha mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/fldigi-alpha > -- +----------------------------------------------------------------+ | Joseph A. Counsil [email protected] Phone:(573) 341-5186 | | 1310 Woodlawn Drive, Rolla, MO 65401 Ham Radio: KØOG | +----------------------------------------------------------------+
_______________________________________________ fldigi-alpha mailing list [email protected] https://lists.berlios.de/mailman/listinfo/fldigi-alpha
