Clemens Ladisch wrote:
Daniel Hawthorn wrote:
Do you have the USB host controller driver loaded, or is it compiled
into the kernel?
Does the Quattro show up with lsusb?
By host controller driver, do you mean UCHI? I made sure to compile
this into the kernel. When I unplug the quattro and then
Hi all,
I'm working on getting sound up and running on my 2.6.0-test7 kernel
I've built from source, running on a Debian system. My system is using
a M-Audio Quattro audio device.
I've gotten alsa up and running fine on other kernels before (2.4.18,
2.4.20, etc) where the alsa drivers weren't
You need to do "alsactl restore" once you've rebooted to reload the
levels. You'll need to put this in your init scripts to do it
automatically. How you do this exactly depends on your distro - if you
need more help on this, please respond with what distro of linux you are
using.
-Daniel
Ju
I seem to have come to the bottom of this one in some further
experimentation. I've gotten the midi input on my quattro to work
(very) occationally, without understanding why. Each time I got it to
work I would reboot to see if whatever I thought it was, was in fact the
real solution. Each t
Fabulous!
I recompiled my kernel, adding usbdevfs support, and added the line to
my fstab. The midisport works wonderfully now. It didn't start
automatically on bootup, but when I unplugged/replugged it loaded the
firmware fine. I will add the line to my modules.conf to see if I can
get it
Clemens Ladisch wrote:
The last message should have the usbfs file name after the "to"
(something like /proc/bus/usb/001/004). Are you sure you didn't
accidentally delete the last part?
Oh! You may have somthing here... doing "ls /proc/bus" gives me only
two directories: "pccard" and "pci", no "u
Clemens Ladisch wrote:
Do you see something when you run "cat /dev/snd/midiCxD0", where x is
the card number?
Not a thing - midiC1D0 is the only device that exists when I do a "cat
/dev/snd/" and I see nothing when I pound some keys on my MIDI
controller.
Are there any messages in /var/log/m
Hello all,
I'm trying to get my Midisport USB midi interface working on my Debian
system. I used to have it running fine when I had RedHat on this
laptop, but since switching over to Debian have been unable to get the
firmware to load to the device properly.
/var/log/messages gives me then when I
Hi list,
I'm currently running a Debian system on with a M-Audio Quattro
midi/audio interface. Everything is working great except I get no midi
input from the device. Midi out works great, audio in/out works great.
Just... no midi in. I generally test using PD to see if I see any
midi input an
By only one channel gets recognized, do you mean only outs 1+2 (and not
3+4)? This may be due to the fact that you are using the default
device. Try telling whatever app you are using to use the "quattro" or
"q4b" device, provided you have your .asoundrc setup like it says in the
soundcard ma
I've had this exact problem as well, running a RedHat 8.0 system on my
laptop. After weeks of trying to figure out what was wrong, I finally
pinned the problem on my PCMCIA ethernet card of all things. When I
booted the system without it inserted, let all the services start
(including alsasou
The Quattro doesn't have headphone outs, but, the outs it does have are
sufficiently powered to drive headphones. A two-mono-1/4"->stereo-1/4"
adapter connected to two outs should work fine if you need headphones.
-Daniel
Frank Barknecht wrote:
Does the Quattro have headphone outs? I thought n
Hi all,
I'm using a M-Audio quattro and I have my system set up so that I can
record and hear audio. However, alsamixer reports I have "No mixer
elements found." I've configured my system according to the
instructions on the alsa page, including the .asoundrc files and such.
Any ideas why I
13 matches
Mail list logo
