HI Robert! 11.01.2015 20:44, Robert Jonsson wrote: > Hi Andrew, > > 2015-01-11 16:27 GMT+01:00 Andrew Deryabin <[email protected]>: >> [Resending this, as no confirmation from sf.net after 15 minutes] >> >> Hi Robert, >> 11.01.2015 18:22, Robert Jonsson wrote: >>> Hi Andrew, >>> >>> short question, is there a way to store LV2 presets? >>> If not, is it possible to add? Seems few of the synths have their own >>> preset store functionality, I guess that means they rely on the host >>> to do it. >> Yes, it's possible. These presets are just <control=value> pairs, so storing >> them will not be so hard to implement. > Cool > >> But one question - should stored >> presets be available to all projects or only to those they were saved from? > They should be available all the time. > The point of creating presets, for me, is to store a setting that you > like, so you can reuse it later in another song, or even make a preset > pack and release publicly. I like this idea! :) > > Implementation wise I think creating a structure under > ~/.config/MusE/plugin/preset/ with user defined presets would be a way > to do it. > We already do similar things with scripts etc. Ok, I'll make it. Now I have a clear way to implement it :). >>> And also, wouldn't it make sense to somehow merge this with the patch >>> selection from the midi channel even though it's not exactly the same >>> thing? >>> I haven't thought it through but it feels wierd to have very similar >>> things on two places whereas one feels more standardized. >> I thought about this and I likely to merge them, but static presets can't be >> automated, though they may be selected and restored on song load.May be >> there should be a submenu in program select menu with name "Static Presets" >> or so? > Not sure I follow why they shouldn't be automatable, could you give an > example?
The main difference between programs and presets is that programs have bank/program numbers and can be selected via midi messages, but presets have no such information, so we must select them by hand. But.. If we choose own program numbering for these presets, say 16384 + n, then they can also be automated (if future plugin updates will not add new presets in the middle of the list, for example) > >> P.S. Offtopic: I want to make jack cpu meter as additional toolbar, and want >> to ask - is there any interest in this, or it's only my wish? > I think that would give good feedback so I'm all for! Ok! My dream about cpu usage info is to make it like in chromium browser - so we can view how much each plugin/synth is eating in %% and time. But implementation of this should be made very accurately to use minimum cpu time for calculations. cpu usage toolbar will be the start point :). > I sometimes ponder adding a view that would store all the output > normally printed in the console also. > Not the least with info about jack xruns, which we don't even report > through MusE now. This also would be good, but if there will be lots of debug messages we should make memory limits for the history of the console. Regards, Andrew > > Regards, > Robert ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
