Re: [Alsa-user] Two USB devices, mixer?

[Bob Hartmann]

Thank you for the hints.  There's some output below to chew on in case 
anyone's hungry.  It looks OK to me but what do I know..  There may be 
an obvious problem there.  I need to familiarize myself with 
modules.conf some more.  SuSE wants me to use modules.conf.local for my 
own stuff so I may have conflicts there.  I don't care about the order 
and I'd rather the ensoniq was out of the picture completely...  I'm 
happy I can get sound out of the Duo at this point.
I'm packing for a trip to Las Vegas now, so this will wait for next 
week.  thanks again



lsusb
-------------------------------------------
Bus 005 Device 001: ID 0000:0000
Bus 005 Device 002: ID 8086:0431 Intel Corp. Intel Pro Video PC Camera
Bus 005 Device 003: ID 0763:1021 Midiman
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 003 Device 005: ID 0763:2002 Midiman
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
cat /proc/asound/cards
-------------------------------------------
0 [M4x4           ]: USB-Audio - MidiSport 4x4
                    M-Audio MidiSport 4x4 at usb-00:14.1-2
1 [AudioPCI       ]: ENS1371 - Ensoniq AudioPCI
                    Ensoniq AudioPCI ENS1371 at 0xd800, irq 10
2 [Duo            ]: USB-Audio - USB AudioSport Duo
                    M Audio USB AudioSport Duo at usb-00:11.3-1
  AND some Jack messages (loading the Ensoniq)  btw, qjackctl won't let 
me get to any connections with the Ensoniq if the Duo is turned on!
------------------
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:1|hw:1|1024|2|44100|0|0|nomon|hwmeter|rt|32bit
control device hw:1
configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:1 for 32bit samples trying 24bit instead
Couldn't open hw:1 for 24bit samples trying 16bit instead
Couldn't open hw:1 for 32bit samples trying 24bit instead
Couldn't open hw:1 for 24bit samples trying 16bit instead
playback and capture sample rates do not match (44100 vs. 44099)
JACK: unable to mlock() port buffers: Operation not permitted
cannot set thread to real-time priority (FIFO/20) (1: Operation not 
permitted)
cannot use real-time scheduling (FIFO/10) (1: Operation not permitted)



Clemens Ladisch wrote:

Bob Hartmann wrote:
 

-M-audio MidiSport 4x4 USB and M-audio Mobile Duo (USB)

So there are 2 ALSA devices with the same name.
   

They should have different names.  What does /proc/asound/cards say?

 

Alsaplayer will play midi files but not CDs.
   

It assumes that the audio output of the CD drive is connected to the
line input of the sound card.
 

The 2 USB devices give me 'no mixer elems found' I've read that
neither have a hardware audio mixer, so what do I use instead?
   

The MidiSport just sends MIDI data to other devices; it's the
synthesizer that would have a volume control.
The Duo indeed doesn't have a volume control.  You'd have to scale the
audio data before sending it to the device.  (Some future version of
ALSA may be able to do this.)
 

It would seem that c 0 is the MIDI controller, c 1 is the
on-board, and c 2 is the USB Audio Duo (the one I want to use for
RoseGarden, Audacity, whatever..)
   

You can change the order with some entries in module.conf.  For
example, if your cards should be 0:Duo, 1:4x4, 2:onboard, use:
options snd-usb-audio index=0,1 pid=0x____,0x1021
options snd-ens1371 index=2
where ____ is the product ID of the Duo (see lsusb).

You can change the order by changing the index parameters.

HTH
Clemens


 



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user