KV331 Audio

kv331 · Post by **kv331** » Tue Mar 01, 2011 12:04 pm

hi guys,

As you know we have thousands of parameter in SynthMaster. Just waay too much.
So, for instance when you want to automate a parameter, you see thousands of parameters in a long long list and you're lost instantly.

As a solution to this, I thought of limiting the automateable parameter to just the easy parameters. There are 8 easy parameters, and on top of that I can add 2 XY pads, so this makes 12 parameters in total which will be reported to the host.

The downside is, you can not automate dicrete parameters, or parameters not linked to easy parameters.

What do you think on this decision? Should I go for it?

Caco · Post by **Caco** » Tue Mar 01, 2011 12:08 pm

How about you leave them all in but organise them so that the easy parameters come first in the host's parameter list so are easy to find? Could provide the best of both worlds, simple way to find the easy parameters but the others are there if required

djsubject · Post by **djsubject** » Tue Mar 01, 2011 12:23 pm

kv331 wrote:hi guys,

As you know we have thousands of parameter in SynthMaster. Just waay too much.
So, for instance when you want to automate a parameter, you see thousands of parameters in a long long list and you're lost instantly.

As a solution to this, I thought of limiting the automateable parameter to just the easy parameters. There are 8 easy parameters, and on top of that I can add 2 XY pads, so this makes 12 parameters in total which will be reported to the host.

The downside is, you can not automate dicrete parameters, or parameters not linked to easy parameters.

What do you think on this decision? Should I go for it?

i don't think removing the individual host parameters is a good move!!

most hosts have a learn function so its not like your looking through a list to find it you just move the parameter on the gui

i like the current way that i can automate all parts from the host

in Reaper i have a midi controller mapped to "last touched plugin parameter" so i just move SM2's filter & its automaticly mapped ready to record host automation

Subz

kx.001 · Post by **kx.001** » Tue Mar 01, 2011 12:55 pm

leave it with as much automation as possible.

kv331 · Post by **kv331** » Tue Mar 01, 2011 1:34 pm

Caco wrote:How about you leave them all in but organise them so that the easy parameters come first in the host's parameter list so are easy to find? Could provide the best of both worlds, simple way to find the easy parameters but the others are there if required

This actually makes a LOT of sense! I might go as this option, as well as "categorizing" parameters. I think VST standard allows categorization of parameters.

EDIT: This is initially what I'm gonna do (in the next build)

i.e. moving easy parameters to the first 8, and then autoassigning easy settings for presets that dont have any easy parameters mapped.

djsubject · Post by **djsubject** » Tue Mar 01, 2011 1:39 pm

kv331 wrote:
Caco wrote:How about you leave them all in but organise them so that the easy parameters come first in the host's parameter list so are easy to find? Could provide the best of both worlds, simple way to find the easy parameters but the others are there if required
This actually makes a LOT of sense! I might go as this option, as well as "categorizing" parameters. I think VST standard allows categorization of parameters.

EDIT: This is initially what I'm gonna do (in the next build)
i.e. moving easy parameters to the first 8, and then autoassigning easy settings for presets that dont have any easy parameters mapped.

this sounds exciting!!

best of both worlds also as the easy 8 will be simple to find for anyone using a host that dose not have a learn function

& auto mapping easy 8 sounds useful!

interested in seeing its first implementation in the next beta

Subz

kv331 · Post by **kv331** » Tue Mar 01, 2011 2:00 pm

djsubject wrote: best of both worlds also as the easy 8 will be simple to find for anyone using a host that dose not have a learn function

& auto mapping easy 8 sounds useful!

interested in seeing its first implementation in the next beta

Subz

All my purpose is to increase workflow&usability

So here are my plans to achieve this purpose:

1) Easy parameters will be moved to the first 8 parameters in the parameters list, so for hosts like Kore, they'll show up instantly.

2) Easy parameters' MIDI CC assignments will be saved "globally". Doesnt make sense to save them per preset. Once a user assigns them to his MIDI controllers's sliders/knobs, he's done.

3) Easy parameters will be "automatically" assigned for presets that didnt use them at all. I'll try to come up with a "useful" autoassign algorithm.

4) Users will be able to save/load easy parameter assignment settings.

5) To browser presets faster: I'll make it possible to assign MIDI controllers to go to Next/Previous presets. This way you can assign buttons on your controller to browser presets. Does that make sense?

djsubject · Post by **djsubject** » Tue Mar 01, 2011 3:08 pm

1) Nice! good move!!

2) best way to do it IMO also

3) Nice! i look forward to playing with it!

4) now this sounds really interesting!!

5) Excellent Idea!! (i wish all plugin developers did this!!)

5.1) yes it all makes perfect sense!

kv331 · Post by **kv331** » Tue Mar 01, 2011 3:18 pm

djsubject wrote:
5) Excellent Idea!! (i wish all plugin developers did this!!)

5.1) yes it all makes perfect sense!

In addition to 5, 5.1:

I'm planning to let users assign a certaion MIDI CC (probably between 101-119), and CC values for "preset browser" management, such as you assign CC100 for user interface control, and CC values for:

CC#100, value 0 = Previous preset in the current preset list
CC#100, value 8 = Next preset in the current preset list
CC#100, value 16 = Previous Instrument category
CC#100, value 24 = Next Instrument category
CC#100, value 32 = Previous Style category
CC#100, value 40 = Next Style category
CC#100, value 48 = Previous Author category
CC#100, value 56 = Next Author category
CC#100, value 64 = Previous bank category (will be very useful after expansions)
CC#100, value 72 = Next bank category (will be very useful after expansions)

So by using a single CC#, we can assign different user interface functions based on the CC value.

djsubject · Post by **djsubject** » Tue Mar 01, 2011 8:02 pm

guess i know what's going to be preset #2 on my Korg nano controller now!!!

kv331 · Post by **kv331** » Tue Mar 01, 2011 9:04 pm

djsubject wrote:guess i know what's going to be preset #2 on my Korg nano controller now!!!

Cool!

Does it have "buttons" on it?

djsubject · Post by **djsubject** » Wed Mar 02, 2011 12:41 am

kv331 wrote:
djsubject wrote:guess i know what's going to be preset #2 on my Korg nano controller now!!!

Cool! Does it have "buttons" on it?

kv331 · Post by **kv331** » Wed Mar 02, 2011 5:49 am

Looks great! So you can assign MIDI CCs to the buttons, and turn the controller into SynthMaster controller

kv331 · Post by **kv331** » Wed Mar 02, 2011 8:18 am

I think I'm also going to implement MIDI Out functionality so that when a new preset is loaded, the plugin sends out MIDI CC to set controllers.

djsubject · Post by **djsubject** » Wed Mar 02, 2011 10:37 am

kv331 wrote:Looks great! So you can assign MIDI CCs to the buttons, and turn the controller into SynthMaster controller

Yes

I think I'm also going to implement MIDI Out functionality so that when a new preset is loaded, the plugin sends out MIDI CC to set controllers.

this may be over kill! & could cause errors with vst's that follow SM2 in the chain, if you do add it maybe make it optional?

Subz

KV331 Audio

KVR Audio

Need feedback: improving "usability"/live usage. Let's hear opinions!