On Thu, 7 Mar 2002, Steffen Neumann wrote:
>
> I have the problem that analog PCM center_lfe Output
> (and therefore also surround51 is not working on SBLive5.1.
> While playback works on surround40, I can't send sound
> to the center channel and get a message from libasound:
>
> ALSA li
I have the problem that analog PCM center_lfe Output
(and therefore also surround51 is not working on SBLive5.1.
While playback works on surround40, I can't send sound
to the center channel and get a message from libasound:
ALSA lib setup.c:343:(snd_config_get_ctl_elem_value) bad value
Hello,
For my first linux installation (2.4.4), I decided to use alsa...
After reading carefully all the docs, compiling my own kernel from
scratch, everything seemed to work. But not the Line2 input. I need it
(: I use it in a kind of home studio, and would like to totally migrate
to linux fo
First I would like to say thanks to the ALSA team for their excellent work.
But, I do have an (hopefully) interesting question:
It seems that when I am running an audio application, such as Xine or XMMS,
I cannot start another application that uses the audio system (even if it
doesn't directly p
Hello,
Just subscribed. I had seen a problem (with today's date) similar to
mine so I'm not sure if it has been addressed as I just subscribed...
Anyhow, I managed to compile the driver 0.9-beta10 successfully
yesterday but could not get the libs compiled. So I installed the
beta10 debian bin
Title: Ȩº£ÀÌ È«º¸¸á
Greetings:
I was tempted to add "...a day late and a dorkbot short..."
Anyway, it's on-line now. Lots of new stuff, etc. etc. etc.
Check it out:
http://www.linuxsound.at/ (Europe)
http://linux-sound.org/ (USA)
http://www.ymo.org/linuxsound/ (Japan
yes, that sounds like a layout problem. i will try to get my hands on
a SBLive, and also use some virtual midi ports. as you might have noticed,
this release is still rather beta: lot's of printf to be removed ;-)
maarten
___
Alsa-user mailing list
[EM
Maarten de Boer hat gesagt: // Maarten de Boer wrote:
> "aconnectgui is a FLTK based frontend for aconnect. It is written
> directly on top of the aconnect source, leaving the original source
> intact, only adding a couple of ifdefs, and some calls to the gui
> part, so it provides exactly the sa
Kai Vehmanen <[EMAIL PROTECTED]> writes:
> [alsa-kernel/alsa-driver]
> - better driver architecture
> - more shared code between drivers for
> different soundcards
no need to reinvent the wheel in every driver
distro maintainers build monuments in honor of alsa team
As a programmer, alsa is just much easier to use.
alsa provides a consistent api interface for all sound cards thanks to the
alsa-lib. (shared user space code)
So, if I write an app for my sound card, I can be pretty sure the app will
work on all other sound cards.
With OSS/Free, hardly any of th
Why is ALSA the better alternative? That's a question I've been asked
quite a few times recently. Below is a reply I just wrote to
ecasound-list. I'd be very interested in hearing your comments on this
issue. Have I missed some important points?
One thing that seems be causing a lot of confusion
I had the same problem. Then I downloaded the latest 0.9.0beta12 and
had no problem! try beta12 version!
Jan
On Friday, 1. March 2002 10:42, you wrote:
> On Fri, 1 Mar 2002 00:41:39 +0100 (CET)
>
> .¿. <[EMAIL PROTECTED]> wrote:
> > hi!
> >
> > i have tried to get my terratec 24/96 to run and i
"aconnectgui is a FLTK based frontend for aconnect. It is written
directly on top of the aconnect source, leaving the original source
intact, only adding a couple of ifdefs, and some calls to the gui
part, so it provides exactly the same functionality, but with a
graphical userinterface."
http://
14 matches
Mail list logo
