The importance of back-up aka... dodging the bullet. - 03/30/21 11:31 AM
I have spoken on this before.... Why you need to not only back up but set restore points.
I was working on a project the other day when my finger slipped and hit two keys at the same time. I was in Sonar and was adding tracks to the newest project. The computer froze. I mean it wouldn't do a single thing. After trying the normal things for several minutes to thaw it.... I ended up having to pull the plug. I restored the power and rebooted. Normally, this doesn't cause a problem except losing the new stuff since the last save. XP Pro is pretty resilient.
I continued to work and when I went to save the project.... Sonar kicked up an exception error and then an Out Of Memory error and the only option was to close without saving. Which as you know is unacceptable. I rebooted and tried again. Same thing. I opened the project in MC4 and then MC5 and they also kicked up the same errors and would not save. My first thought was that my C drive was too full and the file swap temporary storage sector was too small to do what it needed to write the files to disk.
I moved the projects and backup folders to my storage drive.... that was slightly overdue to be done under my normal housekeeping at years end.... Try again....same errors. No save.
I was thinking there was a glitch in one of the common shared CW files.... so I did a reinstall of Sonar. Yep.... you better have a copy of your original disks and if it's a DL you better make a copy and keep it safe as well as the paperwork with serials and keys.
The install went fine.... but did not resolve the problem. The folks on the CWBL forums were of no help. The only advice given was to forget it, buy a new computer and start over. WTH? Anyway..... nope not going that route unless forced too. And it started looking like I was at the point of being forced.
I went through the RESTORE computer to a previous point. Since it's a DAW and I never use it for anything else.... a restore to a few months ago should not affect anything in a negative manner. And at the same time, well, actually while the restore was running, I remembered something else. So after that was finished..... I also deleted the BB & RB files from my folder since I was thinking that there could have been a corruption of those files since that folder was in use at the original glitch. I had the project open in BB, deleted the saved files and then saved a fresh copy from the open, running fine, BB.
I exported the files from BB as waves and into a new folder. Then I closed BB and opened Sonar and started a new project. I imported the tracks.
So.... previously, I could add tracks to the project and save them. I could save up to four tracks and sonar would handle it fine. Normally when I save, it takes about half a second to complete the save of the entire project in Sonar. But when saving the four tracks, it was taking several seconds. Then, when I added a fifth track and clicked on save.... it would take around 10 seconds and Sonar would pop up the 2 different warnings and fail to save.
So I didn't know what it was going to do this time. I added the tracks, popped in the 5th and clicked save. Half a second and done. Also.... anyone who has Sonar knows what I'm talking about.... when you open the project folder, there's 2 icons. The one for audio was previously greyed out as if it was unavailable. This was consistent across my archived song folders and the new stuff. After the restore to point, all of those folders and files were accessible again.
The moral of the story..... back up and set restore points. AND.... don't hit two keys at the same time in Sonar.
Anyway... the DAW and it's software appears to be up and running again. My folders have been moved to my storage drive and I cleared up a ton of space on my C drive.
I was working on a project the other day when my finger slipped and hit two keys at the same time. I was in Sonar and was adding tracks to the newest project. The computer froze. I mean it wouldn't do a single thing. After trying the normal things for several minutes to thaw it.... I ended up having to pull the plug. I restored the power and rebooted. Normally, this doesn't cause a problem except losing the new stuff since the last save. XP Pro is pretty resilient.
I continued to work and when I went to save the project.... Sonar kicked up an exception error and then an Out Of Memory error and the only option was to close without saving. Which as you know is unacceptable. I rebooted and tried again. Same thing. I opened the project in MC4 and then MC5 and they also kicked up the same errors and would not save. My first thought was that my C drive was too full and the file swap temporary storage sector was too small to do what it needed to write the files to disk.
I moved the projects and backup folders to my storage drive.... that was slightly overdue to be done under my normal housekeeping at years end.... Try again....same errors. No save.
I was thinking there was a glitch in one of the common shared CW files.... so I did a reinstall of Sonar. Yep.... you better have a copy of your original disks and if it's a DL you better make a copy and keep it safe as well as the paperwork with serials and keys.
The install went fine.... but did not resolve the problem. The folks on the CWBL forums were of no help. The only advice given was to forget it, buy a new computer and start over. WTH? Anyway..... nope not going that route unless forced too. And it started looking like I was at the point of being forced.
I went through the RESTORE computer to a previous point. Since it's a DAW and I never use it for anything else.... a restore to a few months ago should not affect anything in a negative manner. And at the same time, well, actually while the restore was running, I remembered something else. So after that was finished..... I also deleted the BB & RB files from my folder since I was thinking that there could have been a corruption of those files since that folder was in use at the original glitch. I had the project open in BB, deleted the saved files and then saved a fresh copy from the open, running fine, BB.
I exported the files from BB as waves and into a new folder. Then I closed BB and opened Sonar and started a new project. I imported the tracks.
So.... previously, I could add tracks to the project and save them. I could save up to four tracks and sonar would handle it fine. Normally when I save, it takes about half a second to complete the save of the entire project in Sonar. But when saving the four tracks, it was taking several seconds. Then, when I added a fifth track and clicked on save.... it would take around 10 seconds and Sonar would pop up the 2 different warnings and fail to save.
So I didn't know what it was going to do this time. I added the tracks, popped in the 5th and clicked save. Half a second and done. Also.... anyone who has Sonar knows what I'm talking about.... when you open the project folder, there's 2 icons. The one for audio was previously greyed out as if it was unavailable. This was consistent across my archived song folders and the new stuff. After the restore to point, all of those folders and files were accessible again.
The moral of the story..... back up and set restore points. AND.... don't hit two keys at the same time in Sonar.
Anyway... the DAW and it's software appears to be up and running again. My folders have been moved to my storage drive and I cleared up a ton of space on my C drive.