How To Enable Automation in FS

[Perfect Human Interface]

Sorry to ask a very basic question, but I've searched quite a bit and can't seem to find any proper documentation, tutorials, or anything that simply lays out what the requirements for enabling automation control in FS plugins are.

What I have gathered is that you need "Preset Parameter" components to define the parameters that can be controlled, with "auto" set to true; your controls need to be in a 0-1 range; and you need a "preset manager" module in your schematic somewhere. That's all I know.

My knobs contain Preset Parameter's, with auto set to "true," and ranges that are scaled from 0-1. I've tried simply dropping a Preset Manager module into the top level and that didn't yield any results. I tried renaming the "preset names" in each of (3) knob objects to different things and no difference.

So if anyone wouldn't mind simply listing out for me explicitly what needs to take place before host automation is possible that would be great.

If it makes any difference I'm using FS in FL Studio (10.10 Beta)

[tester]

Preset parameter has 2 nodes: "can be automated" (set "1" or "true") and "send automation recording to host" (connect input value via toggle switch in order to update values). Check here:

viewtopic.php?f=2&t=1190&hilit=toggle&start=10#p3804

[Perfect Human Interface]

Preset parameter has 2 nodes: "can be automated" (set "1" or "true") and "send automation recording to host" (connect input value via toggle switch in order to update values).

Hi, thanks for the response. The "send automation recording to host" is wired to the Y drag component's "dragging" (bool) output (with a sample and hold component between).

[Perfect Human Interface]

Hate to be a bother but if anyone could make a simple list of the things that need to be in place that would be really helpful. Thanks!

[nix]

You have these things which neeed to be done->
1.preset manager on top level
2.unique name for preset parameter
3. auto = true
4. 0-1 range of value in preset parameter
5. a wireless input connected to 'p' terminal

What you may be missing is
6.preset =true

That's all I think.
Please let me know if u r still having trouble
All success

[Nubeat7]

yes dont forget the unique names - this were my problems at the beginning too...
because the host gets confused if there are similar presetparameternames

[Perfect Human Interface]

5. a wireless input connected to 'p' terminal

This was all I needed. Many thanks!

I should be good to go now, but one more question I had was concerning the naming of all the parameters. I read in an old SM tutorial that there was a way to make parameters inherit names from their parent modules, but it never explained how. Does anyone happen to know anything about this?

[nix]

Cool!8D

I quickly chopped out the system that SM used for naming presets under parent module names->

auto name presets.fsm

(461 Bytes) Downloaded 1107 times

Hope it helps

[Perfect Human Interface]

Ah, I see! Thanks a bundle!