Last idea for today.
Consider this scenario: You loaded an FX synth, and configured parameter ranges and control bus mappings for automation. Then you kept going in your project and added several automation envelopes.
Then you realized something needs to change in the synthdef. This isn't going to be a big change in the parameters, just tweak something internally.
PluginCollider (IIRC) keeps the synthdef in the serialized parameter stream that's saved with the project. So you can't just re-writeDefFile in SC. It's necessary to reload the synthdef from disk.
But when you do that, all of the parameter ranges and control bus mappings are gone. (I expected that the DAW might also erase automation envelopes. REAPER, at least, keeps the envelopes; I don't know about other DAWs.)
I think that, when loading a synthdef, it wouldn't be hard to match control names from the file with existing parameters in the plugin instance. I.e., if the synthdef has a mix parameter, and I set it to the range 0.0-1.0 and mapped it to a bus, then if I reload the synthdef with some DSP fixes, it should assume that mix in the new file being loaded is the same as mix that was already configured in the plugin, so that I don't have to set the range and remap by hand.
(E.g., to handle #62, I need to add a .clip for Q into my synthdef. The def has 10-15 parameters. Just to add the clip, I will have to reconfigure all of the parameters. If you consider a typical iterative process of developing a synthdef, and add 1-3 minutes to each iteration for reconfiguring ranges and mappings, that ends up being a potentially large time waster.)
Last idea for today.
Consider this scenario: You loaded an FX synth, and configured parameter ranges and control bus mappings for automation. Then you kept going in your project and added several automation envelopes.
Then you realized something needs to change in the synthdef. This isn't going to be a big change in the parameters, just tweak something internally.
PluginCollider (IIRC) keeps the synthdef in the serialized parameter stream that's saved with the project. So you can't just re-
writeDefFilein SC. It's necessary to reload the synthdef from disk.But when you do that, all of the parameter ranges and control bus mappings are gone. (I expected that the DAW might also erase automation envelopes. REAPER, at least, keeps the envelopes; I don't know about other DAWs.)
I think that, when loading a synthdef, it wouldn't be hard to match control names from the file with existing parameters in the plugin instance. I.e., if the synthdef has a
mixparameter, and I set it to the range 0.0-1.0 and mapped it to a bus, then if I reload the synthdef with some DSP fixes, it should assume thatmixin the new file being loaded is the same asmixthat was already configured in the plugin, so that I don't have to set the range and remap by hand.(E.g., to handle #62, I need to add a
.clipfor Q into my synthdef. The def has 10-15 parameters. Just to add theclip, I will have to reconfigure all of the parameters. If you consider a typical iterative process of developing a synthdef, and add 1-3 minutes to each iteration for reconfiguring ranges and mappings, that ends up being a potentially large time waster.)