![]() I think it is automatic with xlog although you may have to have xlog running in the background. I did try putting a sample entry into the fldigi log and it appeared in the xlog log. Each of the appropriate libraries must be present on the computer to use that particular sound i/o. On Linux Fldigi can interface to the sound card using either the OSS, the Portaudio, or the PulseAudio. Select the SndCrd tab on the configuration dialog. I haven't got on digital yet, still trying to work out the bugs in the system. On Windows: Use the PortAudio and select the device from the list (s). I have both xlog and fldigi on my Lubuntu box in the shack. Under Linux, I've used cqrlog and xlog with reasonable results. I generally log fldigi contacts in the built-in logger, but then transfer them to another logging program via adi files. So it's not surprising if you are running into a capacity limit. Have you tried contacting the author? His page also suggests some Yahoo support groups.įldigi is not really intended to be a serious logging program, as I understand it. Super Moderator Joined: Apr 4th 1998, 00:00 Anyone have any ideas about this? Thanks, Mike K0AZ When I purchased my new 64 bit Ubuntu computer I figured installing Fldigi would be straight forward. Things have progressed pretty well using these procedures on different computers. This Outline represents what Ive learned compiling Fldigi on 32 bit machines. ![]() ![]() It actually took over 3k but stopped at 1998 and all between 1998 and current date do not load. Some notes on compiling Fldigi on a 64 bit Ubuntu machine. I went to merge almost 14k QSOs from an adif file i moved to documents. Used Synaptic Package Manager to install FLdigi 3.21.80. Greetings, Just recently got a machine up and running with Ubuntu 14.04.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |