Hi

I have two ideas that could improve jsynthlib.

One, easier to do is implementing randomization of patches. It would be 
not much work, as we already have all parameter ranges for patches where 
there are PatchEditors present. There could be two options - randomize 
all parameters, or only parameters designated by programmer (because 
some parameters should not be randomized). I think it would be great 
editing patches starting from some weird sounds and polish them to be 
"listenable" ;-) I have such option in my Waldotf MicroQ and I think it 
would be great to have this on any of my synths :-) What do you think? 
Could it be implemented as a part of ongoing code refactoring?

Second idea is more complicated and to be honest I have no idea how to 
realize it :-D But It would be great to be able to translate patches 
between synths, at least to some extent.

Let's assume that we have synth A with a filter where we can edit cutoff 
freq from say 100 Hz (midi hex value 0x00) to 1000 Hz (0xFF) and synth B 
wih filter cutoff from 10 Hz (0x00) to 500 Hz (0x7F).

So 0x28 would be 200 Hz on synth A, and on synth B it would be 0x17 and 
we could translate patches this way. Of course 10Hz (0x00) on B couldn't 
be translated to A, and we would be forced to use 50 Hz. And there is 
also a problem with FM and Wavetable synths, but idea is tempting, isn't 
it? ;->


cheers
Maciek

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Jsynthlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel

Reply via email to