On Sat, Sep 24, 2011 at 3:30 PM, Joe Emenaker <[email protected]> wrote:
> > One question though: What are your thoughts surrounding "Projects" being > the master context (ie, you can only have one open at a time, and it's > the thing that holds everything else)? My initial thought was that a > Studio would be better as the master context. So, you'd "Open a studio" > and that would have your synths for that studio layout and it would have > all of your patches for that studio layout. > > It seems reasonable to me that you could have different projects you're > doing with a single studio setup, so I'm not sure "Project" should be a > broader context than Studio. > In my mind, "studio" is just a collection of equipment, and "project" is the equipment plus everything required for a song or set. So it makes sense that a project would contain *a* studio plus some libraries, rather than a studio containing a project. -Bill Zwicky ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Jsynthlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
