Re: [LAU] FluidSynth fails to sintetize more 85% events generated by Drum machine ALESIS D4.

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <linux-audio-user@...>
Date: Friday, September 11, 2009 - 8:56 am

This is a multi-part message in MIME format.
--------------050100010605060109050704
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

>> In your case you will need to configure a program to filter the

In Puredata it might be as easy as using the stripnote object which
trips note-offs (zero velocity) from incoming midi.

Kind regards,
Lorenzo.

--------------050100010605060109050704
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

In your case you will need to configure a program to filter the
events out before they get to fluidsynth.   I've never done this kind
of filtering so I don't know which software to recommend, but
assuming such a real-time midi filter exists, it should be possible
to create a chain by connecting the alsa ports of the various
applications together correctly and make this all work.

Ken

Might be an overkill, but I'm quite sure pd (puredata) and sc
(supercollider) can easily do that - I wouldn't know the details though
(I just know how to do basic things with these two)

Renato

In Puredata it might be as easy as using the stripnote object which
trips note-offs (zero velocity) from incoming midi.

Kind regards,
Lorenzo.

--------------050100010605060109050704--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [LAU] FluidSynth fails to sintetize more 85% events gene..., Lorenzo, (Fri Sep 11, 8:56 am)