Re: [yoshimi-user] modular yoshimi
- From: "Alessandro Preziosi (licnep)" <lsnpreziosi@xxxxxxxxx>
- To: Dominic Sacré <dominic.sacre@xxxxxx>
- Date: Tue, 5 Apr 2011 00:32:40 +0200
For now, I'd prefer a midi learn function.
sure, if some of you guys haven't seen it yet, check out the midilearn
branch i'm working on:
https://github.com/licnep/yoshimi/wiki/How-to
Actually this thing came to my mind as a CONSEQUENCE to the greater
abstraction of parameters that we should have once the midi learn is
up and running. I understand what many are saying, that with
midi-learn, everything can be done with external programs. but I'm
asking myself wheter it would be better to have it all in yoshimi,
internally.
Think about yoshimi effects, for example. One could argue that it's
'overkill' to have effects built-in when you could use external ladspa
plugins, but i think it's great becase some effects are actually PART
of an instrument, it would be stupid to have them in an external
program, because if you change midi channels you have to re-route
everything, saves are not automatically in synch, and it's
hard/impossible to share the instrument as a whole (effect
included)...
Also, don't underestimate the necessary changes under the hood...
once the midi learn is set up, it shouldn't need too much code. Coding
modular stuff generally needs very little code compared to the
possibilities it opens, my biggest concern is the UI, I have no idea
how one would go about doing it with fltk, i think the ui is
definately what would take most time coding.
LV2
It seems various people are be interested in a yoshimi port to LV2, i
never used lv2 plugins and don't really know what the advantages would
be/how hard it would be to make a port..
anyway for now i will concentrate on the midi-learn thing, bye everybody
Al
Other related posts: