chris.r
49% sad, 51% happy ;)

Great answer, albeit a bit optimistic for some. Well, that's life.

The problem persists. In fact, even the "SONAR 8.5.3 Producer Edition-cycled" save version that has been afterwards saved with BLCW gets stuck at the "Almost done..." point when opening the project file.
 
I guess it's back to SONAR 8.5.3 then.
 
 

Create a new very large file in BLBC and resave it, then see if you get the exact same problem. Could be that your old very large file from previous version could be be corrupted.

kday
Create a new very large file in BLBC and resave it, then see if you get the exact same problem. Could be that your old very large file from previous version could be be corrupted.

Nope, see the original reply from Noel Borthwick who's a part of the Cakewalk team; http://forum.cakewalk.com/FindPost/3787799
 
How I got the project opened up again at all, was to ditch all the AMA data in it. This was done by opening the version that had already been created and in use within BandLab's Cakewalk, and opening that .cwp file using SONAR 8.5.3 Producer Edition.
 
I hope that clarified the issue. I'm not exactly sure what you mean by "BLBC" ("BandLab Before Cakewalk!?!?") in this context; if you could clarify things a bit on that, I'd appreciate it. Thanks.
 

AudioAnnihilator

kday
Create a new very large file in BLBC and resave it, then see if you get the exact same problem. Could be that your old very large file from previous version could be be corrupted.

Nope, see the original reply from Noel Borthwick who's a part of the Cakewalk team; http://forum.cakewalk.com/FindPost/3787799
 
How I got the project opened up again at all, was to ditch all the AMA data in it. This was done by opening the version that had already been created and in use within BandLab's Cakewalk, and opening that .cwp file using SONAR 8.5.3 Producer Edition.
 
I hope that clarified the issue. I'm not exactly sure what you mean by "BLBC" ("BandLab Before Cakewalk!?!?") in this context; if you could clarify things a bit on that, I'd appreciate it. Thanks.
 

I was saying to create a new very large project file in the latest CW update, and see if you get the same error as you did with the old file ? To see if very large file crash is limited to only that file and not files created in the new CW program.

I had a relatively large project that I had been working on in the previous version.  After installing this update, there was a message about this song file not being the right one or something like that.  I sat back a bit and re-tried it.  It took some time loading, but it did indeed open up and worked fine after that.

Thanks to the OP for sending the project file...
I looked at the file and the primary reason for the very slow load is that it appears to have millions of audio snap markers in some clips. Most likely this was due to some kind of corruption due to some bugs in earlier versions. Well and also the fact that it has 490 audio tracks and 6900 measures as well as ARA clips :) 
 
In any case we are doing some optimizations and I feel confident that in the next release we should get this project loading orders of magnitude faster than it ever did.

Noel Borthwick [Cakewalk]
 
In any case we are doing some optimizations and I feel confident that in the next release we should get this project loading orders of magnitude faster than it ever did.

Hey Noel ,
 
While you guys are working on that bug, is it possible to fix another annoying bug issue, it's not major, but it's super annoying and makes using the Pro Channel modules really tedious when using it for editing tracks. The Pro-Channel module scroll order is lost once you leave that track to go to another, and then come back to that Track your module scroll order is lost and you have to look for that module once again. Here is a reference to that bug issue pictured in the GIF on this thread I started, if you want to take a look and see if it's something you guys can fix. Really appreciate the great work you guys have been doing to smash bugs lately, so I just thought I bring this one up, because it's seems like it could be easy to nip in the bud.
 
Bug thread
http://forum.cakewalk.com...ft-it-in-m3775517.aspx
 
Thanks