Internal Controllers

[Perfect Human Interface]

There's a module only in the FL version of Flowstone for creating an "internal controller" in FL; that is, you can send a value out to control or automate other automatable parameters in FL. So if I made an LFO in Flowstone and linked that to an Internal Controller module I could then automate any control in FL with that LFO.

Since there's no corresponding module for other DAWs, I'm wondering how other DAWs handle this sort of thing and how I can create a controller plugin that works in these DAWs. I've only ever used FL so I don't know anything about how other software handles internal controllers. Do they use MIDI messages as I suspect?

I'm not about to go buying other DAW softwares so any insight is greatly appreciated. Thanks.

[Perfect Human Interface]

Anyone have anything to share about this?

[Jay]

generally it is done with midi cc. but the daw would have to support FS! how would you get flowstone working within another daw enviroment? the FS in FL studio is specially adapted to work within FL hence the tailor made modules,

or

if you are talking about making a plugin that controls certain elements of a daw then it would need to be done as midi i think, but then again i think that you would need the daw to support internal routing of midi from plugins to its features!

hmmm its a good question! ive done a plugin that allowed you to assign hardware controllers (midi cc) to under the hood features on the likes of REFX Nexus so sending midi from plugin to plugin works, and i know all daws support midi hardware control from external devices but i have never heard of any software that provides automation to the daw!

hmmmmmmmmmm im away to stroke my chin vigorously over this!

i will have to go fire up FL studio and have a look as ive not used it for a while!

[Perfect Human Interface]

how would you get flowstone working within another daw enviroment?

By using VST version of Flowstone or exporting Flowstone project to VST format. But yes, I would like to know how other DAWs handle these kinds of automation controls so I know how to proceed with this.

[Perfect Human Interface]

Going to give this older topic a bump since it's still relevant. Does anyone know how other DAWs may handle MIDI routing from effect plugins to other places (controls) in the DAW, or if they do at all?

[tulamide]

Controlling the DAW from within a VST plugin is out of the scope of the VST spec. What you can do however is altering incoming midi data or even create additional midi data and send it to the host. As soon as the data leaves the plugin it's the host who deals with it.

[Perfect Human Interface]

As soon as the data leaves the plugin it's the host who deals with it.

Yes, but that's what I'm asking. I don't use other DAWs so I have no idea how/if other DAWs may be able to handle that. Speaking of MIDI automation of course.

[tulamide]

Yes, but that's what I'm asking. I don't use other DAWs so I have no idea how/if other DAWs may be able to handle that. Speaking of MIDI automation of course.

Now you're confusing me. The thread seemed to start with the question if a plugin can control a DAW (like for example it's track volume automation, or something). That is not possible. With no DAW at all (when we're talking of VST). You can only have your VST plugin react to midi controls coming from the DAW (which you already know). The only way to control a DAW (to a certain degree) is by using Rewire and control it from another DAW.

So, no, midi automation controlled by a plugin to let the DAW do things isn't possible.

[Perfect Human Interface]

I don't buy that it's impossible in the sense that it can't be done... Plugins can output MIDI and there's no reason why a DAW can't access this MIDI and use it to control anything, just like it can do so with other MIDI sources. It's a very simple concept.

Now, if there are no DAWs that can do this currently, then yeah that's what I'd like to know. If so that's pretty dumb, but maybe I'm spoiled by FL Studio.