Suggestion for Jitterbox

@milford59

I discussed this with John, who pointed out that Unify's GUI doesn't scale well to lots of small plug-ins in a row, so at least for now we'll keep a single plug-in, and even add more functions to it (e.g. jittering MIDI note velocity).

Your point is well taken, but a better solution will probably be to modify JitterBox's own GUI so you only see the parts you're using.

@getdunne

Thanks for your quick reply - I am really enjoying learning about the functionality.

I hadn't realised the GUI could be an issue, having seen 3 Midi Filters in a row in e.g. "Sound like Mozart"... 

Here is an example where I would have 3 Midiboxes and I would jitter Time, Pitch and Midi Velocity for each Midibox separately.

How would I do that if all 3 jitter functions are in the same plug-in ?

Posted by: @milford59

How would I do that if all 3 jitter functions are in the same plug-in ?

Use three instances of JitterBox, and only activate the function(s) you want in each one.

Posted by: @getdunne

Posted by: @milford59

How would I do that if all 3 jitter functions are in the same plug-in ?

Use three instances of JitterBox, and only activate the function(s) you want in each one.

Thanks for your reply.

So..... although you said earlier "Unify's GUI doesn't scale well to lots of small plug-ins in a row, so at least for now we'll keep a single plug-in, and even add more functions to it (e.g. jittering MIDI note velocity)."  what you seem to be implying is there is actually no GUI restriction on the number of instances of Jitterbox, but the user will have to access all current and future "jitters" through a single plug-in and have no visual clue what he has jittered without opening the plug-in.

@milford59

I should clarify. There is no limit to the number of MIDI-insert plug-ins you can string together, but Unify's layer-stack GUI will not be able to show the full names of more than a few at a time. There are technical reasons why a single multi-function plug-in is preferable to multiple single-function plug-ins.

However, you raise a valid point: a little box showing only the name of a plug-in does not provide an adequate "visual cue" about why that particular plug-in is used in that particular place. There may be some value in allowing the text in each plug-in box to be edited arbitrarily, so the plug-in name is simply the default. This is something I've been considering for a future version of Unify.

@getdunne

That would be a good solution..... an additional feature could be a description box in the plug-in where the user would type some info and when you mouse-over the plugin on the GUI, it would display the description.  I will leave it with you - thanks for your responses.