did you see where I said this may be a hal issue. Plugdevice permission.deamon that is a must on 12.2 and also I see the system treats this as a usb snd devices.
|
Quote:
Quote:
Quote:
Yet another interesting direction to search ;-) One day I'll really know everything about life, the universe and everything... |
While wandering about the internets I stumbled upon this document, as I'm not at home and think there may be answers here that are on topic I post the URL: http://www.tldp.org/HOWTO/MIDI-HOWTO-10.html
Especially the part virmidi a virtual midi card seems like something that I overlooked. (along with the HAL thingey :p) |
re-scanned the soundcard with alsaconf, generating this file:
Code:
root@slacker:/etc# cat /etc/modprobe.d/sound Starting now with the virmidi module and following the howto I linked before, will update on results of that. |
Good news: I got zoundz from le keyboard!
Reading the howto I got on the aconnect thing, I doubt the virmid has much to do with the solution. When running aconnect -i, aconnect -o, aconnect -lo I could see which interfaces were available. I connected the keyboard (port 20:0) with timidity (port 128:0) and got sounds. Here's some outputs: (yes, I did everything with root, to eliminate a "rights" issue; this all should work with normal user privileges as well) Checking which interfaces are available: Code:
root@slacker:~# aconnect -lo Code:
root@slacker:~# aconnect 20:0 128:0 Code:
root@slacker:~# aconnect -lo - When the keyboard is plugged at boot time timidity won't start with the -Os option; With the keyboard plugged after boot this is no issue. This probably is due to Alsa now knowing which card is the default. I'll have to look into that. - will now have to make sure aconnect is done "automagically"... I'll see how I can do that :-) - it's frustrating and humiliating how simple the solution eventually was ;-) oh well :-D it works now... I'll make a nice writeup for those of you that are interested in connecting keyboards to your slack box. All in all, I'm a happy man now. Thanks to all for input! |
Quote:
|
:-) You're welcome :-)
As promised I would do a writeup of what you need to get your keyboard working in Slack 12.2, KDE4 (there is a significant difference, since KDE 3.x use aRts, which was my primary reason to get rid of KDE 3.5) What you need (apart from the obvious): - patience, chances are things won't work for you right out of the box - I'll assume you have a working soundcard and get sounds otherwise out of Alsa (mp3, games, movies etc) - An external keyboard. Myself I use an E-MU Xboard 61, which connects via USB. - I'll assume the stock 2.6.27-smp kernel that comes with Slack 12.2 - Proper privileges (the user must be member of audio and plugdev groups) - A Soft Synth; Myself I use TiMidity++; Get a nice soundfont as well (I got the big one from www.personalcopy.com, it sounds good to me) - Jack - A recording program like Rosegarden is nice, but not really mandatory. You just bought this nice keyboard and you plug it in, turn it on and press some keys... and omg... no sound! The horror! What is wrong? Here's where our experience begins, and some kind of experience it will be! Let's see if you have TiMidity running: Code:
$ ps -ef | grep timidity Code:
/usr/bin/timidity -iA -B2,8 -Os --volume=200 Ok, so timidity is running but we still hear nothing! Let's see if your device is actually seen when you plug it in (I noticed that if I plugged it in at boot time both the sound and the keyboard woudn't work. It appears that having the keyboard plugged in at boot time confuses alsa so it cannot determine which device is the default output device...) Code:
$ dmesg | tail Code:
usb 6-2: new full speed USB device using ohci_hcd and address 3 Ok, so now we know the device is seen by Linux, and Timidity is running... let's press some keys and listen to da music... Still no sound! Now what the heck?!? The reason is not as bad as you may have feared... The device is "there" but your system probably just doesn't know what to do with the midi events that are sent. So we have to get those events to Timidity. Here's how we can do that: Code:
$ aconnect -lo Code:
$ aconnect 20:0 128:0 Code:
aconnect -lo When you press keys on your keyboard you will probably hear music! But why stop there? You want your playings recorded so you can listen back and maybe even produce nice sheets of your musings. For this I use Rosegarden. For Rosegarden jack is required, and a handy tool to control jack with is qjackctl. What jack exactly does is a tad unclear to me, but since you'll need it, we'll use it. Eventually that was about all that was needed; Hope you'll enjoy! Feedback welcome! |
All times are GMT -5. The time now is 10:51 PM. |