On 23/09/2011 19:56, William Zwicky wrote:
> I'd also like to remove synths from the Preferences page.  You should pick
> synth(s) when creating libraries and scenes.
>
how does this fit in with the auto-scan process - do you anticipate
doing an autoscan every time you create a library? This doesn't seem
desirable to me cos autoscan is a bit slow, even if we get autoscan
working in parallel across all ports. And not all synths support
autoscan anyway, so you do anticipate displaying the list of all
supported synths and choosing one?

At the moment I find it a bit of a pain when creating a new patch that I
always have to choose the synth then choose the sub-type of patch e.g.
bank or single. If patches already exist within a library and the
library is locked to one synth, then this should reduce that point of
friction as we already know what kind of patch we would be creating
which will be a nice benefit of locking libraries to synths. And while
we might be creating loads of patches for a synth, we shouldn't be
creating new libraries THAT often. So I could tolerate friction when
creating a library more than the current friction when creating a
patch.  Still, if you have to navigate a big list of synths every time
you create a library it might get annoying.

Maybe there could be an autodetect scheme whereby you create a new
library, then you have the option of either playing a note or moving a
controller on the synth you want to use it for, then JSL detects the
port and does an autoscan and hopefully only gets one response. However
not all synths have keyboards or controller knobs so this would be
flawed I guess...

just some thoughts,
frankie

------------------------------------------------------------------------------
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

Reply via email to