On 08/19/03 03:58:33, Daniel James wrote: Yes. I've been working hard to make sure a recent and working alsa is part of 9.2, and I only have about two weeks left to do so. As of last night, I believe all alsa-related packages are 0.9.6, and everything seems to be working well except my M-Audio Quattro, which works with alsa build from source, but not with the driver included with the kernel. I'm working on a solution though. Everything else is up-to-date as well I believe. Ardour beta3, audacity, muse, swami, fluidsynth, all of Holborn's stuff, the multimedia kernel, and a fancy new GUI for jack, etc. etc. I still haven't managed to figure out a way to get csound in, but I figure that anyone smart enough to be able to actually USE csound will also be smart enough to know how to install it. :-) Austin -- Austin Acton Hon.B.Sc. Synthetic Organic Chemist, Teaching Assistant Department of Chemistry, York University, Toronto MandrakeClub Volunteer (www.mandrakeclub.com) homepage: www.groundstate.ca

On 08/26/03 06:31:04, Chris Butt wrote: You need at least ALSA 0.9.5. Mandrake 9.2beta2 only had 0.9.2. Currently we have 0.9.6 in the cooker kernel, but it's broken. If you just compile the alsa drivers from source and install them with 'checkinstall' everything works fine. My quattro sounds great using cooker and alsa from source. We're trying to get the broken kernel alsa working ASAP. Yes, you need to do this, but it's an unrelated problem. Same deal, you'll have to blacklist 'audio'. The problem is that the hotplug device list is created automatically from the kernel modules, and there is no way for a distribution to 'set' the order hotplug detects your devices in. So since 'audio' comes before 'snd-usb-audio' or whatever, 'audio' gets chosen first. We (Mandrake) are also working on a way to fix this, but we are not too hopeful. Let me know how it goes. Austin -- Austin Acton Hon.B.Sc. Synthetic Organic Chemist, Teaching Assistant Department of Chemistry, York University, Toronto MandrakeClub Volunteer (www.mandrakeclub.com) homepage: www.groundstate.ca

On 08/27/03 12:14:56, Patrick Shirkey wrote: Yes, but only with arecord. No luck with audacity or ardour yet. As of kernel 2.4.22 though, sound in totally broken now. The madness never ends. Austin -- Austin Acton Hon.B.Sc. Synthetic Organic Chemist, Teaching Assistant Department of Chemistry, York University, Toronto MandrakeClub Volunteer (www.mandrakeclub.com) homepage: www.groundstate.ca

On 08/30/03 04:16:39, Chris Butt wrote: Yes. Although you should probably use ./configure --prefix=/usr --disable-verbose-printk See above. Stupid verbose-printk problem alsa should have fixed long ago. I will work using that configure line. Austin -- Austin Acton Hon.B.Sc. Synthetic Organic Chemist, Teaching Assistant Department of Chemistry, York University, Toronto MandrakeClub Volunteer (www.mandrakeclub.com) homepage: www.groundstate.ca

Hello, I am having some problems getting muse to work with the USB M-Audio Quattro. I'm mentioning the device because I am not 100% sure the problem is due to MusE. It could be a Quattro config problem. Anyway, playback seems to work fine (the song position pointer is moving) but no midi comes out of the outputs. The error messages: MidiAlsaDevice::putEvent(): midi write error, returns -19 expected 28: No such device ...and at startup of muse I get: 'WARNING: Cannot lock memory:: Operation not permitted' I'm using Gentoo with 2.4.22 kernel and alsa 0.9.6 compiled from source. Muse I installed as ebuild from Gentoo. Does anybody have experience with this setup or know what the problem might be? Many thanks in advance, Jelmer