VST 3 plugins support dynamically changing various things that are fixed in VST 2. The next big hurdle is going to be handling various restart requests from the plugins. More progress! The three points from the previous post are basically done and things seem to be working well. I believe all their products can be demo’d, so try it before you drop a dime, and see what you think. There are many other possibilities with this plug I will not rant about. The BC12-string sim, when tweaked, is amazing, and I use it live in a couple of Byrds tunes. I am in awe of the newest TH-U sims (compared to TH3), so I decided to use BC Re-Guitar in front of my chain to use modeled pickups, into TH-U. I am now using BC Axiom and Destructor for some live guitar work. I started using the BC free amp sims, and they are as good as any on the market. Since the arrival of VST3 plugs, I used it to load them into C3, and it is flawless. When I finally incorporated it into C3, I was pleasantly surprised at the stability. Just the mixing abilities alone was worth what I paid. Yes, there is the expense, but I’ve used Patchwork for several years now, and I don’t regret the purchase. C3 handles it very well, no glitches at all. It has been perfectly stable, and the CPU load is basically unnoticeable before adding any plugs.

So I’m going to set VST 3 work aside for bit, take a look at adding support for different preset models and then return here once Cantabile is better equipped to handle VST 3’s preset handling.įrom my experience, there is no downside.

This also crosses paths another an idea I had for lightweight presets where just the automation parameters are captured in each preset. This however could cause problems with slow loading plugins and plugins where the preset model actually works as expected. One idea I had was to simply make all VST 3 plugins use pseudo presets (ie: a custom bank of presets where each is preset is a snap shot of the entire plugin state). In Cantabile however where the user might want to switch presets on a state by state basis the behaviour of presets needs to be more deterministic.

Different approaches by different plugins, different things supported by hosts, different models declared as possible by the SDK and associated docs.įor most DAWs this isn’t too big a deal… the plugin is configured by the user and that’s it. The more I look at it, the more I realize that the preset management in VST 3 is a totally mixed bag.

Cubase 5 vst 3