When you say improved performance, what does that mean? I mostly just
want it to work without any intervention as this stuff works flawlessly
in Windows and has for years. The card that I put in was from my
junquebox so it surely is not something new. I liked having it so I
could set my Windows programs to run the front jack with the embedded
sound card (has rear jacks too but not using them) for casual listening
with headset. The "new" SoundBlaster card Live! was put in place so that
I could set up everything for ham digital use only and it is extremely
accurate (within a Hz or two) compared with the embedded card. Made a
big difference on how well some of the digital modes worked.
The aliasing stuff is way over my head, but I have been able to run the
asoundconf-gtk program to give me a GUI to set the default card. It
still doesn't really seem to do this. At least not the way I think it
should work. But I can get the SB Live! card to work partially.
The main thing for me is to at least get things to work adequately.
Now on the binary, nothing is running from what I can tell. I would have
no way to know if my Bash shell is configured correctly, but it does
have bash as I recall when I use the CLI. It is not being called by the
./fldigi command although I am not really sure what they command does,
as I only recently found out about it. I do see the files OK with the ls
command and I am definitely in the correct directory when issuing the
command. From one other comment, someone else may have a similar problem.
What I am wondering is how many people are actually using the binary
form and having good luck with downloading it, and unrolling it?
Rick Kunath wrote:
> 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.
> 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.
> 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
> sound card.)
> 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