Bug: Imported Rack presets do not connect Macro Parameters on load

[Robert Randolph]

Current Behaviour:

Loading a rack preset with Macro Parameters active does not allow you to use the Macro Parameters until you adjust the destination parameter knobs in the "Assignments" window.

Expected Behaviour:

Upon loading a rack preset, all modifiers should be active.

Steps to reproduce:

• Create a new empty rack
• Add a Volume and Pan plugin
• Create a Macro Parameter attached to Volume
• Test Macro Parameter to make sure it works
• Export Rack preset
• Import Rack preset

On import, the Macro Parameter does not work until you tweak the parameter knob in the parameter column.

Video:

[Robert Randolph]

I've been testing this further, and sometimes the imported Rack will crash Waveform as well.

I can't pin down when/why this happens.

[Robert Randolph]

I originally titled this with "Modifiers" instead of "Macro Parameters" because my brain is melted this morning...

However... Modifiers don't work on import either. I just learned this.

[Robert Randolph]

And here's 3 presets that crash Waveform on import for various reasons.

https://www.dropbox.com/sh/ojbtrcncdekk ... 5OiBa?dl=0

One is a generated (by a script I wrote) preset. One is using Modifiers, created entirely in Waveform. One is using Macro Parameters, created entirely in Waveform.

[Robert Randolph]

5 day bump (and my only bump).

[dRowAudio]

Thanks for the report, test cases and sorry for the delayed response.
I thought this would be simple to fix but it turns out the way the presets get applied using that button isn't really compatible with the new Macros and Modifiers. I'll see if I can improve this in the future as I've got some more work to do on Racks soon but for now I've made it fail with a warning about the incompatibility and a suggestion to add the preset as a new Rack. This should at least avoid the crash.

Thanks again,
Dave

[HansP]

What if you have a general compound ID system and a general Graph description system, where plugins, racks, modifiers, and free interconnection of automation curves with macros and modifiers or whatever are nothing special at all? Not even any invention of any new functional mix object should be special.
Then only some object methods (insert, delete, to/from clipboard, process audio w/reading automation, load settings, (re-)connect with controls like automation and modifiers) need to be refined, based on the context how the object is being used and mounted. Then a framework of growing options and versatility should be stable and viable.
humble 2 cents, so much is already there.

[dRowAudio]

That's kind of how it works already. It's just a complex system and changing only the internals of a Rack (explicitly Macros and Modifiers) from underneath the window just doesn't work I'm afraid.