Jump to content
Bad Mac

VST3 synths supported in Cakewalk?

Recommended Posts

As best I can tell from the three threads created by the OP, there are issues with 2 VST3 plug-ins: EZ Drummer 3 and Session Drummer 3.

This was compounded by the plug-in browser appearing to have VST3 plug-ins "greyed out" with icons that looked like they were disconnected suggesting the plug-ins were disabled.

Toontrack has already acknowledged issues with both plug-ins on their forum and the plug-in browser is properly displaying the plug-ins based on the active theme.

 

  • Like 1

Share this post


Link to post
Share on other sites

What's concerning is that they don't work on several DAWs. It's just not Cakewalk having the problem. I don't understand how this got by the testers.

Share this post


Link to post
Share on other sites

Either testers did not have the error (one user in this thread reported EZD3 runs OK) or

they did and failed to report it or

they reported the problem and Toontrack released the product anyway.

 

I am sure there is more than one bug on the to-do list for EZD3 and probably more than one bug that crashes the plug-in.

Chances are there are more bugs yet to be reported.

Share this post


Link to post
Share on other sites

Yes lots of unanswered question from the OP.    That ALL VST3's are crashing has never been actually verified even though it was a question asked by scook early on. Looking at the list it would seem Sample Tank, Syntronik and Iris2  would also be crashing? 

I also noticed the duplication of all VST3 and VST 2 instruments. The OP might want to check the boxes in Preferences to prevent this. 

848567611_browserpic.PNG.da781612e3e8029dcc0b66b0c86f54e8.png.2589a1d6d22ba06499a6e079aee5e841.png

 

275615288_Screenshot(408)_LI.jpg.40c55ca9ae9c219daf2fe35de8e19ea1.jpg

 

Share this post


Link to post
Share on other sites

Thinking about other info that might be related to issues. Here's some more things to chew on. In the OP signature they list their Audio interface. A quick trip to the Tascam support page finds we are dealing with a very obsolete device. We actually don't know if the OP is running W10. Do VST3's run on W7? I google the question and there was no immediate answers. 

672173164_Screenshot(410).png.26276ea2d6b888ab9c1ff6747d6045ce.png

 

 

Share this post


Link to post
Share on other sites

Re: The FW-1884:  While it cannot be ruled out as an issue on the OPs PC (regardless of whether or not any such issue might impact VST3s not working), I just want to add a few things as long as @John Vere raised it as a possible issue. On my system (recognizing all systems are different)

  • sometimes Windows doesn't see the driver (v1.80) at the start of the day until I reboot the FW-1884.  I suspect a few things things but on my system:
    • the only problem I have seen if I need to reboot is that the ASIO lines are not seen by Windows (and therefore software that replies on some of Windows' Sound Services).
    • on my system,  non-ASIO audio modes work until such time that I reboot the FW-1884 and Windows sees the ASIO lines.
  •  VST3s work as they should--even if I have not rebooted the FW-1884 to make sure Windows sees the ASIO driver properly

Let me be clear, blaming the FW-1884 for the OPs problem is premature. It might be problematic, but it is not necessarily problematic as concerns Cakewalk, VSTs, etc.  On my legacy 2011 era system Cakewalk works quite well.  And while I could push the PC beyond what its resources can handle, the PC, running Cakewalk with the FW-1884 can handle tens of hundreds of plug-ins -- probably not all at the same time, though. 

Edited by User 905133
fixed typos

Share this post


Link to post
Share on other sites
1 hour ago, User 905133 said:

. . . while I could push the PC beyond what its resources can handle, the PC, running Cakewalk with the FW-1884 can handle tens of hundreds of plug-ins -- probably not all at the same time, though.  😜

image.png.7f3cc672d2888a8e496df13c05248ea4.png

PS: Even though its late in the day, I had not yet rebooted the FW-1884 so Windows 10 would do its Audio Endpoint Builder double check.  As a result, Cakewalk did not see my ASIO Driver / audio lines, but ASAPI (Shared Mode) had them all! 

After power cycling the FW-1884, rebooting Cakewalk. and then switching from ASAPI to ASIO, Cakewalk running with the FW-1884 sees my plug-ins!!!  (Including 26 new ones I must have forgotten I added.)

Edited by User 905133
fixed typos

Share this post


Link to post
Share on other sites

@User 905133  Good to know, My Tascam 1641 was made in 2008 , last driver was issued in 2016 and says W10. Tascam make good Windows drivers. I'd say that my 1641 driver outperforms my brand new Motu M4 driver in some ways.

  My reason for mentioning the Tascam was when I saw it didn't support W10 I was wondering if the OP was still on W7 ?. I tried Googling " Does Windows 7 support VST3" and came up with no answers. 

  • Like 1

Share this post


Link to post
Share on other sites
7 hours ago, scook said:

Either testers did not have the error (one user in this thread reported EZD3 runs OK) or

they did and failed to report it or

they reported the problem and Toontrack released the product anyway.

 

I am sure there is more than one bug on the to-do list for EZD3 and probably more than one bug that crashes the plug-in.

Chances are there are more bugs yet to be reported.

Well, yeah.

Share this post


Link to post
Share on other sites

I was having an issue with ezd3 crashing in cakewalk. Switch the driver from wasapi to asio and it works. Ezd3 must have an issue with the wasapi driver. Hope this helps somebody 

Share this post


Link to post
Share on other sites

The three I know of are using ASIO (and all different) but that is interesting. I wouldn't expect the driver to be involved with just adding the VST but it's all certainly a complicated process.

Edited by Terry Kelley

Share this post


Link to post
Share on other sites
13 hours ago, Noel Borthwick said:

That’s not accurate. Cakewalk adds that folder by default to the scan path.

I know, but isn't it still possible for it to be deleted? I thought it was worth checking, as his issue seemed so odd in the first place.

Share this post


Link to post
Share on other sites
7 hours ago, John Vere said:

I tried Googling " Does Windows 7 support VST3" and came up with no answers.

Well, technically, Windows doesn't support VST3 plug-ins (just as Microsoft doesn't officially recognize ASIO as a driver model), it's the other way around. But I did use VST3's for years, including with CbB, on Windows 7.

