That looks keen, but I'm having a hard time figuring out how to get pd to talk to my MIDI devices. $ pd -alsa -listdev reading startup file: /home/fugalh/.pdrc input devices: 1. Sound Fusion CS46xx (hardware) 2. Sound Fusion CS46xx (plug-in) 3. Keystation (hardware) 4. Keystation (plug-in) output devices: 1. Sound Fusion CS46xx (hardware) 2. Sound Fusion CS46xx (plug-in) 3. Keystation (hardware) 4. Keystation (plug-in) API number 1 no midi input devices found no midi output devices found couldn't open MIDI input device 0 couldn't open MIDI output device 0 opened 0 MIDI input device(s) and 0 MIDI output device(s). So it's seeing my keyboard as an audio device but not a midi device. Any ideas? On Sun, 26 Sep 2004 22:40:17 +0200, Frank Barknecht <fbar@xxxxxxxxxxx> wrote: > Hallo, > Mark Knecht hat gesagt: // Mark Knecht wrote: > > > On Sun, 2004-09-26 at 09:26, Hans Fugal wrote: > > > I play the organ, and would like to sequence some organ music in > > > rosegarden4. The only problem is that the organ doesn't care how hard > > > you hit the keys (MIDI note velocity), so what would be a fine organ > > > performance sounds really silly because of the different velocities. > > > > I might suggest that you consider recording the velocity information but > > then not use it. It won't hurt anythign to have it in the MIDI file. > > I agree here, but you need velocity info to detect noteon and noteoff, > but your organ synth probably should not care about the actual values > and instead play all notes as the same velocity. > > For filtering I always use Pd, as it's very flexible and quick to do > all kinds of filters. Attached is a little patch which replaces all > velocities > 0 with 127. This is just five objects connected, I would > never care to use or write a special program for this kind of stuff, > which is quick to hack in Pd, Python, or whatever your "scripting > language" of choice is. > > Ciao > -- > Frank Barknecht _ ______footils.org__ > > > > -- De gustibus non disputandum est.
