If you have a problem or need to report a bug please email :

There are 3 sections to this support area:

DOWNLOADS: access to product manuals, support files and drivers

HELP & INFORMATION: tutorials and example files for learning or finding pre-made modules for your projects

USER FORUMS: meet with other users and exchange ideas, you can also get help and assistance here


For general discussion related FlowStone


Postby ChrisHooker » Wed Apr 04, 2018 4:47 am

I guess I don't really understand the purpose of having multiple knobs if they are always set to the same value. Why not just have only one knob in that case?

If you're looking for a linkable solution, such as RJ described, I've attached an example I worked up. You can add as many knobs to the system as you like, and link/unlink at whim. The knobs can start out at different values, then link and move proportionally. If a knob in the group hits 0 or 1, it does not prevent the others from continuing their sweep. Boundaries will be limited to 0-1 on the outputs, but relationships (beyond boundaries and back again) are maintained until MouseUp. Once the mouse button is lifted up, the knob will be set to that boundary, and subsequent movements back into range will begin immediately. I'm not sure how that will play with automation (I have not tried it yet).
Linkable Knobs - working on automation.fsm
Created in
(196.56 KiB) Downloaded 556 times
Last edited by ChrisHooker on Fri Apr 06, 2018 5:30 am, edited 1 time in total.
Posts: 54
Joined: Tue Jul 13, 2010 10:02 pm


Postby RJHollins » Wed Apr 04, 2018 5:13 am

Very interesting solution ChrisHooker !

Works quite nice. Thanks for posting and sharing.

Posts: 1457
Joined: Thu Mar 08, 2012 7:58 pm


Postby Spogg » Wed Apr 04, 2018 7:36 am

Very nice implementation Chris!


User avatar
Posts: 2710
Joined: Thu Nov 20, 2014 4:24 pm
Location: Birmingham, England


Postby BobF » Wed Apr 04, 2018 10:25 pm

Hello Chris,

Thanks for posting this, very cool.

Hope to see more from you in the future!

Cheers, BobF.....
Posts: 593
Joined: Mon Apr 20, 2015 9:54 pm


Postby ChrisHooker » Thu Apr 05, 2018 12:12 am

Thanks guys.
Unfortunately, testing the automation reveals some issues. I tested by connecting a knob/oscillator in place of the "Set" wireless connection inside the Knob Control, and it gives unexpected results. The automation will not cause an offset in any linked knobs (just the one being automated); clicking link off/on after automating can cause jumps; you can't overwrite the automation by manually moving the control... I'm a bit lost with all that. /Or tired... or both.
If someone is willing to do some improvements, have at it!
Posts: 54
Joined: Tue Jul 13, 2010 10:02 pm


Postby ChrisHooker » Fri Apr 06, 2018 5:56 am

Leaving things half-completed bugs the heck outta me...
I revised the file above with the following changes:

-Fixed a glaring mistake on the knob output (was not supplying correct value due to trigger blockers).

-Fixed the jumping value issue when linking/unlinking.

-Fixed(?) automation to allow manual usage to override playback automation. I've actually never played around with automation testing in SynthMaker/Flowstone, so I don't know how it SHOULD look, but when feeding the knobs oscillating values in place of automation from the Preset's "Set" connection, and then trying to manually override by dragging the knob with the mouse, it would result in a very glitchy knob. Now the manual movements SHOULD completely override the automation. Perhaps in a host, the Parameter primitive would take care of this automatically, but I don't know.

I have not yet figured out how to get automation in one knob to affect a linked knob proportionally. Currently, automation only affects the knob that the automation was written to, whether linked or not while reading the automation. (If linked while writing automation, then all linked knobs should also write their own automation, and thus each would play back their own individual automations as well.) The gist of this: you currently can't for example draw automation in your host as a smooth ramp for one knob and have all the linked knobs automatically follow as well. I will try to fix this, but not tonight.

-I've also made even more spaghetti inside the knob (sorry).
Posts: 54
Joined: Tue Jul 13, 2010 10:02 pm


Postby ChrisHooker » Fri Apr 06, 2018 12:10 pm

On second thought...
What would happen if two knobs were linked and each write automation... if automation on any one (linked) knob affected relative levels of any knobs linked to it, each would cause an additional offset in the other, adding to each own's automation. ...Or perhaps if using a last changed primitive, the automation and offset would fight each other.

...I think it may be best to leave automation un-linked. ...Thoughts?
Posts: 54
Joined: Tue Jul 13, 2010 10:02 pm


Postby Duckett » Fri Aug 16, 2019 2:41 pm

Just wanted to say many thanks to Chris Hooker for this .fsm- wish I had any answers/insights about automation... I'll bash away at it and report back.
We have to train ourselves so that we can improvise on anything... a bird, a sock, a fuming beaker! This, too, can be music. Anything can be music. -Biff Debris
User avatar
Posts: 76
Joined: Mon Dec 14, 2015 12:39 am


Postby trogluddite » Fri Aug 16, 2019 3:57 pm

ChrisHooker wrote:...I think it may be best to leave automation un-linked. ...Thoughts?

After a few attempts in the past at building linked controls, I came to pretty much the same conclusion.

As soon as you introduce VST automation, you face the problem of automation for different controls 'fighting' each other, or having to very carefully manage which controls you enable automation recording for in the DAW. It can even lead to the linked controls updating each other in an infinite loop if you're not careful! Due to rounding errors in calculations, even using 'changed' primitives doesn't help much.

It will work if the schematic builder or user decides on one of the controls to be a 'master', and only records automation data for that one, but this makes it a bit opaque what the automation represents and means that you then can't tweak the automation independently for each control when you need to.

In the end, I decided that linking should be a GUI feature only, with each control recording independent automation data, and the controls unlinked for automation playback. I'm sure that's not the only solution, but it seemed to me the only one which works in a way that's intuitive for people who are used to how VST automation usually works.
All schematics/modules I post are free for all to use - but a credit is always polite!
Don't stagnate, mutate to create!
User avatar
Posts: 1645
Joined: Fri Oct 22, 2010 12:46 am
Location: Yorkshire, UK


Return to General

Who is online

Users browsing this forum: No registered users and 32 guests