Re: [Alsa-devel] mutli channel
On Saturday February 1 2003 12:22 pm, ljp wrote:
> 2) I am not real clear on how to use the mixer. What would be the bare
> minimum steps to get the main volume?
to answer my own question, perhaps. minimal to get volume:
snd_mixer_open
snd_mixer_attach
snd_mixer_selem_register
snd_mixer_load
for{} through the elements
if( snd_mixer_selem_is_active
if( snd_mixer_selem_has_common_volume
if( snd_mixer_selem_has_playback_volume
snd_mixer_selem_get_playback_volume
correct?
ljp
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Automounting my 1394 drives causes Alsa to notload...
On Sat, 2003-02-01 at 12:31, Fernando Pablo Lopez-Lezcano wrote: > > 1) Old problem - if my MidiSport 2x2 is plugged in when I cold boot, > > then Alsa gets loaded when the MidiSport is found. When I get to the > > part of the boot process where Alsa is supposed to get started, I get a > > 'Failed' message, telling me Alsa is already running. Even this is OK, > > but then later when Linux attempt to load the HDSP 9652 drivers, they > > fail one out of two times saying they cannot allocate memory. > > I think the solution to this one is to "blacklist" the alsa driver so > that hotplug does not load it while the system is starting up. To do > that just add a line with "snd-usb-audio" to the end of > /etc/hotplug/blacklist > You probably already have "audio" and "usb-midi" there (the oss kernel > modules that deal with usb audio and midi). > Fernando, Thanks! Early indications are that this helps. I'll keep an eye on it and see how it goes. Cheers, Mark --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Automounting my 1394 drives causes Alsa to notload...
> 1) Old problem - if my MidiSport 2x2 is plugged in when I cold boot, > then Alsa gets loaded when the MidiSport is found. When I get to the > part of the boot process where Alsa is supposed to get started, I get a > 'Failed' message, telling me Alsa is already running. Even this is OK, > but then later when Linux attempt to load the HDSP 9652 drivers, they > fail one out of two times saying they cannot allocate memory. I think the solution to this one is to "blacklist" the alsa driver so that hotplug does not load it while the system is starting up. To do that just add a line with "snd-usb-audio" to the end of /etc/hotplug/blacklist You probably already have "audio" and "usb-midi" there (the oss kernel modules that deal with usb audio and midi). -- Fernando --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] Automounting my 1394 drives causes Alsa to not load...
Hi, Bit of a problem. This is Redhat 7.3, PlanetCCRMA flow, and the machine has 256MB. Alsa has been working reasonably well for me, but I have two problems that I would really like to fix: 1) Old problem - if my MidiSport 2x2 is plugged in when I cold boot, then Alsa gets loaded when the MidiSport is found. When I get to the part of the boot process where Alsa is supposed to get started, I get a 'Failed' message, telling me Alsa is already running. Even this is OK, but then later when Linux attempt to load the HDSP 9652 drivers, they fail one out of two times saying they cannot allocate memory. 2) When I try to auto-mount my 1394 hard drives by creating an auto-mount entry in /etc/fstab, they may not be turned on, which is legal. However, in this situation Alsa always fails to load. I have to make the drive 'noauto' to get Alsa to start correctly. Both of these problems seem to be solved by warm booting the system. However, that takes time and I certainly shouldn't have to do that. What can I do to solve these problems so that Alsa will come up correctly on my first cold boot. Cheers, Mark --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] mutli channel
I have a couple questions 1) does alsa have support for multichannel output? If so, how would one go about sending individual signals to channels 1-8? 2) I am not real clear on how to use the mixer. What would be the bare minimum steps to get the main volume? thanks. ljp --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] RC7 and CS46xx (GTXP)
> Something between CVS 2002-12-18 and RC7 seriously broke the amplifier > stuff for me on my GTXP - sound is very disorted and volume is very > low. It's different from the troubles RC6 gave me though. I'd guess > it's the recent amplifier patch that was applied to the CS46xx driver. Replying to my own mail, I know:) I reverted the changes the recent amplifier patch did to cs46xx_lib.c and RC7 works perfectly - no warning in dmesg either. -- Richard Olsson [EMAIL PROTECTED] http://www.nyo-box.net/ - http://www.aelia-studios.org/ --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] RC7 and CS46xx (GTXP)
Something between CVS 2002-12-18 and RC7 seriously broke the amplifier stuff for me on my GTXP - sound is very disorted and volume is very low. It's different from the troubles RC6 gave me though. I'd guess it's the recent amplifier patch that was applied to the CS46xx driver. Only oddity I see is in dmesg: ALSA ../../alsa-kernel/pci/cs46xx/cs46xx_lib.c:415: cs46xx: failure waiting for FIFO command to complete I'll stick to the 2002-12-18 CVS for now:) -- Richard Olsson [EMAIL PROTECTED] http://www.nyo-box.net/ - http://www.aelia-studios.org/ --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