Moreover, since Steinberg came out with the VST3 spec in 2008, even Windows 8 was still 4 years down the road, and Windows 10 was 7 years off. So yeah, VST3 better have supported Windows 7.

I've found, though, that it's taken some manufacturers a while to get VST3 right. Acon Digital's excellent Multiply Chorus, a freeware stalwart for many years, was updated to include VST3 support, and it's just broken on Cakewalk in VST3 form. Same with a Hornet plug-in that came out just last year. So the dance is still "install VST3 first, if it has issues, try the VST2 instead."

A wholesale failure for all VST3 instruments to work in Cakewalk is a big anomaly, but @Bad Mac hasn't said whether he's tried any of the ones I suggested. As far as I can tell, he's having trouble with one single instrument that others have also had trouble with.

Until he checks back in, it's a mystery.

Edited by Starship Krupa
  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites
10 minutes ago, F0h said:

Pigments 4.0.1.2949

It works on my 2011 PC.  I will defer to others to try helping with possible reasons for the error on your system.

image.png.faea9d878dd0b230267e4c40f3bdbd1d.png

Edited by User 905133
  • Like 1

Share this post


Link to post
Share on other sites
15 minutes ago, F0h said:

In my case it is true too!
Pigments 4.0.1.2949

01_CWBL_CRASH_PIGMENTS_2022_12_29.jpg.8c43327de5a58e40dde4dd7f4e6d8365.jpg

This reply has nothing to do with the problem experienced by the OP.

The subject of the thread is misleading as subsequent posts revealed the problem was VST3 plug-ins released by Toontrack.

Toontrack acknowledged the issue and AFAIK addressed it in subsequent releases.

 

Arturia Pigments VST3 v4.0.1.2949 loads OK here in CbB 2022.11 build 21 on Win 10 Pro 22H2 

 

It is not clear when the error occurred> Was it during the initial scan, a subsequent scan, attempting to load the plug-in into a project, opening a existing project referencing the plug-in or some other time (please be specific in your new thread).

Is there a repeatable formula to generate the error?

Better to create a separate thread for this issue. 

  • Like 1

Share this post


Link to post
Share on other sites
59 minutes ago, F0h said:

In my case it is true too!
Pigments 4.0.1.2949

01_CWBL_CRASH_PIGMENTS_2022_12_29.jpg.8c43327de5a58e40dde4dd7f4e6d8365.jpg

Hi CakeWalkers.
My solution is just a little annoying:02_CWBL_MINIHOST_PIGMENTS.thumb.jpg.4eb87b33a9a8e752ccf9a37fe7f04bb3.jpg
1. Install a vst host
2. Load the vst3 in the installed vst host

Happy new year!

  • Like 1

Share this post


Link to post
Share on other sites
18 minutes ago, F0h said:

Hi CakeWalkers.
My solution is just a little annoying:
1. Install a vst host
2. Load the vst3 in the installed vst host

Happy new year!

Using a plug-in within CbB hosted in another host is not necessarily a bad thing.  I have used this technique successfully and without issues with plug-ins inside of Voltage Modular inside of CbB. The method allows for some wonderful interconnectivity.  I have done this with a number of plug-ins.

However, Pigments within a Voltage Modular host inside of CbB along side of instances of Pigments hosted by CbB seems to cause extreme slowness requiring CbB to be killed to get back control.

Also, when I first inserted Pigments into an empty project, the Synth Rack showed Pigments considerably before the UI window opened up. I do not have a super modern graphics device and since Pigments uses a lot of graphics, I am not sure if my graphics device is part of my issue. 

 

  • Like 1

Share this post


Link to post
Share on other sites

Check mark in these 4 boxes

rescan failed plugins 

rescan all plugins

scan in sandbox

generate scan log

Rescan plugins.

 

If they still crash, move non working plugins to the desktop or other folder not in the scan path. Scan as above to completely remove them. Move them back and scan as above.  If this does not work you defiantly should send dump files to vendors and cakewalk. 

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...