Subscribe in a reader Follow me

VSTForx

Modular Freedom

VSTForx is a full-modular effect network creation tool which comes as a VST-plugin. With VSTForx you are able to load any number of VST-plugins and connect them anyway you want.

Additional modules allow you to manipulate such signal chains and offer a whole new way in mixing and producing.

Plugin chain example
Parameter network example

Advanced Controls

Build complex controler chains by creating parameter networks composed of arbitrary plugin parameters. With special audio-transformer modules it’s possible to control parameters with audio events.



Available Features



Basic Features

  • Free Plugin Chaining

    Unlike many other plugin chainers you are able to build effect chains similar to "real" circuits. With that you have more control on how your sound is created.

  • Free Parameter Binding

    Every effect and every module is controlled by parameters. All of these parameters have a knob representation which can be placed and controlled on the main "circuit" view. With the knobs you are able to bind parameters together, so that every parameter changing will be transmitted to its neighbours.

  • Connection Operators

    are modificators for parameter value transmissions. Available operators are Inverse, Logarithmic, Exponential, Multiplier, Min/Max and Offset.



Internal Modules

Besides the plugins VSTForx knows three types of modules: the signal processor, the signal switch and the signal transformer.


  • Input/Output Switches

    are able to switch between several states while every state belongs to an input or output. An "Input Switch" for example can switch several inputs to one output. A "selector" parameter controls the switch state. Furthermore several parameters control the "fade-in / fade-out" behaveiour.

  • Input/Output Step Switches

    Unlike the "I/O Switches" the "Step Switch" state is not controlled by a parameter. The states will be iterated automatically. Either with a fixed time per state or synced to the beat of your DAW.

  • The ADSR Trigger

    generates an ADSR sequence triggered by an audio signal. This sequence will be transformed into an output parameter value. Thus it's possible to control parameters (or rather the connected units) with any audio input.

  • Remote Channel

    offers (system wide) signal communication between VSTForx instances. So it's possible to send an audio stream from a VSTForx instance in Ableton Live to a VSTForx instance loaded in Cubase. Just as it works for audio data, it's possible to transmit parameter values.

  • VSTForx further modules

    Further Modules

    Volume, Pan, Peaktracker, MIDI Receiver

  • Script module symbol

    Script Modules

    give you the opportunity to write user specific modules in the - easy to learn - Lua language. Lua is fast enough to implement own signal processors or sound generators. Furthermore you can write scripts to manage the view and its elements.

Planned Features



Modules / Features

Multiple IO's icon

Multiple I/O's: At the present VSTForx has only one stereo input and one stereo output. Future versions of VSTForx are able to add arbitrary inputs and outputs.

Physics icon

Physics Contoller: Consider the Physics Controller as a physics driven sandbox environment. Every object and it's physical values can be bound to an output parameter value.

64-bit support symbol

64-bit support: A 64-bit version of VSTForx would be able to load 32-bit and 64-bit plugins.


VST3 Logo

VST3 Support: Future versions of VSTForx will support VST3 plugins.

Audio Unit icon

AU Support: with AU-support it is possible to load AU-plugins in VSTForx as well as loading VSTForx as an AU plugin. Of course this feature is only available for the Mac version of VSTForx.




User Interface

Zoom icon

Zoom In/Out: thanks to the new vector oriented GUI, future versions of VSTForx will have a seamless zoom-in and zoom-out function.

Undo/Redo icon

Undo/Redo: VSTForx will support undo and redo in the future.

Stepeditor icon

Editor for Step modules: Create complex rhythm patterns for the Step Modules with a convenient "Piano Roll"-like editor.




OS Support

VSTForx is available for Windows and Mac.

Comments   

+3 #33 Rainer 2015-04-10 09:18
Tried and just bought 'the forx'.

Cool plugin, good job.

The only feature request I'd have is a menu entry for "add plugin" and "add internal" from the right-click menu in the scene. They could directly jump to the respective directory in the scene browser.
Quote
0 #32 Douglas 2015-03-24 05:53
Putting the lua files in the top level of the VSTplugins folder has allowed the plugin to load.
If I play a midi note on, the event gets detected (see first line) then a lot of nonsense events and finally the with "lshift" error.

PS is the dropbox hosted screengrab visible to you?
(maybe direct email communication will work better...)
Quote
0 #31 Samba Godschynski 2015-03-23 20:01
Quoting Douglas:
Thanks for responding!
I've placed the attached files in the lua_plugins folder with the others. I did a scan from the Setup Dialog. The midiHelper.lua "failed" and the testMidiHelper.lua "succeed" as expected.
The testMidiHelper does not appear in the browser with the other lua plugins, however. when I use "Find Plugins" ->"midi" the testMidiHelper shows up on the list of results and can be added to the workspace.
When I open the plugins editor I see the following (paraphrased):
[ERROR]loading script failed:VSTpathVSTForx/scripts/lua_plugins/midiHelper.lua:1: module 'midiHelper' not found:
no field package.preload['midiHelper']
...
a series of "no file" lines looking for midiHelper.lua, midiHelper.dll and other files in various paths relating to the DAW host


