开云体育

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 ==

Sorry, But I have disabled the link to the source code pending the resolution of a reported bug. Please check for an update to the source code on Monday, 10 Sept. Thank you. I apologize for the

Tried to download Fldigi from link on W1HKJ.COM, but I get Not Found The requested URL /LinuxApps/fldigi.933b.src.tar.gz was not found on this server. Additionally, a 404 Not Found error was

When I addes the button to gmfsk I put it in the settings. I also was working on a mode-dependent version...probably CW and Other only, as the CW center is usually lower. It would be great if fldigi

It is configured in the source. Specifically, in src/rigcontrol/hamlib.cxx on line 177. -Joe, KD8ATU Rick Kunath wrote:

w1hkj wrote: Works beautifully here for me Dave, thanks so much. One other question on the QSY feature... where does "sweet spot" number come from? Is this coming from Hamlib, or is it settable

The PTT problem with receive-only rigs should be fixed in this version. If you can test that type of device please do so and report your results. I retested the hamlib interface to my Argonaut V and

The problem with cpu% going to 100% when holding the mouse over the waterfall button controls is resolved in this version. I will be looking at the PTT problem tomorrow. My brain works better in the

Good Info for me too Rick. Also I have located the issue with the 100% cpu usage when you change waterfall speeds. It was worse than that. The cpu% would go to 100% whenever you held the mouse over