Le 18/02/2014 16:41, Vesa a écrit : > On 02/18/2014 04:32 PM, Tres Finocchiaro wrote: >> >> We also can not improve the default values, as they are given by >> the plugins, and we don't have code to fix every single plugin. >> >> >> If we are at the mercy of the plugin developers for changing plugin >> defaults > > Why would we be? All of the LADSPA plugins are open source. Yes. Moreover changing the control ports description is not very difficult (the init function of the plugins is not very complicated, and the ports description is not too complicated too).
Moreover as many LADSPA plugins are not natively compatible with LMMS (they use other schemes than 1->1 or 2->2, or the don't have the appropriate naming scheme for input/output) I think it make sense to have a kind of control on the way they are "inside" :) For example the vocoder plugin I adapted was an existing one, but it can't work with LMMS. BTW LMMS tree includes a set of plugins that - I guess - were developped for LMMS or adapted for it. Regards, -- Y. > > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > > > > _______________________________________________ > LMMS-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/lmms-devel > ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
