pinguinotuerto

I want to thank everyone who chimed in. Your help is very much appreciated.

Thanks for your response!

Hey John, Wasn't aware of that. I upgraded to Cakewalk from Sonar Producer Edition so I have melodyne on my machine. Don't know if Cakewalk now comes with melodyne and if the newer version does things that previous one didn't do. I don't remember exactly what I did right now but when I tried to have my audio file follow the project tempo I think audiosnap was launched automatically.

Just wondering what people's experiences have been with audiosnap with newer systems using Windows 10 or Windows 11? I'm still on a Windows 7 computer and I'm thinking about upgrading and audiosnap has been a feature that has never worked properly for me even with the latest version of Cakewalk. Once I launch audio snap my system gets bogged down it becomes sluggish and erratic. Does audio snap work properly for others? Are transients detected correctly and system works well after launching it? Hoping to get answers from people who use it on multiple tracks at once, like multitrack drums. Thanks in advance.

Hey John, Thanks for replying. I hear ya, but I'm doing multi-track drums that are grouped and after the bounce the clips become ungrouped, so I have to create a group again and then I can loop them, so it becomes a bit tedious after a while. If it were just one clip, then yeah, no big deal. Thanks again.

Hoping somebody can answer this question for me just in case I am missing something. When I time stretch a clip, I am not able to Loop that clip unless I bounce the clip down. Is there a way to Loop a clip After Time stretching without having to bounce? I can do this easily in Logic Pro and I'm hoping the same is true for Cakewalk. Thanks in advance.

I want to say thanks to everyone who chimed in trying to offer suggestions.

Yeah, I had the migration boxes checked. I guess Cakewalk sees the VST2 and VST3 versions of AD2 as two separate plugins (that's what XLN said) and that's why it wouldn't replace the VST2 with the VST3 automatically.

Maybe I didn't have that option checked? I'll look in preferences and see. That would have saved me a lot of trouble.

XLN helped me solve the issue. The problem was not that I moved AD2 to a different drive, but that I unchecked VST2 in the XLN online installer. I was under the impression I was using the VST3 version of AD2, but I think what happened was that I used a template when I started this project that had the VST2 version of AD2 instead of the VST3. That's why when I would create a new project from scratch, it found AD2 (because it was inserting the VST3 version), but the existing project couldn't find AD2 because it was looking for the VST2 and I had unchecked that box in the XLN installer. Lesson learned.

I did. XLN might have found the problem. I'll report back after i try their suggestion.

Yes, that would be a last resort solution if this can't be resolved, but I think there has to be a fix.

When I open the plug-in manager and I look at the properties of The Addictive Drums 2 plug in, I see the path to the VST folder which has never changed. That's the only thing that I can manually change within Cakewalk, but there's no need to change it because the plugin is still in the same folder.

Hi Glen, I did that already and it made no difference. The strange thing is that Cakewalk finds AD2 in new projects with no issues. If I had moved the vsti, then I would understand this happening, but I did not.