Is Studio 1 the only realistic alternative to Cubase ?

[LeVzi]

So if VST2.4 is dropped completely , how will this effect VST3 supported plugins that use the VST2.4 .dll's

I've tried to delete the VST2 of some plugins and when I load the VST3 "equivalent" the plugin doesn't load.

That's some kind of wrapper at work, so why can't that work ?

Hm... can't be really. Otherwise you wouldn't be able to install just the VST3 version of those plugins.

Try uninstalling everything, and then just install the VST3.

Even if they were wrapped (I have no idea, and I don't care what's going on in the background), I haven't seen yet that the DLL files have to be present when the VST3 is installed.

Tone2 synths, I deleted the VST2 and the VST3 didn't work. Markus said the VST3 uses parts from the VST2 or something along those lines, but you cannot not install one without the other.

[chk071]

Hm... that's bad. I can't remember that I have a single plugin which doesn't let me choose whether I want to install the VST2 or the VST3.

No wonder that he could do the VST3 so quickly, if he just uses the VST2, and wraps that into the VST3.

[LeVzi]

Hm... that's bad. I can't remember that I have a single plugin which doesn't let me choose whether I want to install the VST2 or the VST3.

No wonder that he could do the VST3 so quickly, if he just uses the VST2, and wraps that into the VST3.

But that's brilliant if that's what is happening. Solves all the problems.

[LeVzi]

No. Its Ableton Live suite 11.

this

It most definitely is not.

[chk071]

Hm... that's bad. I can't remember that I have a single plugin which doesn't let me choose whether I want to install the VST2 or the VST3.

No wonder that he could do the VST3 so quickly, if he just uses the VST2, and wraps that into the VST3.

But that's brilliant if that's what is happening. Solves all the problems.

Wrapping always needs more CPU cycles, plus you will always end up with more disk space for both versions needed as well. It's not very elegant, compared to native development.

[LeVzi]

Hm... that's bad. I can't remember that I have a single plugin which doesn't let me choose whether I want to install the VST2 or the VST3.

No wonder that he could do the VST3 so quickly, if he just uses the VST2, and wraps that into the VST3.

But that's brilliant if that's what is happening. Solves all the problems.

Wrapping always needs more CPU cycles, plus you will always end up with more disk space for both versions needed as well. It's not very elegant, compared to native development.

Yes true, but it would solve the issue.

[chk071]

Obviously, that's what some developers do. Although I haven't really seen it anywhere else that way.

I could be wrong though, as I always install VST2 and VST3, and wouldn't even notice if there are both when you only install VST3.

[pdxindy]

CLAP isn't really a thing yet to talk about whether it survives or not, it's an idea at this point.

just FYI... the latest More Feedback Machine (MFM2.5) from u-he already comes with a CLAP version. So it is a bit more than just an idea.

[pdxindy]

Wrapping always needs more CPU cycles, plus you will always end up with more disk space for both versions needed as well. It's not very elegant, compared to native development.

The great majority of VST3 plugins today are wrapped. Very few Devs are doing native VST3 development.

[machinesworking]

CLAP isn't really a thing yet to talk about whether it survives or not, it's an idea at this point.

just FYI... the latest More Feedback Machine (MFM2.5) from u-he already comes with a CLAP version. So it is a bit more than just an idea.

Yeah I'm aware, I've owned MFM since is was AU only and nagware! but in terms of the conversation at hand, CLAP is untested, not a standard (yet), and isn't relevant beyond acknowledging that it's existence is partially due to VST3 being problematic for developers and it's ownership by Steinberg can be a pain for host programmers to essentially reverse engineer.

AU came from Apple acknowledging that there were multiple issues with the VST standard in 2001 on OS9, porting a Windows VST to Mac OS ended up all too often with a buggy port. Some of this is due to the layers of abstraction here: Windows developer ports VST plug in, Mac user attempts using it in Logic and it's a buggy mess in Logic what with Emagics own struggle to host VST, which of course wasn't half as documented as how to make a VST in the first place.... So one line of graphics code specific to Windows left in a plug in could make a buggy mess in Logic.

[machinesworking]

I don't want to move, but the impending shift from VST2 to 3 only worries me i'll lose a lot of essential plugins.

Hey LeVzi, wouldn't Patchwork solve this issue for you? Host your VST2 plug ins, inside Patchwork and whatever Cubase does, you're good until some major change in Windows kills VST2. Blue Cat do have sales every once in a while, so wait for one and grab it, and continue to use Cubase.

https://www.bluecataudio.com/Products/P ... PatchWork/

[EnGee]

I don't want to move, but the impending shift from VST2 to 3 only worries me i'll lose a lot of essential plugins.

Hey LeVzi, wouldn't Patchwork solve this issue for you? Host your VST2 plug ins, inside Patchwork and whatever Cubase does, you're good until some major change in Windows kills VST2. Blue Cat do have sales every once in a while, so wait for one and grab it, and continue to use Cubase.

https://www.bluecataudio.com/Products/P ... PatchWork/

This is a good solution but expensive a little bit. Aren't there a cheap wrapper? Oh, what about FL Studio VST? Can it be used as wrapper? The OP said he already has FL Studio (me too!).

For me I think from the only VST2 I have are from Sugar Bytes. I'm waiting for VST3 versions and also waiting for Rob Papen's plugs to be implemented correctly in VST3 (They don't acknowledge the GUI problem I have in Cubase!), otherwise, I will sell any software won't upgrade to VST3! Lazy developers won't have my money

[jamcat]

Wrapping always needs more CPU cycles, plus you will always end up with more disk space for both versions needed as well. It's not very elegant, compared to native development.

The great majority of VST3 plugins today are wrapped. Very few Devs are doing native VST3 development.

Where did you get that information from? Care to share your source? It sounds like more unqualified nonsense from the uninformed anti-VST goon squad. Don't fall for it. What they lack in sense they make up for in zealotry.

The fact is it’s not uncommon for developers to create a pure processor and/or resource module that gets called by separate small-footprint plugin interfaces for each plugin format. That has been a standard practice for decades by majors such as Waves and IK Multimedia. But I can assure you, the VST3 components are “native VST3” and not low-rent amateur hack jobs. That is going to be the case amongst all the respectable development houses.

BTW, Waves has been supporting VST3 since 2009, and IK has since 2014. You won't hear representatives from either company whining about it being too hard to do it properly.

[LeVzi]

I don't want to move, but the impending shift from VST2 to 3 only worries me i'll lose a lot of essential plugins.

Hey LeVzi, wouldn't Patchwork solve this issue for you? Host your VST2 plug ins, inside Patchwork and whatever Cubase does, you're good until some major change in Windows kills VST2. Blue Cat do have sales every once in a while, so wait for one and grab it, and continue to use Cubase.

https://www.bluecataudio.com/Products/P ... PatchWork/

If that solved the problem in a stable way, then yeah i'd be down for that. I hadn't heard of it tbh.

[machinesworking]

If that solved the problem in a stable way, then yeah i'd be down for that. I hadn't heard of it tbh.

To be fair, that's not the only VST and VST3 host out there, there's quite a few:

New Sonic Arts Freestyle - https://www.newsonicarts.com/html/freestyle.php

PluginGuru Unify- https://www.pluginguru.com/products/unify-standard/

There's probably more out there I don't know about, but those three have been on my radar anyway.
All three are good companies.