Set order of parameters as listed for automation

[dannytaurus]

@ustk Make sure to check the AU version if you use the LEGACY setting. According to Claude, it will set all params IDs to 0 and therefore only one param (or none of them) will survive to show in the DAW as automatable.

Interested to hear what you find out.

[dannytaurus]

@ustk

I'll stay out of this added brain-shuffling beast

I don't blame you!

[ustk]

@dannytaurus Yeah I tested successfully AU and AAX (not VST3 yet but it should be good)

I'll keep your idea in mind though because it seems very interesting.
In fact, it might be doable to add this as a layer in Hise so it's transparent to us @Christoph-Hart ?

[dannytaurus]

@ustk I've been looking at the automation params of some other synths, that are exposed in the DAW and really, they're all over the place. Nothing consistent at all.

That's why I don't think it's worth all this effort.

Although it might be nice to be one of the few plugins that has sensible and predictable automation params.

[ustk]

@dannytaurus said in Set order of parameters as listed for automation:

That's why I don't think it's worth all this effort.

That might be precisely where we can add value

[dannytaurus]

@ustk Agreed. I look at these jumbled lists of hundreds of automation params and wonder how anyone bothers with automation. It must be so confusing wading through it all, just to find that ONE param you want to automate.

[ustk]

@dannytaurus If others are like me, you record automation while turning the knobs, and show the recorded lanes... This way you don't spend your time scrolling like crasy

[dannytaurus]

@ustk True, true.

[dannytaurus]

These are my test results to far.

Forcing the order by manipulating the IDs to produce specific hashes gets:

1. Correct ordering for AU in Ableton Live and Reaper (but those users likely use VST3 anyway), and
2. Correct group ordering in Logic Pro, although params in the group are still alphabetical

VST3 always shows in the component tree order either way, except in Cubase, which shows the param groups in the wrong order, but the params inside the groups in the correct order. WTF.

Conclusion - probably not worth the effort, but since the work is already done, I'll use it.

[ustk]

@dannytaurus Good job detective!
I agree to the WTF, seems that developing new protocols of all sorts but there's still no agreement whatsoever in the way DAWs handle such a simple task... Shame...