mark4man
MoonMix Studios
What does it mean when a (badly) corrupted SONAR XL Project File can seemingly be repaired by opening up other uncorrupted files first?
I have a Project that started to go bad about two weeks ago (& I posted here in the BBS in hopes of a fix: http://www.homerecording.com/bbs/showthread.php?t=125332&highlight=mark4man)
The problem originally began when I attempted to open it, which was unusually slow; & the progress bar would stop at a few different points (40%, 63%, etc.)
Once I had it opened (& I'm running 18 to 20 24-Bit, 96 kHz tracks); It would always dropout almost immediately upon hitting Play. I would have to hit the Reset & Play buttons a few times before the tracks would play successfully...
I sort of got it back to normal by increasing my buffer size & mixing latency, but then today, it took a turn for the worse. Playback took longer & longer to kick in; & then stopped altogether. After about 30 seconds, my monitors would let out a nasty buzz, which I could only stop by turning off the AI (Layla 24/96.) Scrolling was dead slow; Saving was dead slow...just about all functionality ground to a halt. It even took forever to close the program; & I noticed it would slow down Windows (XP) until I rebooted.
I performed a clean uninstall & reinstall of both my Echo Audio software & drivers...& SONAR XL.
Then I opened up the Project; & the same thing happened...(only to a slightly lesser degree.) Now...I'm worried (the project represents song 9, of a 9 song CD; & contains dozens & dozens of painstakingly constructed tracks.)
I got it closed; & then opened up three or four other Projects that were OK; played them...they played fine...
...Then I reopened the corrupted Project...& it seems to work OK now!
Just to be sure, I bounced all of my complex multiple comped tracks to stereo stems, to take the load off the CPU (as before, it had seemed that the problem was exacerbated by opening more tracks)...& it seems to be under control.
But why would uninstall/reinstalls not help...& yet, opening uncorrupted files prior to opening the corrupted file would???
Thanks for any help...as I'm not sure at this point the file is going to stay fixed (if it even is at this point)...
mark4man
I have a Project that started to go bad about two weeks ago (& I posted here in the BBS in hopes of a fix: http://www.homerecording.com/bbs/showthread.php?t=125332&highlight=mark4man)
The problem originally began when I attempted to open it, which was unusually slow; & the progress bar would stop at a few different points (40%, 63%, etc.)
Once I had it opened (& I'm running 18 to 20 24-Bit, 96 kHz tracks); It would always dropout almost immediately upon hitting Play. I would have to hit the Reset & Play buttons a few times before the tracks would play successfully...
I sort of got it back to normal by increasing my buffer size & mixing latency, but then today, it took a turn for the worse. Playback took longer & longer to kick in; & then stopped altogether. After about 30 seconds, my monitors would let out a nasty buzz, which I could only stop by turning off the AI (Layla 24/96.) Scrolling was dead slow; Saving was dead slow...just about all functionality ground to a halt. It even took forever to close the program; & I noticed it would slow down Windows (XP) until I rebooted.
I performed a clean uninstall & reinstall of both my Echo Audio software & drivers...& SONAR XL.
Then I opened up the Project; & the same thing happened...(only to a slightly lesser degree.) Now...I'm worried (the project represents song 9, of a 9 song CD; & contains dozens & dozens of painstakingly constructed tracks.)
I got it closed; & then opened up three or four other Projects that were OK; played them...they played fine...
...Then I reopened the corrupted Project...& it seems to work OK now!
Just to be sure, I bounced all of my complex multiple comped tracks to stereo stems, to take the load off the CPU (as before, it had seemed that the problem was exacerbated by opening more tracks)...& it seems to be under control.
But why would uninstall/reinstalls not help...& yet, opening uncorrupted files prior to opening the corrupted file would???
Thanks for any help...as I'm not sure at this point the file is going to stay fixed (if it even is at this point)...
mark4man