Automation subfolders in DAW
-
Would be really nice to be able to use folders / sub menus in the automation menu for our plugins... as below

-
D dannytaurus referenced this topic on
-
@DanH Digging this back up as would be a lovely addition going forward @Christoph-Hart

Too many vsts have a chaotic automation list.
-
Did we ever get a solution for this?
And to reiterate @dannytaurus's question, what is
automationIDused for? (should be writtenautomationIdbtw...)https://forum.hise.audio/topic/10568/automation-parameter-grouping
-
@ustk said in Automation subfolders in DAW:
should be written automationId
That lowercase
dstill gets me LITERALLY EVERY TIME
-
@ustk yeah this should work. You have to define the automation groups in the script. Will send over example when back at computer
-
@DanH Oh ok so script is the way! Checking this right now...
-
var PluginParameterGroupNames = ["Sampler", "Synth", "etc"]; -
@DanH Oh nice! I just got back home so we're in sync!
So I did this
const var groups = ["EQ", "Input Stage", "Noise", "Exciter", "Output Tube", "Transformer", "Macros", "Envelopes", "LFOs"]; uph.setPluginParameterGroupNames(groups);But how do I set the groups to the different components?
I created the parameter object:
const var IS_TYPE_MACRO = 0; const var IS_TYPE_CUSTOM = 1; const var IS_TYPE_COMPONENT = 2; const var obj = { "Low Boost": {type: IS_TYPE_COMPONENT, parameterIndex: 0, typeIndex: 0, group: groups[0], name: "Low Boost"}, "Low Freq": {type: IS_TYPE_COMPONENT, parameterIndex: 1, typeIndex: 1, group: groups[0], name: "Low Freq"}, "Low Cut": {type: IS_TYPE_COMPONENT, parameterIndex: 2, typeIndex: 2, group: groups[0], name: "Low Cut"}, "Hi Bandwidth": {type: IS_TYPE_COMPONENT, parameterIndex: 3, typeIndex: 3, group: groups[0], name: "Hi Bandwidth"}, "Hi Boost Freq": {type: IS_TYPE_COMPONENT, parameterIndex: 4, typeIndex: 4, group: groups[0], name: "Hi Boost Freq"}, "Hi Boost": {type: IS_TYPE_COMPONENT, parameterIndex: 5, typeIndex: 5, group: groups[0], name: "Hi Boost"}, "Hi Cut": {type: IS_TYPE_COMPONENT, parameterIndex: 6, typeIndex: 6, group: groups[0], name: "Hi Cut"}, "Hi Cut Freq": {type: IS_TYPE_COMPONENT, parameterIndex: 7, typeIndex: 7, group: groups[0], name: "Hi Cut Freq"}, "Bypass": {type: IS_TYPE_COMPONENT, parameterIndex: 8, typeIndex: 8, group: groups[0], name: "Bypass"}, "Heat": {type: IS_TYPE_COMPONENT, parameterIndex: 9, typeIndex: 9, group: groups[1], name: "Heat"}, "Bias": {type: IS_TYPE_COMPONENT, parameterIndex: 10, typeIndex: 10, group: groups[1], name: "Bias"}, "Dynamic": {type: IS_TYPE_COMPONENT, parameterIndex: 11, typeIndex: 11, group: groups[2], name: "Dynamic"}, "Hold": {type: IS_TYPE_COMPONENT, parameterIndex: 12, typeIndex: 12, group: groups[2], name: "Hold"}, "Static": {type: IS_TYPE_COMPONENT, parameterIndex: 13, typeIndex: 13, group: groups[2], name: "Static"}, "Mix": {type: IS_TYPE_COMPONENT, parameterIndex: 14, typeIndex: 14, group: groups[2], name: "Mix"} };But then I don't know what to do with this
uph.setPluginParameterSortFunction(function(p1, p2) { return -1; // instant crash return 1; // instant crash return undefined; // doesn't crash });how do I pass
obj?
I guess just returning-1should assign the parameter in natural order but it's just crashing instantlyIt's like a crucial step is missing in the doc and there's not even a single entry with those methods in the whole forum...
-
@DanH Holy sh... They are just appearing in the property editor! No need for the sort function if, well, no sorting is needed lol

still it's weird it's crashing but at least I got something...