VCV Host: What's In Your Host Module?

Following what already said from @ablaut and @PaulPiko, I managed to screencast both solutions. Here some thoughts about that.

Use case 1: jBridge
I registered jBridge quite some time ago (but I rarely use it anymore, since I began to use Reaper which has great embedded bridging features). jBridge is a nice tool but can fail to bridge some older plugins, and can be more buggy. If I remember correctly, issues may arise with plugins compiled with older versions of SynthEdit. In my case, I get an autohost process error while resetting the VCV Host module (TS-808 is an instrument plugin, not an effect plugin) and after closing Rack.

VCVRack+TS-808-vst+jBridge

Use case 2: VST host/chainer
In my case this solution it’s more stable, no issues, but the workflow is a little trickier. The more well-known plugin chainer seems to be Blue Cat’s PatchWork (quoted above in the thread). Personally I began to use Metaplugin from DDMF (it’s a little cheaper) to wrap VSTs in ProTools, and it makes a good work for my needs. With VCVRack it worked well, too. Also, it preserved the possibility to load the program presets of the TS-808 (that got lost with the “jBridged” version of the plugin).

VCVRack+TS-808-vst+metaplugin

That’s all, but please, don’t take these as tips for shopping. It’s just my experience!

EDIT: added the external links to both video on my Google Drive.

4 Likes