That sounds all really weird. The "scripts/lua_pl ugins/" folder is actually more an internal folder for internal lua plugins than for custom ones. You can move the both lua files into your regular vst plugin folder and perform a rescan. Does this work? The error in your post means that the midiHelper was not found. It should be in the same folder as the plugin "lua" file.
Quote
0 #30 Douglas 2015-03-22 23:20
Thanks for responding!
I've placed the attached files in the lua_plugins folder with the others. I did a scan from the Setup Dialog. The midiHelper.lua "failed" and the testMidiHelper. lua "succeed" as expected.
The testMidiHelper does not appear in the browser with the other lua plugins, however. when I use "Find Plugins" ->"midi" the testMidiHelper shows up on the list of results and can be added to the workspace.
When I open the plugins editor I see the following (paraphrased):
[ERROR]loading script failed:VSTpathVSTForx/scripts /lua_plugins/mi diHelper.lua:1: module 'midiHelper' not found:
no field package.preload['midiHelper']
...
a series of "no file" lines looking for midiHelper.lua, midiHelper.dll and other files in various paths relating to the DAW host
Quote
0 #29 Samba Godschynski 2015-03-22 12:29
Quoting Douglas:

...
Is midi messages input to an instance of VSTForx broadcast to all plugins hosted within it?
...
Is midi messages sent from a lua plugin with SendMIDI() broadcast to all plugins hosted within the same instance of VSTForx?
...
It follows that using the midi config channel property of a plugin we can set the plugin to hear only that channel?

to all of your questions: yes its working exactly as you described.
I wrote a litte Midi helper class to make the processing a bit easier:
http://dl.vstforx.de/midiHelper.zip

a simple sample lua test plugin is included.
Please note: I didn't had enough time to test it so if you find some issues please let me know.
I'am considering to include this helper into one of the next releases.
Quote
0 #28 Douglas 2015-03-22 09:54
A few words in the manual about how midi works in VSTForx would be helpful.
So I have some questions: Is midi messages input to an instance of VSTForx broadcast to all plugins hosted within it?
Is midi messages sent from a lua plugin with SendMIDI() broadcast to all plugins hosted within the same instance of VSTForx?
It follows that using the midi config channel property of a plugin we can set the plugin to hear only that channel?
I'm sorry if these questions are a little obvious but I'm trying to understand how to workaround the inability to route midi messages with a line in the way audio signal paths are defined in VSTForx. Might it one day be implemented thus?
Quote
0 #27 Samba Godschynski 2015-03-16 10:12
Quoting Douglas:

It's a very useful, unique project and I'm now a proud licencee!

Hey ... good to hear
Quote
0 #26 Samba Godschynski 2015-03-16 09:52
Quoting Douglas:

It seems to me that the api documentation is incomplete. It does not document lcProcessMidi.

You are right. I will fixing that (also with an example) in the next days.
Quote
0 #25 Douglas 2015-03-16 05:30
Quoting Samba Godschynski:

A repository would be great, but there are currently not that much scripts to reposit. If you make progress with some of you MIDI scripts, feel free to send me some lines.
.


Thanks for reply! Splitting into channels would be fine. It seems to me that the api documentation is incomplete. It does not document lcProcessMidi. I'm assuming this callback is triggered when a midi event comes along. Would you be able to provide the simplest of skeleton lua plugin that simply translates the channel of incoming note and CC events to another channel? I would use this as a starting point for my own plugin. I'll donate the code I write to your project (I'm new to Lua, however). It would be nice to see many more example plugins distributed with VSTForx. It's a very useful, unique project and I'm now a proud licencee!
Thanks again.
Quote
0 #24 Samba Godschynski 2015-03-13 11:52
Quoting Doug:
Great Project!
I'm wondering if there is a repository of Lua plugins as VSTForx only has 4 example Lua plugins.
In particular I'd like to do MIDI processing. The first use I have is to create keyboard splits (i.e take midi notes and output to different connectors based on the note range). Actually what I really want to do is scale the velocities at the boundaries (which typically overlap) so that the output streams crossfade across the midi key range. Are you familiar with Ableton Live 9 Instrument racks? This is why I want to make my own lua plugin. If you should decide to create a native module that does this it would be even more awesome!
Thanks

A repository would be great, but there are currently not that much scripts to reposit. If you make progress with some of you MIDI scripts, feel free to send me some lines.

To your MIDI splitter: VSTForx unfortunately dosen't support MIDI routing. The only way you can approach such things is to seperate on the MIDI channels.
Quote

Add comment


Security code
Refresh