开云体育

w1hkj wrote: I hadn't thought about automating the acquisition to handle the tuning errors. I think you are right. This might be a superior solution. I've tried DominoEX, and agree about it's

I considered and tried implementing something similar to what you have suggested Rick. It seems like such a trivial thing to implement, but drove the waterfall processing over the top. Perhaps it has

Leigh, WA5ZNU, reported having problems with cpu% usage, so I took another hard look at the waterfall code. Incremental changes, but I have managed to cut the cpu usage down. You will not see much

I was tuning some weak MFSK16 signals last night on 40 and have a request about tuning markers. I really like the way there are no vertical markers in the waterfall on fldigi now as compared to gMFSK,

Leigh L. Klotz, Jr. wrote: For what it's worth, I am not seeing the 100% CPU usage here on either the old and slow 600 MHz Mandrake 10.1 machine )50-65% depending on waterfall speed and color or B/W)

I'm seeing 100% on the previous release too...I haven't isolated it yet. Leigh L. Klotz, Jr. wrote:

I get 100% CPU utilization on this version. When I naively run it under GDB, type ^C, and where, it's always in innards(). I don't remember how to select the other threads. The previous version showed

w1hkj wrote: I cannot compile the FLTK, line 1022 is looking for stdlib.h and it is in /usr/include. Root has read/write, groups and user have read permissions. I have no idea how to set the path if

By the way Dave, is there any reason why the print would be better? Is it the same modem code or different? Hamish -- Hamish Moffatt VK3SB <hamish@...> <hamish@...>

I think missing -dev packages is the most likely problem. At least libfltk1.1-dev is required, and it will depend on some X headers which it also requires. Hamish -- Hamish Moffatt VK3SB <hamish@...>

Ed, From your email it looks like you are having difficulty getting past the ./configure on Fltk. Is that correct? I'm not familiar with the Ubuntu distro, but I believe it is based on Debian. Your

David Freese wrote: Dave, I get the following error and have no idea how to correct it. configure: error: Configure could not find required X11 libraries ./configure: line 10022: exit: aborting.:

W2AGN wrote: Just compiled and tried fldigi .936 beta. Very nice program. I tried it alongside Gmfsk and at least for PSK31, got better print with fldigi. It might be my sound card setup, but fldigi

Just compiled and tried fldigi .936 beta. Very nice program. I tried it alongside Gmfsk and at least for PSK31, got better print with fldigi. It might be my sound card setup, but fldigi is definitely

A few changes that puts all of the necessary source code into the primary fl_logbook/src directory. Source tree now includes a Makefile so you do not need to have MinGWStudio installed in order to

Fixed a LSB - QSY (center signal in passband button) bug that was reported by Leigh, WA5ZNU. Thanks Leigh. Simplified the Dominoex Transmit code - eliminated the use of the FFT to generate the signal

Nothing huge ... just a few changes requested by testers. * Added RstIn to the pop-up list in the received text viewer, * Added CW_SWEET_SPOT to the #defines in the file "src/config.h" 73s, Dave,

I just concluded the bench test of all the modes in both FWD and REV mode. All work fine when tested against MultiPsk. 73s, Dave, W1HKJ

Thank you Leigh, Your analysis of the problem in both programs was correct, but there were a few missing pieces in fldigi to insure that the waterfall scale and frequency values tracked correctly.

Below the code I sent to Tomi to fix my QSY button sign error in gMFSK 0.7.1pre. if (hamlib_qsy) { gfloat f = conf_get_float("hamlib/cfreq"); hamlib_qsy = FALSE; G_LOCK(hamlib_mutex); if (mode ==