Need advice regarding issues with opening existing Sonar projects (cwp) on a new computer

[Ron Caird]

My 10 year old Dell desktop (i5 core processor/32 GB RAM/ Windows 11) recently bit the dust.  I have replaced it with a new i5 computer, 16 GB RAM, Windows 11 Pro.  Fortunately all of my existing projects were stored on an external USB hard drive.  Through the Command Center I downloaded and installed Sonar Platinum then installed paid Sonar from the Cakewalk Product Center.  I also installed many of the third party instruments and plug-ins that were on the deceased computer.  I may not have yet gotten every one of the previously installed third party components installed yet as I am trying to determine what was there.  Anyway, there are a number of existing projects that will not open in the new instance of Sonar.  If I try to open them by browsing from the start screen some of them will scan vst's then say the project has been opened before returning to the Start Screen with no project open.  Others will begin to scan vst's and then close Sonar entirely.  If I try to open a project from Windows Explorer with Sonar open, after about 5 seconds Sonar will close.  There are a few existing projects that will open but I have not been able to determine a pattern of what will or will not open.  I have tried about 15 different projects, all .cwp files. 3 of them opened the rest did not.  I probably have 50 or 60 projects total.  The experience with Sonar Platinum is about the same, even with projects that originated in Sonar Platinum.  I have created a few small projects on this current computer and those open and close as expected.  These only have a couple of audio tracks and an instance of EZ Drummer.

Any ideas on what I have missed or solutions I might try?  Thanks.

[Bass Guitar]

I have a similar problem. You will see my post on this page further down. 

The projects will crash right when it gets to a toast notification warning about a few missing instruments and plugins. 
They aren’t actually missing, they are just either in a different folder than the previous computer or I have upgraded to VST3 version. 
 

Did you check to see if there are mini dump files generated? 
They are found in User/ your name/ App data/ Roaming/ Cakewalk/ Sonar/mini dumps. 
 

There’s a free app called windbg that will open and analyze them. 
 

Im just in the process of trying to figure out what is going wrong.  The crashes don’t always generate a dump file. 

[David Baay]

54 minutes ago, Ron Caird said:

If I try to open them by browsing from the start screen some of them will scan vst's then say the project has been opened before returning to the Start Screen with no project open.  Others will begin to scan vst's and then close Sonar entirely.

When you say "scanning" VSTs do you mean "loading"?  VST scanning should already have been completed and not be triggered by opening a project.

If it is actually related to scanning, will Sonar get through a VST scan initiated from Utilities >  Cakewalk Plugin Manager with no project open?

If the scan complestes, and opening a project still fails, try holding Shift as you launch the project from the browser top open the project in Safe Mode and disallow loading any plugins that are not in projects that open without issue.

Edited 15 hours ago by David Baay

[David Baay]

56 minutes ago, Ron Caird said:

Any ideas on what I have missed or solutions I might try?

It is possible you have an issue like Bass Guitar's related to projects that have empty Prochannels. As I recall, I was able to fix one of his by opening the project in SONAR 8.5 that ignores Prochannel content.

If you don't have access to 8.5, PM me a link to download a zipped project and I will have go at it.

[Ron Caird]

6 minutes ago, David Baay said:

When you say "scanning" VSTs do you mean "loading"?  VST scanning should already have been completed and not be triggered by opening a project.

If it is actually related to scanning, will Sonar get through a VST scan initiated from Utilities >  Cakewalk Plugin Manager with no project open?

Yes, I meant VST loading.  Sonar does get through the VST scan both when the program launches and when initiated from Plug in Manager.  I will try the 'safe mode' approach.

[Ron Caird]

16 minutes ago, Bass Guitar said:

Did you check to see if there are mini dump files generated? 
They are found in User/ your name/ App data/ Roaming/ Cakewalk/ Sonar/mini dumps. 
 

There’s a free app called windbg that will open and analyze them. 
 

Im just in the process of trying to figure out what is going wrong.  The crashes don’t always generate a dump file. 

There are a number of dmp files.  I will get the windbg app and see what I might learn.  Thanks.

[Ron Caird]

6 minutes ago, David Baay said:

It is possible you have an issue like Bass Guitar's related to projects that have empty Prochannels. As I recall, I was able to fix one of his by opening the project in SONAR 8.5 that ignores Prochannel content.

If you don't have access to 8.5, PM me a link to download a zipped project and I will have go at it.

By empty, do you mean that none of the modules in a Prochannel are in use?  Probably most of the Instrument channels in any project will not have any Prochannel modules turned on. I may have my 8.5 installation discs somewhere so I will attempt to find them

[David Baay]

25 minutes ago, Ron Caird said:

By empty, do you mean that none of the modules in a Prochannel are in use?

I'm referring to both a bug and a hack going back to SONAR X1 that allowed creating tracks/buses that didn't even have the minimum of the GlossEQ module in them - just completely empty. This didn't generally cause any problems in SONAR or CbB, but early releases of Sonar would crash on it. This was resolved when I reported it, but John (Bass Guitar) continued to have issues with a seemingly related Prochannel corruption in his legacy projects. It's possible you;re seeing something like this but itmight be completely unrelated. Just thought I'd clarify since John brought it up.

Edited 14 hours ago by David Baay

[Ron Caird]

I was able to download the WinDBG app and analyze some of the mini dump files.  There were 10 dmp files, I analyzed 5 of them, all of which identified an INVALID CRUNTIME PARAMETER c0000417 BREVERB 2.  I'm guessing that my next step is to uninstall Breverb from Sonar and try to load again.  Other projects which have loaded with missing VST effects just gave me a message that effects were missing and would identify them.  Unless anyone has different thoughts on how to proceed.

Again, thanks for your help and for furthering my education!

[Bass Guitar]

@David Baay    @Ron Caird   

I have been working on this all day trying to get to the bottom of it. 

Yes at the heart of it is there was something happened and everything points at the prochannel. No need to open them in older Sonars. Just use safe mode. If you have the same issue it will show one of these.

 

 

And no need to uninstall anything. There should be nothing wrong with your currant installation. This is something else and I'm slowly narrowing it down to WHEN this happened to these files.   

 

I will post further information in my thread. 

Edited 13 hours ago by Bass Guitar

[David Baay]

1 hour ago, Ron Caird said:

INVALID CRUNTIME PARAMETER c0000417 BREVERB 2

I recalled others reporting issues with Breverb and hunted up an old thread. I'm not sure what the current state of it is, and there may be a newer thread somewhere, but it seems some versions are/were more stable. I never used it myself.

 

[Ron Caird]

I moved Breverb into another folder that is not part of the vst scan for now until I can learn why it is causing the problem.  Unfortunately, I have used it in a number of projects.  So far all the projects load and can be run.  I get the toast notification that the Breverb plugin is missing but the project is still accessible.  Most of these are completed projects so I'll just leave them as is for now.  For projects that are currently active I have (will) replace the Breverb with an alternative.  A bit disappointing as I have used Breverb enough that I am comfortable with the interface and have found some preferred settings, but I suppose it never hurts to have options.

[Bristol_Jonesey]

15 minutes ago, Ron Caird said:

I moved Breverb into another folder that is not part of the vst scan for now until I can learn why it is causing the problem.  Unfortunately, I have used it in a number of projects.  So far all the projects load and can be run.  I get the toast notification that the Breverb plugin is missing but the project is still accessible.  Most of these are completed projects so I'll just leave them as is for now.  For projects that are currently active I have (will) replace the Breverb with an alternative.  A bit disappointing as I have used Breverb enough that I am comfortable with the interface and have found some preferred settings, but I suppose it never hurts to have options.

If my memory aerves me correctly, there were 2 different versions of Breverb

One was a dedicated Pro Channel module and the other was a standard vst. 

Are you getting the same problem with both versions?