Kevin Walsh

Sorry I misunderstood your comment and the fact that the plugin was causing the crash. I know there's not a lot that a DAW can do to prevent a plug-in from taking the whole thing down. I assumed it was cake walks problem because it doesn't crash with reaper. Speaking philosphically as a software user who isn't qualified to make the distinction between crash culprits, it would be lovely if all the companies involved could gather around a table and figure out how to prevent that from happening. Thanks for the information.

That's all very useful to know, thank you, it's great to have a good workaround from the Cakewalk team. Still I've got to believe there's some way Cakewalk could handle this situation without a crash with no error messages whatsoever. I know that for many people, running to a forum for an answer isn't something they normally do. Just my two cents worth.

That wasn't the problem in this instance. As I said in my OP, I reset the plugin, moved the plugin file, TONEX. vst3, to the common files\vst3 folder, and then delete the IK-TONEX.vst3 folder. I believe that if I had simply reset the plugin and rename the foler to say. IK-TONEX it would have worked as well. Thanks!

I have no doubt the Windows has that problem but in this case the file and directory were not identically named. In fact, the file was a in another directory below the unfortunately named directory.

I keep my Sonar 8.5 key fob in a safe deposit box.

Reaper seems to have the secret as well. I only have CbB, Sonar and Reaper so those are the tests I ran.

Yes, and that worked, but in the end I just moved it up to the top of the VST3 tree for simplicity's sake. In either case, SONAR seems to be crashing when it encounters a folder is named with a .vst3 extension. Note that it doesn't crash during the scan, it crashes when you try to add it to the fx bin on a track. The rename workaround is all very good, but imho in most cases it's not good form for software to crash.

I updated my TONEX plugin today to 1.71 and after installing, opening a pre-existing TONEX instance or trying to add a new instance to a track would instantly crash SONAR with a dump file. Turns out that IK installs the plugin into this folder: c:\program files\common files\VST3\IK-TONEX.vst3\Contents\x86_64-win\TONEX.vst3 I had to delete the SONAR registry entry for the plugin, then move the .vst3 file to c:\program files\common files\VST3\TONEX.vst3, then delete the old folder and re-scan. After that, it worked. Prior to doing all that, I tested it in CbB, SONAR and Reaper. Reaper worked, but CbB and SONAR crashed. I suspect SONAR sees the IK-TONEX.vst3 folder and assumes by it's extension that it is a vst3 file and tries to open it as such, but that's just guessing. Hope this helps someone else who sees this.

Thanks, Lynn. I think I shaved maybe 8 seconds off of it. I appreciate your comments!

Thanks for coming back for another listen!

Thanks, I've posted Mix 3 that I think addresses the top end.

I really enjoyed it. I'm a bit in awe of the people who make this kind of music. It's beyond me how you do it.

Thanks for the feedback and the listen! When you say warm, do you mean the top end is excessively suppressed? Second mix is up so I'm looking forward to your critique on it.

Always appreciate your feedback, Nigel. Yeah, I was going for a Pink Floyd Doo Wop kind of a vibe.

What a great discussion! This is why I love this forum. I have so many projects with bunches of markers clustered in a group at the end out of the way because I didn't know how to delete them. I can't wait to go back and remove them all with vicious glee.