MODO Bass 2 problem solved

[Ricky Wayne Hunt]

I was finally able to get MODO Bass 2 working with Cakewalk. It stopped working on two separate computers after the latest update, though it would work as a standalone and as a plugin in FL Studio. I uninstalled v2.0.3 and reinstalled v. 2.0.2 and its working agai..

[Promidi]

On 11/9/2024 at 10:29 AM, Ricky Wayne Hunt said:

I was finally able to get MODO Bass 2 working with Cakewalk. It stopped working on two separate computers after the latest update, though it would work as a standalone and as a plugin in FL Studio. I uninstalled v2.0.3 and reinstalled v. 2.0.2 and its working agai..

That's quite strange.  I can use Modo Bass 2.0.3 in Cakewalk by Bandlab.

With out looking up the previous thread, what issue did you have with Modo Bass 2.0.3 in Cakewalk by Bandlab?

[msmcleod]

@Ricky Wayne Hunt - have you got the latest version of Cakewalk's VstScan ?

IIRC, MODO Bass 2.03 started using the new VST3 convention of putting the .vst3 in a MODO BASS 2.vst3 directory.

The older VstScan did not support this convention (it was treating the MODO BASS 2.vst3 directory as if it was the plugin itself).

You can get the latest here:   

 

[user 905133]

Thanks for that link, @msmcleod.  

On 7/19/2024 at 9:58 AM, user 905133 said:

• After reverting MODO BASS 2 (to Version 2.0.2 from Version 2.0.3), back (to Version 2.0.3), and then checking some things, I found:
  • Version 2.0.3 uses a different folder/file arrangement
  • CbB did not automatically detect the change 
    • Might be a problem for some people, not others depending on personal VSTScan choices/options
    • I do manual scans as needed
  • Doing a Rescan with "Rescan Failed Plugins" selected allowed CbB to (appropriately enough) rescan and find Version 2.0.3.

On Friday I used MODO BASS 2 to create a 16 bar drum pattern with improvised bass line test project.  It worked. So, not sure if the "Rescan Failed Plugins" option would help @Ricky Wayne Hunt, but I thought I'd mention it as a possibility.