Support and discussion for all of Akai’s modern standalone MPCs including the MPC X / X SE, MPC Live 1, 2 & 3, MPC One / One+, MPC Key 37/61.
User avatar
By BostonGreen Tue Jul 12, 2022 12:54 pm
Starting to notice a lot of plugin manufacturers are only offering vst3 an no vst2 version.......

Is their a wrapper for pc?

I hope akai bring vst3 support soon.
User avatar
By Monotremata Tue Jul 12, 2022 2:30 pm
Steinberg discontinued and stopped supporting VST2 ages ago. They stopped selling licenses for it quite awhile ago too which is why new devs cant make them. Unless you're an OG that bought your license years ago, you can only get a VST3 license now. 10 years ago Steinberg told everyone to start moving on which is why they're finally turning VST2 off in Cubase once and for all.
By SakisX Tue Jul 12, 2022 5:29 pm
MPC-Tutor wrote:Is it particularly challenging to support VST3? I would have assumed not as that's in no one's interest to make it hard to implement, but I guess there must be something causing an issue. Isn't Reason also still missing VST3 support?


Mostly due to new license required for commercial usage of VST3
The future is CLAP format and (surprisingly) many companies where interested , it's open source and can also be used commercially without a license and without the need to share the code
Hopefully Akai will get in touch with the devs , also CLAP offers better audio performance (besides other features)

An interesting video that also explains the licenses
User avatar
By Monotremata Tue Jul 12, 2022 5:55 pm
I dont get how CLAP has been out for less than a month and everyone is already evangelizing it as 'THE FUTURE OMG'.. So far the ONLY host that supports it is BigWig, a niche product for folks that didnt like Ableton Live, and theres what like 10 plugins in CLAP format so far MAYBE? When Logic Pro, Pro Tools, and Cubase all support it, then we'll call it 'the future'. Good luck getting any one of them to do it.

@Tutor - from the sound of the whole VST2-VST3 discussion it sounds like the anti-VST3 devs have gotten along this far with weird hacks and workarounds in VST2 and now when confronted with properly coding in VST3, they get mad and claim its a bunch of crap instead of learning how to do it by the actual spec. Its been an interesting development to follow as a Cubase user. A lot of plugs have been VST3 for ages now, and the holdouts seem to be either the lazy folks like Native Instruments, or the small time guys that dont want to part with any of their profit to pay for a VST3 license.
Last edited by Monotremata on Tue Jul 12, 2022 6:30 pm, edited 1 time in total.
By Trensharo Tue Jul 12, 2022 6:08 pm
CLAP won't do anything but further fragment the plug-in market. In addition to that, developers are locked into supporting at least:

AAX: Pro Tools & Media Composer
Audio Units: Logic Pro & Final Cut Pro
VST: Cubase, Nuendo & WaveLab

Neither of those three entities is likely to drop their own "internal standards" for CLAP. As a result, CLAP is nothing more than additional work everyone needs to do to support the plug-in format on DAWs that are already forced to support VST/AU due to years of no other viable alternatives.

The only other alternative was DirectX Plug-Ins and Virtual Instruments, and that is a Windows platform technology that got sidelined in favor of VST (but still supported by some Windows DAWs/NLEs).

Supporting CLAP for "reasons" makes sense only if it will allow you to invest less elsewhere, otherwise you are simply increasing developer workload.

That, or they will do the laziest port possible (the way some developers just use VST3 wrappers to port plug-ins over from VST2, so you don't even get any of the real benefits of VST3). That doesn't really benefit users - it's just a PR maneuver.

IMO, the way to stop VST from becoming such a monolith was by supporting platform native frameworks for A/V FX and Virtual Instruments and simply not opting into it when it was younger. I know it was first, but there was tons of time to avoid this. Developers should have simply moved to AU and DX when those were available, so that they were not beholden to a competitor (while being charged for that privilege).

It is way too late, at this point.
By SakisX Tue Jul 12, 2022 6:28 pm
Monotremata wrote:I dont get how CLAP has been out for less than a month and everyone is already evangelizing it as 'THE FUTURE OMG'.. So far the ONLY host that supports it is BigWig, a niche product for folks that didnt like Ableton Live, and theres what like 10 plugins in CLAP format so far MAYBE? When Logic Pro, Pro Tools, and Cubase all support it, then we'll call it 'the future'. Good luck getting any one of them to do it.


Because of this unexpected interest :
Following companies and projects are already evaluating CLAP for their host and plug-in software:

Arturia: https://www.arturia.com/ Link
Avid: https://www.avid.com/ Link
BespokeSynth: https://www.bespokesynth.com/ Link
cableguys: https://cableguys.com/ Link
Cockos: https://www.reaper.fm/ Link
Cytomic: https://cytomic.com/ Link
DMGAudio: https://dmgaudio.com/ Link
Epic Games (Unreal Engine): https://www.unrealengine.com/ Link
Expressive E: https://www.expressivee.com/ Link
FabFilter: https://www.fabfilter.com/ Link
Image-Line: https://www.image-line.com/ Link
iPlug2 framework: https://iplug2.github.io/ Link
LHI Audio: https://lhiaudio.com/ Link
Node Audio (Entonal Studio): https://entonal.studio/ Link
Oddsound: https://oddsound.com/ Link
Presonus: https://www.presonus.com/ Link
Plogue: https://plogue.com/ Link
Qtractor: https://qtractor.org/ Link
Togu Audioline: https://tal-software.com/ Link
ValhallaDSP: https://valhalladsp.com/ Link
VCV: https://vcvrack.com/ Link
Vital Audio: https://vital.audio/ Link
Xfer Records: https://xferrecords.com/ Link


Forget Cubase , it will be the last host supporting it

PS. Bitwig isn't Live alternative , especially with the latest updates it has different approach (mostly modular sound design)
Last edited by SakisX on Tue Jul 12, 2022 6:39 pm, edited 1 time in total.
User avatar
By Monotremata Tue Jul 12, 2022 6:34 pm
"Evaluating" doesn't mean anything, and again, doubt Avid is going to do it. Otherwise ProTools would've opened up to support either VST2/3 or the OS standard Audio Units a decade ago.
By SakisX Tue Jul 12, 2022 6:39 pm
Monotremata wrote:"Evaluating" doesn't mean anything, and again, doubt Avid is going to do it. Otherwise ProTools would've opened up to support either VST2/3 or the OS standard Audio Units a decade ago.


CLAP is the future :smoker: