On December 9, 2012 06:07:21 PM Tim E. Real wrote: > Long answer (grab a coffee): If you add a DSSI synth, you will notice that > the piano roll midi controller graphs DO list an entire series of available > midi controllers for the synth.
Yikes. I just did some testing on those 32NF* DSSI midi controller graphs and with some synths which have thousands of controls (FreeAlpha DSSI-VST) I noticed two things: 1) When I recently unified the 'Ctrl' popup menus, I made it waaay slower with these thousand-control synths because it now takes a long time to fill up the 'Add' sub-menu. (Clicking on 'Add' used to popup a separate new menu.) 2) The numbering scheme gets outta whack. I noticed the low param numbers go above 127 - like this: 32NF234. Proof that's wrong is when you try to edit that graph and it shows a completely different number like 32NF60. Maybe I forgot to logical AND the low param number with 0x7F... I will take a look. Also Dan I will try to add these controls for VST synths just to get you folks running, manually creating graphs. Thing is that the 32NF* numbers are arbitrary, no way for user to change them. So I'm studying the controller situation. Got some ideas might work quickly. Easiest would be to expand on my 'midi learn' dialog box adding a table, and this is how you would assign (create actually) new controllers available to be shown in the midi controller graphs. You would access the dialog from the 'Ctrl' menu as well as the 'Automation' column menus - which would really clean that whole mess up - thousands of controls gives too many audio automation menu items with those colour boxes and so on. More elegantly I've been aiming to add two new routing types: Midi control and audio control. Route anything anywhere - even say, raw audio data to midi control ports. Robert, this would allow us to route for example audio compressor control outputs to anywhere else, for which you recently expressed a desire. Alas I was hoping to unify audio and midi controllers first but hey, maybe I'll take just a pragmatic approach (we got streams - deal with 'em!) and support the two separate streams. Anyway after that, our much forgotten 'routing' dialog (in the mixer menus) needs a makeover to show all the routes. It's problem ATM is it uses TEXT items. We need to use class Route as the list items, NOT text. Because the class Route has trouble determining the Route type based solely on it's text name (other Routes might have the same text name but be different types.) Once we do that, we're free to list any route types confidently. And bring this routing dialog out of the shadows and more upfront. And give it Bezier curves and so on. I think the OOM team made their router a centerpiece. Makes sense, that and a mixer is where crucial stuff happens. Tim. ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
