> I have no knowledge of Portaudio. Is this something that you set up to
> work with fldigi?
Portaudio is a cross=platform API. FLdigi can use and get some improved
performance. Just install it, and select it from the config box in
FLdigi when you get it running.
> I don't have much knowledge about ALSA vs OSS, other than from what I
> have read, it is intended that ALSA is the replacement for OSS which
> apparently had a lot of problems?
OSS is still a solid sound system, no problems really. But it isn't
free. There is a free version (limited) of it, bu the full OSS sound
system is a commercial product, which I actually have owned many
versions of over the years. It's owned by 4front Technologies. ALSA is
free. And the drivers show it (sometimes.) A commercial 4front OSS
driver is solid.
> As far as mapping mixer controls, I don't think that I have had to do
> that with Windows, so I would rather this be done with the OS and not
> some additional fix for the user.
Your choice is to remap the controls yourself if they need mapping. This
would pertain to the alsa-oss emulation layer only, and not the alsa
layer directly. Portaudio will also use these mixer controls too, so
fixing them in alsa-oss emulation fixes then for Portaudio too. This
isn't a defect in Linux, it's a defect in the driver for the particular
sound card. Contact the maintainer to get it fixed if you have an issue.
(In the case of Intel sound, good luck> Considering that ALSA has been
> developed for nearly 10 years now, I hope this can help toward making
> Linux at least a bit more competitive with sound issues compared to
> Windows. I won't say I have never had any problems with Windows sound,
> but it does seem to work far better and is more understandable. At least
> it is to me.
> k.) I do this for cards I use, so once the new release makes it to
the street, no more issues. You have to remember that the drivers in
alsa (and the emulation layer) are maintained by volunteers, and they
may not have the actual card to play with. So sometimes you have to lend
a hand. Some of these modern sound cards are too complex for one mixer
mapping to work for every application. So if you have special ham needs,
you'll sometimes have to either remap them, or get a card that is less
either less complex or better mapped, or use a commercial sound system,
like you do with M$ products.
Aliasing the second sound card (for alsa-oss emulation) has always been
done manually in Linux. So you'll be needing to double check this and
apply any aliases if needed. (unless you are using card0 as the ham
> The binary does not run. I have tried using the ./fldigi and nothing
> happens. That is the odd thing, really. Nothing is happening, not even
> any errors displayed.
Nothing on the terminal at all? No text, nothing? Is your bash shell
configured right? Is FLdigi even being called by the ./fldigi command?
Do you see the file with an ls command to catalog the directory? You
opened the terminal window in the fldigi directory right?
Rick Kunath, k9ao