17 Sep
2007
17 Sep
'07
6:42 p.m.
Hi,
I just got a toy (at least it's been called that before) Millenium MD70 for my
kid. Anyway its just about right for my 5 year old kid. It had midi out so I
thought that I try it together with Hydrogen and Fluidsynth. One thing I
first noticed was that Fluidsynth just responded about half of the hits made
at the pads. Hydrogen responds ok but the velocity is low compared to what I
get when I just play the sound in Hydrogen. I was puzzled to why Fluidsynth
couldn't respond more than every second hit so I took amidi and dumped the
output. It turns out that the MD70 sends a "Program Change" every time I hit
a pad. In hex it is C9 00. Do anyone out there know why this happens? Or is
it normal to send a program change at every hit? I can't get Fluidsynth to
ignore the program change. Do anyone know if theres a way to do that? There
might be a midi filter somewhere (suggestions welcome) but I thought that it
would be nice to do it directly in Fluidsynth.
Here is an example of amidi -d when I hit one pad
C9 00
99 23 7F
99 23 00
As i interpret it (GM that is), it's:
Program change to 0
Note on for Acoustic Bass Drum with velocity 127
Note on for Acoustic Bass Drum with velocity 0
/bengan
18 Sep
18 Sep
5:55 a.m.
Bengt Gördén wrote:
I just got a toy (at least it's been called that
before) Millenium MD70 for my
kid. Anyway its just about right for my 5 year old kid. It had midi out so I
thought that I try it together with Hydrogen and Fluidsynth. One thing I
first noticed was that Fluidsynth just responded about half of the hits made
at the pads. Hydrogen responds ok but the velocity is low compared to what I
get when I just play the sound in Hydrogen. I was puzzled to why Fluidsynth
couldn't respond more than every second hit so I took amidi and dumped the
output. It turns out that the MD70 sends a "Program Change" every time I hit
a pad. In hex it is C9 00. Do anyone out there know why this happens? Or is
it normal to send a program change at every hit?
Probably just to make sure that the right program is selected.
I can't get Fluidsynth to ignore the program
change.
A program change shouldn't hurt.
Here is an example of amidi -d when I hit one pad
C9 00
99 23 7F
99 23 00
You could use aseqdump to have the computer interpret it.
As i interpret it (GM that is), it's:
Program change to 0
Note on for Acoustic Bass Drum with velocity 127
That's maximum velocity.
Note on for Acoustic Bass Drum with velocity 0
Velocity 0 actually means note off.
It's possible that fluidsynth cuts off the sound as soon as the note off
is received. Many GM synths ignore note off messages on the drum
channel. Probably you're using a sound font where the decay and release
times for drum sounds are different; try different ones.
Regards,
Clemens
6:52 a.m.
tisdag 18 september 2007 09:54 skrev Clemens Ladisch:
Yes. I followed some links and found out that it's normal to do that instead
of note off. Do you know if note off and note on velocity 0 behave
differently according to specs or is it just up to the implementation? I
can't find any readable MIDI-specs for that. Pointers would be appreciated.
You could use aseqdump to have the computer interpret
it.
Ok. Missed that one. Thanks.
That's maximum velocity.
Yes. I struck the pads a few times and just copied the last one.
Note on for
Acoustic Bass Drum with velocity 0
Velocity 0 actually means note off. It's possible that fluidsynth cuts off the sound
as soon as the note off
is received. Many GM synths ignore note off messages on the drum
channel. Probably you're using a sound font where the decay and release
times for drum sounds are different; try different ones.
Ok. I just switched sounds within the same SF. I'll give it another shot with
different SF. I also think I saw a SF-editor so I might fire that up and have
peek at the SF:s to see how they are build up. I really don't know much about
SF but now's the time to learn :-)
regards,
/bengan
7:45 a.m.
On Tue, 2007-09-18 at 10:50 +0200, Bengt Gördén wrote:
Yes. I followed some links and found out that it's
normal to do that
instead
of note off. Do you know if note off and note on velocity 0 behave
differently according to specs or is it just up to the implementation?
I
can't find any readable MIDI-specs for that. Pointers would be
appreciated.
I like:
http://www.borg.com/~jglatt/tech/midispec.htm
or you could go to the source, but you have to pay :-(
http://www.midi.org/about-midi/specshome.shtml
Keith.
8:27 a.m.
tisdag 18 september 2007 11:45 skrev Keith Sharp:
On Tue, 2007-09-18 at 10:50 +0200, Bengt Gördén
wrote:
Thanks. I'll take this one :-)
mvh,
/bengan
Yes. I followed some links and found out that
it's normal to do that
instead
of note off. Do you know if note off and note on velocity 0 behave
differently according to specs or is it just up to the implementation?
I
can't find any readable MIDI-specs for that. Pointers would be
appreciated.
I like:
http://www.borg.com/~jglatt/tech/midispec.htm
11:58 a.m.
Bengt Gördén wrote:
tisdag 18 september 2007 09:54 skrev Clemens Ladisch:
Yes. I followed some links and found out that it's normal to do that instead
of note off. Do you know if note off and note on velocity 0 behave
differently according to specs or is it just up to the implementation?
Note-on with velocity zero should use a default release velocity (64),
but the vast majority of devices just ignores release velocity anyway,
so there isn't any difference.
The special case of velocity zero was intended to allow for running
status when sending consecutive note-on and -off messages, but it seems
your device doesn't use running status; with running status, the bytes
sent would have been C9 00 99 23 7F 23 00.
Regards,
Clemens
Note on
for Acoustic Bass Drum with velocity 0
Velocity 0 actually means note off. 
7:38 a.m.
Hi,
Am Montag, 17. September 2007 schrieb Bengt Gördén:
I was puzzled to why
Fluidsynth couldn't respond more than every second hit so I took amidi and
dumped the output. It turns out that the MD70 sends a "Program Change"
every time I hit a pad. In hex it is C9 00. Do anyone out there know why
this happens? Or is it normal to send a program change at every hit?
I just stumbled across qmidiroute which does midi filtering with something
like regexp but built graphically.
I used it for filtering the volume-controller so it doesn't hit linuxsampler
but only jack-rack while everything else goes to linuxsampler. That way I
could control the wahwah with my volume-pedal and ls didn't change its
volume.
You would simply ignore all the program-changes...
Arnold
--
visit http://www.arnoldarts.de/
---
Hi, I am a .signature virus. Please copy me into your ~/.signature and send me
to all your contacts.
After a month or so log in as root and do a rm / -rf. Or ask your
administrator to do so...
8:27 a.m.
tisdag 18 september 2007 11:37 skrev Arnold Krille:
I just stumbled across qmidiroute which does midi
filtering with something
like regexp but built graphically.
I used it for filtering the volume-controller so it doesn't hit
linuxsampler but only jack-rack while everything else goes to linuxsampler.
That way I could control the wahwah with my volume-pedal and ls didn't
change its volume.
You would simply ignore all the program-changes...
Ah. Nice. Worth a shot. I'll get to it as fast as I'm at home again.
regards,
/bengan
6329
days inactive
6330
days old
linux-audio-user@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
Arnold Krille -
Bengt Gördén -
Clemens Ladisch -
Keith Sharp