On 11/01/2014 11:10 PM, Ted Felix wrote: > a composition's studio on a device by device basis. My idea just moves > the Bank and Program checkboxes into the device file/bank editor. For > the most common use cases, this is no change, just a simplification.
The only way I can see to move responsibility for picking the bank/variation to the studio is to restructure the entire thing into a flat list where each unit contains information about how to get there. Unit 42 "Explosion" (program: Noises variation: Explosion) I say "unit" because we can't call this a "program" or an "instrument" and we'd have to coin a suitable name for such a construct. It would provide a recipe for how to produce a given sound, through whatever combination of things each sound required. It's probably possible to assemble this new structure out of existing traditional data, and then users could just pick from a flat list from 0 to n units, without worrying about what controls to twiddle to get each one to sound. There are some tasty things about the idea, but I have serious concerns about obfuscating the logical grouping of sounds, and probably encountering conflicts where the same name is used in multiple contexts, and it's impossible to distinguish one from the other without knowing its full "address" in the scheme of things. I'm not loving the idea. Why do you perceive a problem here that is in need of a solution? -- D. Michael McIntyre ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
