Chevy

OK Scook,  you're right on the money !   Problem solved.

Took a fair bit of looking, as I didn't know what I was doing...  I walked thru all your steps and still didn't get it going...   I could see the Ozone 9 Advanced .dll files being scanned while the scan was in progress, but they still did not show up as scanned and registering in Cakewalk.

I had to do a file search on Win 10 to find the right Ozone 9 files folder path.  Turns out that the path I added to the paths to be scanned needed an extra   "/izotope" added after the "/vst3" folder in the path. 

Why this is this way, I have no idea.  Why would these new Ozone 9 .dll files not just be added to the existing Ozone 8 .dll's files folder?  Or - why didn't Cakewalk pick them up in the same path anyways ?

Just bought Ozone 9 Advanced, loaded it up, and it runs successfully as a stand-alone entity.  However, the individual plugins don't appear in Cakewalk for some reason.  I've tried re-scanning all plugins,  but still no success.

I have Ozone 8 Advanced, Ozone 9 Elements and those plugins all show up in Cakewalk.

Gotta be something simple... any ideas ?

"When I highlight a drum clip and try to invoke the region effect Drum Replacer, I get the following error message:"

When I highlight a drum clip and try to invoke the region effect Drum Replacer, I get the following error message:

VST Plug-In Error

The following VST plug-in failed to load: (80004002)

C:program files\cakewalk\shared utilities\internal\Drum Replacer\DrumReplacer.vst3

Drum Replacer

I've tried to uninstall and reinstall Drum Replace, but no joy, same problem.

Any ideas?

Thanks!

10 minutes ago, Noel Borthwick said:

I don't work for support  I can get the link from them but its quicker to just PM to me.

Oh.   New to this forum.... will figure things out eventually.  OK.... link sent to you from OneDrive.

3 hours ago, Noel Borthwick said:

Interesting. We'll still need the project because thats the quickest way to investigate it. You can trim it down and save as a new project so that the size becomes smaller.

did you not get the link?  I uploaded to OneDrive and sent you the file share info to support@bandlab.com.

1 hour ago, Noel Borthwick said:

@Chevy please upload it to dropbox, google drive, One drive or any file share of your choice and send a link. You can zip the full project folder.

Noel,    this Melodyne problem occurs only with Waves plugins.  My Melda, Izotope and Softube plugins don't cause the problem.

OK Noel,   sent you the OneDrive link to the file.

Just also discovered that the Melodyne problem disappeared when I either turned off or deleted the Waves plugins that were on the particular audio track I was working on.

53 minutes ago, Noel Borthwick said:

Have you tried it in an new project with just an audio clip?
When that error fires it is normally specific to the project you are doing this which is why we need the steps and the actual project file.

Extra info re Audio Engine Dropout (12)      Windows 10,  Mixing Latency currently 1024, interface is Focusrite 6i6 2nd gen with new driver and firmware updated just yesterday,   ASIO driver mode.

Ok, tried it with a brand new project, short audio clip, and it seems to be working.

The steps are: split the track to get a very short clip, select the clip, select Region Fx, then Melodyne, then Create Region Fx.  This causes the computer to hang up, and eventually the Audio Engine Dropout (12) occurs.

But looks like you are right, this seems specific to this project.  

How do I send you the project file...  can't send the audio...  limit seems to be 4.88 MB ?  Just sending the .cwp file.... is that what you are referring to ?

Song test file for Bandlab Feb 4 2021.cwp

yep, it was a very short clip

I just reinstalled Bandlab, and then upgraded to Melodyne 5, and I'm still getting "Audio Engine Dropouts" (error code 12) when I try to invoke Melodyne via Region Fx;  happens as soon as I click on Create Region Fx.   Don't even get a chance to play the clip.

The help section text says  "12  [Internal] Internal audio buffer memory limit overflow. Contact support with recipe/project file."   Not sure what this is referring to.  Which buffer is this ? I messed with the Mixing latency buffers and ASIO,  bumped up to 1024, but that makes no difference to the problem. What is a recipe ?

I just reinstalled Bandlab, and then upgraded to Melodyne 5, and I'm still getting "Audio Engine Dropouts" (error code 12) when I try to invoke Melodyne.  Can't use it.

The help section text says  "12  [Internal] Internal audio buffer memory limit overflow. Contact support with recipe/project file."   Not sure what this is referring to.  Which buffer is this ? I messed with the Mixing latency buffers and ASIO,  bumped up to 1024, but that makes no difference to the problem. What is a recipe ?

Thanks for the tips... checked them all, and all are as you suggested.  

BUT....   I realized the Record button was activated for all tracks...  somehow the master Arm All Tracks was hit I guess, and that prevents the track meters from working... problem solved.  Thanks!

I select a short audio clip and then click on Region Fx - Melodyne - Create Region Fx and the program just hangs up for a long while, then I get the audio engine dropout (12) alert.   This is without even asking it to play the clip.

The help section text says  "12  [Internal] Internal audio buffer memory limit overflow. Contact support with recipe/project file."   Not sure what this is referring to.  Which buffer is this ? I messed with the Mixing latency buffers and ASIO,  bumped up to 1024, but that makes no difference to the problem. What is a recipe ?

For what it's worth, I just had my Scarlett 6i6 driver and firmware updated today, but that didn't help with the problem either.

Is it possible Melodyne 4.2.4 won't work with Bandlab 2021.01 ?

The meters on each track don't display the audio level, they are just blank.  Can't seem to find how to turn them on. What am I doing wrong? 

The level meters for the mixing console do work, though.  

thanks for the info !    I'm back to Studio X3 for now...  never had any problems with it...

Bummed out here, spent a lot of time working on a project without incident, but got occasional crashes due to invoking an Ozone 8 EQ plugin.  At one point, Cakewalk would no longer open the project, but just crash right off the bat, with the message   "fatal error has occurred"    "crash dump file created..."

I'm assuming incompatibility with the plugins.

Any ideas anyone?

Thanks!

Doh!   didn't realize it was a VST.....  that did it, thanks much!

Hi guys,  back after 5 years off...   trying to get Drum Replacer working.  Downloaded fine, seemed to load fine, but doesn't appear in the Region FX dropdown.  Rebooted computer... no dice.  Tried to reload add-ons, but Assistant says it's already loaded.  

Any ideas?