DrLumen
What were the symptoms when it went bad? Was it just certain sectors or did everything crash-and-burn?

No symptoms really. Died a sudden death.

It went flawlessly!  In my situation, I took the cloned HDD completely out and replaced it with the SSD, and I just assigned the SSD the same volume letter as the old drive, so after a quick reboot, everything worked great! --
 
Now I am totally glad I did it, and I would do it again, but candidly, I'm a little surprised that my current project doesn't load faster with all the storage being SSD associated with it. I know it's a fairly large project, but I have a pretty powerful DAW and I guess I expected my project to load faster. Hmm...

razor
It went flawlessly!  In my situation, I took the cloned HDD completely out and replaced it with the SSD, and I just assigned the SSD the same volume letter as the old drive, so after a quick reboot, everything worked great! --
 
Now I am totally glad I did it, and I would do it again, but candidly, I'm a little surprised that my current project doesn't load faster with all the storage being SSD associated with it. I know it's a fairly large project, but I have a pretty powerful DAW and I guess I expected my project to load faster. Hmm...

See above at http://forum.cakewalk.com/FindPost/3615325

BobF

razor
It went flawlessly!  In my situation, I took the cloned HDD completely out and replaced it with the SSD, and I just assigned the SSD the same volume letter as the old drive, so after a quick reboot, everything worked great! --
 
Now I am totally glad I did it, and I would do it again, but candidly, I'm a little surprised that my current project doesn't load faster with all the storage being SSD associated with it. I know it's a fairly large project, but I have a pretty powerful DAW and I guess I expected my project to load faster. Hmm...

See above at http://forum.cakewalk.com/FindPost/3615325

 

Yeah, thanks. My samples were already on an SSD. The audio and picture files are what went to SSD this time. That was the last element of SPLAT to be moved to SSD, so I figured that must be the reason for the slow load time. Even reopening the project doesn't seem much faster.

razor

BobF

razor
It went flawlessly!  In my situation, I took the cloned HDD completely out and replaced it with the SSD, and I just assigned the SSD the same volume letter as the old drive, so after a quick reboot, everything worked great! --
 
Now I am totally glad I did it, and I would do it again, but candidly, I'm a little surprised that my current project doesn't load faster with all the storage being SSD associated with it. I know it's a fairly large project, but I have a pretty powerful DAW and I guess I expected my project to load faster. Hmm...

See above at http://forum.cakewalk.com/FindPost/3615325

 

Yeah, thanks. My samples were already on an SSD. The audio and picture files are what went to SSD this time. That was the last element of SPLAT to be moved to SSD, so I figured that must be the reason for the slow load time. Even reopening the project doesn't seem much faster.

Bummer.  The only other thing I can think of is AV real-time scanning.  I use Defender and have the SONAR, VST and sample folders excluded from scanning.  This sped up load times in a huge way.
 
You can open a Task Manager window and watch for your AV software activity while you load a slow-to-load project to see if this a problem in your case.

Rob[atSound-Rehab]

DrLumen
What were the symptoms when it went bad? Was it just certain sectors or did everything crash-and-burn?

No symptoms really. Died a sudden death.

That's kinda scary. At least HDD's usually give some indication.

DrLumen

Rob[atSound-Rehab]

abacab
Still, I would recommend a backup image plan for all important drives, whether HDD or SSD, as all drives can fail.  Murphy's Law ...
 

 
+1000
 
I had one SSD fail on me after a little more than 2 years of virtually daily use ... on a tablet PC which I used for office tasks. Never bothered to do a proper image since it's just office stuff and not a DAW ... took me 3 days to get the machine back to where it was before the SSD crash. one day just for getting windows to the latest update stage and 2 days to download and reinstall all these applications that I installed over the years ... backup, backup, backup

What were the symptoms when it went bad? Was it just certain sectors or did everything crash-and-burn?

Hmm, maybe your topic can branch into another post? It seems to have gained a life if it's own! 😜

BobF

razor

BobF

razor
It went flawlessly!  In my situation, I took the cloned HDD completely out and replaced it with the SSD, and I just assigned the SSD the same volume letter as the old drive, so after a quick reboot, everything worked great! --
 
Now I am totally glad I did it, and I would do it again, but candidly, I'm a little surprised that my current project doesn't load faster with all the storage being SSD associated with it. I know it's a fairly large project, but I have a pretty powerful DAW and I guess I expected my project to load faster. Hmm...

See above at http://forum.cakewalk.com/FindPost/3615325

 

Yeah, thanks. My samples were already on an SSD. The audio and picture files are what went to SSD this time. That was the last element of SPLAT to be moved to SSD, so I figured that must be the reason for the slow load time. Even reopening the project doesn't seem much faster.

Bummer.  The only other thing I can think of is AV real-time scanning.  I use Defender and have the SONAR, VST and sample folders excluded from scanning.  This sped up load times in a huge way.
 
You can open a Task Manager window and watch for your AV software activity while you load a slow-to-load project to see if this a problem in your case.

I've got a good av program that my DAW maker suggested I use, so i can make sure nothing music is scanned. I also turned off the auto scan of my vst folders when i open sonar. I do that manually.

Thanks for this tip. I wouldn't have thought to look there.

Does anyone know of a program, or performance monitor setting, etc. that I can run while opening a Sonar project that will help me ID what is causing the slowness?
 
Thanks,
 
 
Stephen