Subscribe in a reader

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.

OS Support

VSTForx is available for Windows and Mac.

Comments   

0 #39 Levendis 2016-01-26 06:16
Quoting CT Blaze:
…TAL Bassline (the free one), do not show an input.
A few ther synths, like TyrellN6 or MiniBit, show an input.
What's going on here? HELP
---

Though i'm not on a 64bit system, and only tested the TAL Bassline, i'm unable to replicate your bug.
i'm able to access hosted plugin's audio inputs and outputs, even if there are multiples of those. i'm able to set MIDI channels per instrument using the parameter found in Modify Scene-->(VSTi)- ->midi config. The multi-outs of VSTForx also works as expected.
Here is a screenshot of those functions:
Quote
0 #38 CT Blaze 2016-01-25 21:13
I tried several plugins, Instruments and MIDI-Plugins (all 64bit).
Before I posted my first msg, I had just tried a few which would apparently not show an input.
MIDI plugs from CodeFN42 (e.g. Chordz) do not show an input, which is a shame because I need to exclusively route through those.
And many synths I tried, e.g. Massive, the Roland System-1 and Promars, xhip, Charlatan or the TAL Bassline (the free one), do not show an input.
A few ther synths, like TyrellN6 or MiniBit, show an input.
What's going on here? HELP
PS: I would pay at least double if this would all work...
---
Quote
0 #37 Samba Godschynski 2016-01-25 08:00
Quoting CT Blaze:
Johannes, I tried the latest DEMO of VSTForx for windows 64 bit.
I cannot see the entry points of items, therefore I cannot connect/route to test VSTForx. THe only connections I can make is from exit points of items to the main exit point.
I'm running Windows 10 with the latest updates and I tried in Reaper and Maschine (both lates versions). Any clue? THX

Which plugins did you try?
Quote
0 #36 CT Blaze 2016-01-24 21:28
Johannes, I tried the latest DEMO of VSTForx for windows 64 bit.
I cannot see the entry points of items, therefore I cannot connect/route to test VSTForx. THe only connections I can make is from exit points of items to the main exit point.
I'm running Windows 10 with the latest updates and I tried in Reaper and Maschine (both lates versions). Any clue? THX
Quote
0 #35 Levendis 2015-08-20 00:53
Quoting Levendis:
Unfortunately, i'm unable to make use of the host parameters.

Only true in FL Studio. Works fine in other DAWs.
Brilliant fun, this plugin!
Quote
0 #34 Levendis 2015-08-09 03:31
VSTForx offers very flexible utility!

Unfortunately, i'm unable to make use of the host parameters. Adjusting them while recording does yield automation data in my DAW. Playback, however, doesn't engage the respective parameter within VSTForx. In order to modulate parameters with DAW automation i have to use a MIDI Receive module.

Great plugin! i look forward to any future developments.

System: Win8.1, FL Studio 12.1
Quote
+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

Add comment


Security code
Refresh