Options.txt. PluginAutoPopulateThreshold in 10.1?

[S4racen]

No Youtube Video/Tutorial - no tests from music websites....

https://www.youtube.com/watch?v=LTqmMPSw9Fw&t=6s

https://vimeo.com/showcase/5476346

Cheers
D

[Alfonx]

https://www.youtube.com/watch?v=LTqmMPSw9Fw&t=6s

https://vimeo.com/showcase/5476346

Cheers
D

Man - that's mad! Google and Youtube automatically changed my search to "predator 2".
Okay, thank's a lot!

[Alfonx]

Preditor 2 (https://isotonikstudios.com/product/pre ... g-utility/) is great for this but unfortunately heavily relied on pluginautopopulate.

Sorry - i am trying to understand this (because i am interested in this tool):
If Live doesn't autogenerate that mappings does it mean you can't map the parameters with preditor 2? Does it just work with "pluginautopopulate"...?

I thought you can always map the parameters of the vst by hand with preditor and save them and use this template in future. See:
https://www.youtube.com/watch?v=LTqmMPSw9Fw

Once you have a mapping - can't you just save the generated mappings in preditor 2 to avoid these problem?

Regards,
Alfonx

[scheffkoch]

...basically it only works when the vst exposes its parameters (which is done by the autopopulate command) so no parameters = no mapping, BUT you can define the parameters yourself „by hand“ and then save this vst configuration „as default“ (select plugin and right-click)...works perfect!...

[Alfonx]

Thank you very much for explaining.

Regards,
Alfonx

[emiel-r]

old thread, but still relevant.

You can manually select parameters you want, just once.

group the synth / effect

save it

it will appear in the same state when loaded in a new project.
You can ungroup it too if you need too

any other modern solutions to this problem? still room for improvement id say. but this works