12 Aug
2003
12 Aug
'03
7:37 p.m.
Hi
I just installed kernel 2.6.0-test3 on my laptop. I looked around in
/proc and saw all kinds of promissing things showing up there.
/var/log/messages even showed my Evolution USB keyboard. Very nice. But
since I'm fairly new to the kernel2.6.0/build-in-ALSA I'm hoping for
some pointers just to get started.
1) I didn't do any configuration of ALSA. Is that needed? If so how do I
do it now that ALSA is compiled in?
2) Where can I expect my devices to show up? For now I have an onboard
soundcard (i810) and the Evolution keyboard. I would like to route the
incomming midi to csound, but later also to either Muse or Rosegarden4.
Is that a matter of having the softsynth or sequencer read from
/dev/midi00 (or somthing like that)? And do I simply tell the sound
generating software to direct its output to the appropriate device, say
/dev/audio?
3) I noticed somethiing jack showing up. Is jack supported? If so, to
what extend?
4) What would be a nice program use for figuring out what midi-events
the knobs on the Evolution sends?
Hope some of you could find the time to either explain me a bit or send
me in direction of some useful documentation. Thanks in advance.
--
peace, love & harmony
Atte
12 Aug
12 Aug
8:13 p.m.
1) I didn't do any configuration of ALSA. Is that needed? If so how do I
do it now that ALSA is compiled in?
If Alsa is running, then lsmod will show you the sound modules you are
running from /etc/modules.conf. lspci should show you what hardware the
system is seeing.
2) Where can I expect my devices to show up? For now I have an onboard
soundcard (i810) and the Evolution keyboard. I would like to route the
incomming midi to csound, but later also to either Muse or Rosegarden4.
Is that a matter of having the softsynth or sequencer read from
/dev/midi00 (or somthing like that)? And do I simply tell the sound
generating software to direct its output to the appropriate device, say
/dev/audio?
Possibly under /proc/asound, but this is a 2.4.X model. I've not used 2.6
yet.
3) I noticed somethiing jack showing up. Is jack supported? If so, to
what extend?
man jackd I think.
4) What would be a nice program use for figuring out what midi-events
the knobs on the Evolution sends?
Don't know. I hope we get an answer! Certainly Rosegarden should be able to
record and show you MIDI events if MIDI is working.
- Mark
13 Aug
13 Aug
5:26 a.m.
At 07:58 AM 13/08/2003, Mark wrote:
Pure-Data (PD) is able to do this. i have just purchaced an Evolution
UC33, and that is what I used to determine what it sends, even though the
controllers are reprogrammable.
Regards
Luke
----------------
Luke Yelavich
AudioSlack Founder and main package maintainer
Audio software packaged for the Slackware Linux Distribution
http://www.audioslack.com
luke(a)audioslack.com
4) What would
be a nice program use for figuring out what midi-events
the knobs on the Evolution sends?
Don't know. I hope we get an answer! Certainly Rosegarden should be able to
record and show you MIDI events if MIDI is working. 
6:45 a.m.
Hallo,
Atte André Jensen hat gesagt: // Atte André Jensen wrote:
1) I didn't do any configuration of ALSA. Is that
needed? If so how do I
do it now that ALSA is compiled in?
I think, that ALSA normally still builds as modules. It depends on
your setup, but I would build modules. Then you just configure it like
old alsa, but I think the file locations have changed in 2.6, i.e. no
/etc/modules.conf anymore. It should be explained in modules.txt or
such in the Documentation folder. Sorry for this vague info, but I'm
still running a 2.4 kernel.
2) Where can I expect my devices to show up? For now I
have an onboard
soundcard (i810) and the Evolution keyboard. I would like to route the
incomming midi to csound, but later also to either Muse or Rosegarden4.
Is that a matter of having the softsynth or sequencer read from
/dev/midi00 (or somthing like that)? And do I simply tell the sound
generating software to direct its output to the appropriate device, say
/dev/audio?
Software that uses the ALSA sequencer (RG4, MusE) should need no
further tools, but for software, that uses raw-midi devices (Ardour,
Csound) you need a virmidi-device and route with aconnect. See the
Midi-Howto or the Softsynth-Sequencer-Quicktoot for that.
4) What would be a nice program use for figuring out
what midi-events
the knobs on the Evolution sends?
As mentioned, Pd does this. YOu don't even need to learn Pd: Just open
the "Test audio and midi" help file from the Pd menu.
ciao
--
Frank Barknecht _ ______footils.org__
7 a.m.
Atte André Jensen wrote:
I just installed kernel 2.6.0-test3 on my laptop. I
looked around in
/proc and saw all kinds of promissing things showing up there.
/var/log/messages even showed my Evolution USB keyboard. Very nice. But
since I'm fairly new to the kernel2.6.0/build-in-ALSA I'm hoping for
some pointers just to get started.
1) I didn't do any configuration of ALSA. Is that needed? If so how do I
do it now that ALSA is compiled in?
The only difference between 2.2/2.4 and 2.6 is that you don't need to
compile/install the alsa-driver package.
You still need some entries in modules.conf and to install the
alsa-lib and alsa-utils packages. These things are exactly the same as
in 2.2/2.4, so you probably already have them. If not, have a look at
the ALSA website.
Your modules.conf entries would look somewhat like this:
options snd cards_limit=2
alias snd-card-0 snd-intel8x0
options snd-intel8x0 index=0
alias snd-card-1 snd-usb-audio
options snd-usb-audio index=1
# maybe third entry if the mainboard has a MIDI/game port
# OSS emulation entries omitted
It may be possible that your hotplug scripts try to load the OSS
driver (usb-midi) for the keyboard. In this case, add usb-midi to the
/etc/hotplug/blacklist file.
2) Where can I expect my devices to show up? For now I
have an onboard
soundcard (i810) and the Evolution keyboard. I would like to route the
incomming midi to csound, but later also to either Muse or Rosegarden4.
Is that a matter of having the softsynth or sequencer read from
/dev/midi00 (or somthing like that)? And do I simply tell the sound
generating software to direct its output to the appropriate device, say
/dev/audio?
These device files are used for OSS emulation only. ALSA devices are
accessed through the ALSA library.
Audio devices have names like "hw:0,0" or "plughw:0,0" (the numbers
are card and device numbers). For a list of devices, run "aplay -l" or
"arecord -l".
MIDI sequencer ports have names like "72:0" (client and port number).
For a list of ports, run "aconnect -io".
3) I noticed somethiing jack showing up.
This is probably the usb-midi driver. These messages tell you about
the presence of MIDI jacks, and aren't related to the Jack Audio
Connection Kit.
Is jack supported? If so, to what extend?
Yes. Just like in other kernel versions.
HTH
Clemens
7778
days inactive
7779
days old
linux-audio-user@lists.linuxaudio.org
4 comments
5 participants
participants (5)
-
Atte André Jensen -
Clemens Ladisch -
Frank Barknecht -
Luke Yelavich -
Mark Knecht