[Alsa-devel] libasound and libpthread
Hi all, I am working with Alsa 0.9.0beta12 version and I am also using posix threads (libpthread) in my project. In the release version of the program I link both libraries (libpthread, libasound) dynamically and everything works well. In the debug version however, I have to do static linking of the libpthread for proper debugging. Here is the problem: If I try to link libasound dynamically and libpthread statically, the program crashes with a segmentation fault before even reaching the first line of my code (maybe, because libasound uses multithreading and libpthread itself ?). If I try to link both statically, the program runs at least some line of code, until it reaches the sound initialization. Then it crashes again with the following messages: ALSA lib conf.c:2540:(snd_config_hook_load) Unable to find field files in the preload section ALSA lib conf.c:1785:(snd_config_hooks_call) function snd_config_hook_load returned error: Invalid argument ALSA lib conf.c:2127:(snd_config_update) hooks failed, removing configuration Any help is appreciated. Thanks in advance Thomas --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] libasound and libpthread
I am working with Alsa 0.9.0beta12 version and I am also using posix threads (libpthread) in my project. In the release version of the program I link both libraries (libpthread, libasound) dynamically and everything works well. In the debug version however, I have to do static linking of the libpthread for proper debugging. why? i use pthreads a great deal, and i have never had to do this. and no, libasound does not use pthreads or any other form of threads. --p --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] ALSA docs
i would personally work from a complete set of snd-* modules, and use modinfo(1) + perl to get the information Isn't that what happens in the INSTALL file anyway? it doesn't look like it. there are several cards missing there, and it looks hand-written rather then fetched from the source. and put that into the temp file that is inserted into the template, or if possible, put it straight into the template. IIRC doing the above would need access to a set of modules online. Seems unneccesary when the INSTALL file is already available. But I'm willing to be told otherwise if it makes the info more reliable. it would be much more reliable if you got the options from the modules themselves. even just running grep for MOD_PARM etc. would be better than using the INSTALL file. --p --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] my first usb-midi experiment ends with segmentation fault
On Mon, Jul 29, 2002 at 12:40:51PM +0200, Takashi Iwai wrote: At Sun, 28 Jul 2002 23:39:24 +0200, Martin Langer wrote: ... and doing rmmod snd-usb-midi and rmmod snd-usb-audio ends here with Segmentation fault: Jul 28 22:28:07 tuba kernel: usb.c: deregistering driver snd-usb-audio Jul 28 22:28:10 tuba kernel: usb.c: deregistering driver snd-usb-midi Jul 28 22:28:10 tuba kernel: Unable to handle kernel paging request at virtual address 29323034 Jul 28 22:28:10 tuba kernel: printing eip: Jul 28 22:28:10 tuba kernel: e2858329 Jul 28 22:28:10 tuba kernel: *pde = Jul 28 22:28:10 tuba kernel: Oops: 0002 Jul 28 22:28:10 tuba kernel: CPU:0 Jul 28 22:28:10 tuba kernel: EIP: 0010:[snd-dt019x:__insmod_snd-dt019x_O/lib/modules/2.4.19-rc1/kernel/sound/i+-195799/96] hmm, why snd-dt019x module appears here..? was it loaded? the trace seems corrupted... yes, snd-dt019x was loaded, but that make no difference. could you try to put snd-usb-audio to /etc/hotplug/blacklist, so that it's not automatically loaded. then we'll know the problem is related only with snd-usb-midi. in both cases: - without snd-usb-audio - without snd-usb-audio and without snd-dt019x the same occurs. Yes, good arguments for a problem in snd-usb-midi. Here is what I have done: just a modprobe and rmmod. --- tuba:~# lsmod Module Size Used byNot tainted snd-mixer-oss 9056 0 (autoclean) (unused) snd24136 0 (autoclean) [snd-mixer-oss] soundcore 3364 0 (autoclean) [snd] tuba:~# modprobe snd-usb-midi tuba:~# rmmod snd-usb-midi Segmentation fault tuba:~# lsmod Module Size Used byNot tainted snd-usb-midi 0 0 (deleted) snd-seq-virmidi 2728 0 [snd-usb-midi] snd-seq-midi-event 2872 0 [snd-usb-midi snd-seq-virmidi] snd-seq37356 0 [snd-usb-midi snd-seq-virmidi snd-seq-midi-event] snd-timer 10400 0 [snd-seq] snd-rawmidi12224 0 [snd-seq-virmidi] snd-seq-device 3856 0 [snd-usb-midi snd-seq snd-rawmidi] snd-mixer-oss 9056 0 (autoclean) (unused) snd24136 0 (autoclean) [snd-usb-midi snd-seq-virmidi snd-seq-midi-event snd-seq snd-timer snd-rawmidi snd-seq-device snd-mixer-oss] soundcore 3364 0 (autoclean) [snd] tuba:~# Jul 29 14:15:09 tuba kernel: usb.c: registered new driver snd-usb-midi Jul 29 14:15:09 tuba kernel: snd-usb-midi: using interface 1 Jul 29 14:15:09 tuba kernel: snd-usb-midi: MIDIStreaming version 01.00 Jul 29 14:15:09 tuba kernel: snd-usb-midi: using 1 input jack(s) on endpoint 1 Jul 29 14:15:09 tuba kernel: snd-usb-midi: using 1 output jack(s) on endpoint 2 Jul 29 14:15:09 tuba kernel: snd-usb-midi: detected Evolution Electronics L MK-2 49C USB MIDI keyboa Jul 29 14:15:14 tuba kernel: usb.c: deregistering driver snd-usb-midi Jul 29 14:15:14 tuba kernel: printing eip: Jul 29 14:15:14 tuba kernel: e2b20329 Jul 29 14:15:14 tuba kernel: Oops: 0002 Jul 29 14:15:14 tuba kernel: CPU:0 Jul 29 14:15:14 tuba kernel: EIP:0010:[e2b20329]Not tainted Jul 29 14:15:14 tuba kernel: EFLAGS: 00210246 Jul 29 14:15:14 tuba kernel: eax: 29323030 ebx: db5021c0 ecx: db502204 edx : db502100 Jul 29 14:15:14 tuba kernel: esi: db500c00 edi: 1fff ebp: e2b3b7dc esp : db041ee4 Jul 29 14:15:14 tuba kernel: ds: 0018 es: 0018 ss: 0018 Jul 29 14:15:14 tuba kernel: Process rmmod (pid: 485, stackpage=db041000) Jul 29 14:15:14 tuba kernel: Stack: daf98380 dd446e00 e2b203ed db500c00 e2b18e5a daf98380 1000 e2b18fc5 Jul 29 14:15:14 tuba kernel:dd446e00 db500c00 dd446e00 0001 e2b3b7c0 e2b159ae dd446e00 0001 Jul 29 14:15:14 tuba kernel: e2b3aa01 dd446e00 dfe688d8 c021e47d dfe67800 dd446e00 dfe67300 Jul 29 14:15:14 tuba kernel: Call Trace: [e2b203ed] [e2b18e5a] [e2b18fc5] [e2b3b7c0] [e2b159ae] Jul 29 14:15:14 tuba kernel:[e2b3aa01] [usb_drivers_purge+141/224] [e2b3b 7c0] [usb_drivers_purge+62/224] [e2b3b7c0] [e2b3b7c0] Jul 29 14:15:14 tuba kernel:[usb_deregister+114/144] [e2b3b7c0] [e2b3aa8a ] [e2b3b7c0] [free_module+23/160] [sys_delete_module+247/448] Jul 29 14:15:14 tuba kernel:[system_call+51/56] Jul 29 14:15:14 tuba kernel: Jul 29 14:15:14 tuba kernel: Code: 89 50 04 89 02 ff 4b 3c ff 43 44 0f 8e 05 07 00 00 53 56 e8 --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] libasound and libpthread
Paul Davis wrote: I am working with Alsa 0.9.0beta12 version and I am also using posix threads (libpthread) in my project. In the release version of the program I link both libraries (libpthread, libasound) dynamically and everything works well. In the debug version however, I have to do static linking of the libpthread for proper debugging. why? i use pthreads a great deal, and i have never had to do this. and no, libasound does not use pthreads or any other form of threads. Thomas, you should know to not rely too strong to Paul's words. He own a big heart, but unfortunately a big mouth too, that he's often unable to keep under control ;-) Some portions of libasound *do* use pthreads. -- Abramo Bagnara mailto:[EMAIL PROTECTED] Opera Unica Phone: +39.546.656023 Via Emilia Interna, 140 48014 Castel Bolognese (RA) - Italy --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] current cvs: unresolved symbols
Hi, At Sun, 28 Jul 2002 11:54:30 -0700 (PDT), Fernando Pablo Lopez-Lezcano wrote: Found in current cvs: # depmod -ae depmod: *** Unresolved symbols in /lib/modules/2.4.18-10.llsmp/kernel/drivers/sound/isa/snd-dt0197h.o depmod: snd_sbdsp_create_Rsmp_3f86b411 depmod: snd_sbmixer_new_Rsmp_2880de09 depmod: snd_sb16dsp_pcm_Rsmp_4d33d580 it's an obsolete module, which was renamed to snd-dt019x. just remove this file. Takashi --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] libasound and libpthread
Abramo Bagnara wrote: Paul Davis wrote: I am working with Alsa 0.9.0beta12 version and I am also using posix threads (libpthread) in my project. In the release version of the program I link both libraries (libpthread, libasound) dynamically and everything works well. In the debug version however, I have to do static linking of the libpthread for proper debugging. why? i use pthreads a great deal, and i have never had to do this. More precisely, I would like to do some breakpoint debugging. The only way I know of doing this with multithreaded programs, is to link libpthread statically (and I tried this with gdb). Anyway, the question to me is, are there in general for some reasons problems to be expected, when linking libasound statically or is it only in connection with multithreading or is it because of some unknown error of mine ? and no, libasound does not use pthreads or any other form of threads. Thomas, you should know to not rely too strong to Paul's words. He own a big heart, but unfortunately a big mouth too, that he's often unable to keep under control ;-) Some portions of libasound *do* use pthreads. I hope I did'nt raise any kind of fight between the two of you :-) . Thanks for your comments Regards Thomas --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] libasound and libpthread
Paul Davis wrote: Paul Davis wrote: I am working with Alsa 0.9.0beta12 version and I am also using posix threads (libpthread) in my project. In the release version of the program I link both libraries (libpthread, libasound) dynamically and everything works well. In the debug version however, I have to do static linking of the libpthread for proper debugging. why? i use pthreads a great deal, and i have never had to do this. and no, libasound does not use pthreads or any other form of threads. Thomas, you should know to not rely too strong to Paul's words. He own a big heart, but unfortunately a big mouth too, that he's often unable to keep under control ;-) its true. mea culpa. this is what we get for a library containing large chunks of code and functionality not used by anyone except its author :) is there anyone on the list except abramo or jaroslav that have ever used the shared PCM device type? I have looked into it but cannot see clear reason for using it. -- Patrick Shirkey - Boost Hardware Ltd. For the discerning hardware connoisseur Http://www.boosthardware.com Http://www.boosthardware.com/LAU/guide/ --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] ALSA docs
Do you mean that I should be parsing each driver file seperately?
not really, just do a single pass over each one of them at some point
in time. store the results, and use them. this should get you started
(its not perfect, but it doesn't do a bad job.
#!/usr/local/bin/perl
while() {
if (/MODULE_PARM_DESC/) {
@foo = split /[()]/;
@bar = split (/,/, $foo[1], 2);
$bar[1] =~ s///g;
printf (%-32s %s\n, $bar[0], $bar[1]);
}
}
add something to recurse through the source tree, and include the
module name and card name info, and you're pretty much done ...
--p
---
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] ALSA docs
Paul Davis wrote:
Do you mean that I should be parsing each driver file seperately?
not really, just do a single pass over each one of them at some point
in time. store the results, and use them. this should get you started
(its not perfect, but it doesn't do a bad job.
#!/usr/local/bin/perl
while() {
if (/MODULE_PARM_DESC/) {
@foo = split /[()]/;
@bar = split (/,/, $foo[1], 2);
$bar[1] =~ s///g;
printf (%-32s %s\n, $bar[0], $bar[1]);
}
}
add something to recurse through the source tree, and include the
module name and card name info, and you're pretty much done ...
Now that I think about it I could probably get away with doing this on
my computer everytime that a new driver is added. We have to add the
info manually for the soundcard matrix anyway.
Although If I don't have access to a working Linux computer in the
future this will cause problems. Ideally I would like a way to do this
all from online preferably automagically.
I'm loathe to admit but I am very new to perl so I don't even know how
to call the above code from a webpage. Is it possible to get the perl
script to parse the files and then use php to parse the output of the
perl script? I have various variables from a form which php can
understand and use to create the correct output in the template.
Unless Dan Hollis speaks up soon (I tried to contact him last Friday)
I'm officially commandeering the Soundcard matrix from his dir and
putting it in the alsa-docs dir. Where it will become the opening page
to the driver docs. He will need to get cvs access for the www dir from
Jaroslav to edit the new version of the matrix.
You can see what I'm trying to do here:
http://www.alsa-project.org/alsa-doc/ALSA_Soundcard_Matrix.php3
That is unless other people have a better idea for how to make the docs
more user friendly (and competitive ;] ).
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
---
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] guitar + sblive + ardour + ladspa effects
Hi all, This is what I want to do: guitar into the line input on the live drive, that going into ardour, through a few ladspa effects, and out to the speakers. I can't seem to do this. The only way I seem to be able to get the input into ardour is to have it going through the speakers as well so that both the input and the ladspa-processed output can be heard. I only want the ladspa-processed output. Is this possible? I've had a search through the alsa-devel, alsa-user and ardour-devel archives, as well as the alsa wiki and a google search. I am yet to be enlightened. The SB-Live-mixer.txt is a probably a nice set of notes if you're a driver writer, but I'm not. name='Line LiveDrive Capture Volume',index=1 name='Line LiveDrive Capture Volume',index=1 This control is used to attenuate samples from left and right I2S ADC inputs (on the LiveDrive). The result samples are forwarded to the ADC capture FIFO (thus to the standard capture PCM device). What's the ADC capture FIFO? What's the standard capture PCM device? What have these to do with recording from hw:0,0? Why is it that ardour only seems to be able to hear the line input when I put up the volume on Line LiveDrive and not Line LiveDrive Capture? What is the Capture device sitting in alsamixer? What difference does the little red Capture make above the sliders in alsamixer? If it's not possible to this with only the sblive, I have the motherboard's soundcard as well but how do I get jackd to deal with more that one bit of hardware? I hope somebody can help as I'm utterly confused. Bob -- Bob Ham: [EMAIL PROTECTED] http://pkl.net/~node/ --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] ALSA docs
Paul Davis wrote:
#!/usr/local/bin/perl
while() {
if (/MODULE_PARM_DESC/) {
@foo = split /[()]/;
@bar = split (/,/, $foo[1], 2);
$bar[1] =~ s///g;
printf (%-32s %s\n, $bar[0], $bar[1]);
}
}
add something to recurse through the source tree, and include the
module name and card name info, and you're pretty much done ...
I tried the above but it didn't work for me by itself and I don't have
the insight at the moment to get it to. Thanks anyway because you jogged
my memory.
I remembered that Jaroslav had given me a command a while ago (last
year) to get the module options for each module.
modinfo $(modprobe -l snd-*) | cat /art/code/alsa/modinfo
This returns a reasonably readable file. If I make a perl script to
parse that and print a more readable version then I have what I need for
now.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
---
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] SB Live and Audigy development
Hello ALSA list Would someone please tell me who the main developers of the SB Live and Audigy drivers are and their email addresses? Thanks, Daniel Sheltraw _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] guitar + sblive + ardour + ladspa effects
This is what I want to do: guitar into the line input on the live drive, that going into ardour, through a few ladspa effects, and out to the speakers. I can't seem to do this. The only way I seem to be able to get the input into ardour is to have it going through the speakers as well so that both the input and the ladspa-processed output can be heard. I only want the ladspa-processed output. Is this possible? sure. assuming we're talking stereo: add 2 routes (*without* diskstreams) set the inputs to in 1 and in 2 respectively (from the mixer window) set the outputs to out 1 and out 2 respectively (from the mixer window) add the desired plugins to each route listen ... before you do all this, however, you need to have set up the line input as the capture source. that's an sblive specific issue on which i have no knowledge whatsoever. you will also probably want to turn down the line-in level, so that the direct feed is not audible. that is also an sblive issue. ALSA has a correctly designed mixer API to reflect the true capabilities of various mixing hardware, but the vast differences between audio interfaces and the lack of a standard (every card must provide the following mixer controls if it provides any at all) makes this stuff much harder than it should be. or so it seems from reading messages to the list. Capture device sitting in alsamixer? What difference does the little red Capture make above the sliders in alsamixer? it controls which sources are being used for capture *by the hardware*. they should be over the relevant sources in alsamixer. If it's not possible to this with only the sblive, I have the motherboard's soundcard as well but how do I get jackd to deal with more that one bit of hardware? jackd -d alsa -d hw:N where N is the relevant card number for the motherboard audio interface. --p --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [ardour-dev] Re: [Alsa-devel] guitar + sblive + ardour + ladspaeffects
On Mon, 2002-07-29 at 21:31, Patrick Shirkey wrote: Have a read of the arecord quicktoot http://www.boosthardware.com/LAU/quicktoots That will give you some info about using alsamixer correctly. Getting ardour to be able to record/modify the incoming sound isn't the issue. It's getting ardour to do that without it going through the speakers beforehand. I don't want to hear any sound if I put the mixer slider down to nothing in ardour. At the moment, I hear the original, clean guitar signal. I assume the line input is getting routed to both jack's alsa_pcm inputs and the soundcard's amp. I want it only to go to jack, and then the ladspaified signal to the amp afterwards. Bob -- Bob Ham: [EMAIL PROTECTED] http://pkl.net/~node/ --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] my first usb-midi experiment ends with segmentation fault
Hello! I'm happy to see that I'm not the only MIDI guy at ALSA-USB world :) El Dom 28 Jul 2002 23:39, Martin Langer escribió: my new USB-MIDI-Keyboard has two USB subclasses usb-midi and usb-audio. Evolution, the manufacturer, told me it's an Audio Class compliant device, but I don't find a new entry in /proc/asound/seq/clients after loading the modules. cat /proc/bus/usb/devices T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=01(audio) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0a4d ProdID=008e Rev= 2.00 S: Manufacturer=Evolution Electronics Ltd. S: Product=MK-249C USB MIDI keyboard C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=snd-usb-audio I: If#= 1 Alt= 0 #EPs= 2 Cls=01(audio) Sub=03 Prot=00 Driver=snd-usb-midi E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms dmesg: usb.c: registered new driver snd-usb-audio usb.c: snd-usb-audio driver claimed interface dfe688c0 usb.c: registered new driver snd-usb-midi snd-usb-midi: using interface 1 snd-usb-midi: MIDIStreaming version 01.00 snd-usb-midi: using 1 input jack(s) on endpoint 1 snd-usb-midi: using 1 output jack(s) on endpoint 2 snd-usb-midi: detected Evolution Electronics L MK-249C USB MIDI keyboa usb.c: snd-usb-midi driver claimed interface dfe688d8 It's not typical to have a midi-keyboard with two subclasses, or? IMHO, those descriptors are very close to the USB-Audio specification. Your keyboard presents two interfaces: an AudioControl interface (Sub=01) and a MIDIStreaming one (Sub=03). Perhaps the snd-usb-audio claims making a very quick decision based only on the AudioControl interface. The AudioStreaming interface is Sub=02, and your keyboard has not one. I am using two USB MIDI devices at home, both with the snd-usb-midi driver; an Edirol UM-2 (semi-compliant) and a Midiman Midisport 2x2, with a nice GPL firmware by Lars Doelle, that tryes to follow the standard. FYI, these are my last device descriptors: T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0763 ProdID=1110 Rev= 0.01 S: Manufacturer=Midiman S: Product=Midisport 2x2 S: SerialNumber=Copyright (GPLv2) 2001 by Lars Doelle [EMAIL PROTECTED] C:* #Ifs= 2 Cfg#= 1 Atr=00 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=(none) I: If#= 1 Alt= 0 #EPs= 2 Cls=01(audio) Sub=03 Prot=00 Driver=snd-usb-midi E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms As you can see, very similar to yours. You can find the specs at http://www.usb.org/ The relevant documents about USB Audio Class and USB MIDI subclass are: - Universal Serial Bus Revision 1.1 specification, http://www.usb.org/developers/data/usbspec.zip - Audio Device Document 1.0, http://www.usb.org/developers/data/devclass/audio10.pdf - USB MIDI Devices 1.0, http://www.usb.org/developers/data/devclass/midi10.pdf ... and doing rmmod snd-usb-midi and rmmod snd-usb-audio ends here with Segmentation fault: I can't reproduce this behaviour at home. Perhaps the jack or endpoint descriptor parser in snd-usb-midi gets confused for your keyboard. AFAIK, the MK-249C is not listed as tested or supported, though. What I do is blacklist all the snd-usb-* and the corresponding usb oss modules, avoiding hotplug from loading them. Instead, the /etc/init.d/alsa boot script loads them, with some /etc/modules.conf lines like these: alias char-major-14 soundcore alias char-major-116 snd alias snd-card-0 snd-ens1371 alias snd-card-1 snd-usb-midi alias sound-slot-0 snd-card-0 alias sound-slot-1 snd-card-1 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss This is not very coherent with the usual USB devices hotplugging capabilities, but you have the chance of setting some options. Anyway, if your device is not 100% standard, perhaps you have to tweak the alsa-driver/usb/usbmidi.c file (search for 'snd_usbmidi_usb_id_table'). Another option is to use the daemon, that runs in userspace, and perhaps can be easy for experiment with it, along with hotplug. You can find it at: http://www.informatik.uni-halle.de/~ladischc/usbmidid.html Regards, Pedro --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] general audio card Q
Hello ALSA list Besides the RME PST card, are there other sound cards which can do interrupt driven data transfer to double-buffers (ie. no DMA) for playback? Thanks, Daniel Sheltraw _ Chat with friends online, try MSN Messenger: http://messenger.msn.com --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Re: guitar + sblive + ardour + ladspa effects
Bob Ham wrote: Err.. I mean have *both* cards in jack. I have a ~/.asoundrc with platinum51 and via devices defined. I normally do jackd -d alsa -d platinum51. Doing jackd -d alsa -d platinum51 -d via makes it only use the via card. How can I tell it to use both? There is some info on how to set up your .asoundrc for this operation in the alsa wiki. http://alsa.opensrc.org -- Patrick Shirkey - Boost Hardware Ltd. For the discerning hardware connoisseur Http://www.boosthardware.com Http://www.boosthardware.com/LAU/guide/ --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
