Hi all,
Earlier this year I custom built I new studio computer and immediately ran into some repeated crashing issues with it after setting it up. At the time one of the main culprits for causing the crashes seemed to be ST3.
With the amazing help of some of the good folks on these forums I worked through most of my issues and discovered things I had forgotten to deal with when setting up my system and all was well, or so I thought.
Despite the fact I solved many of the problems I was having with my new system, I now realise that because of the repeated ST3 issues I was having I simply began to stop using it in my productions as I had time critical work to complete so I deferred to my proven stable plug-ins. Recently I reached for ST3 again as I knew it had a particular sound I needed and boom - we are on the first train straight back to crash-ville again.
My system is a core i7 7700 with 32Gb of ram and SSD's for both system and sample drives - plenty of grunt to run all I need. [mod edit - suspicious links removed] However even an empty project with a single instance of ST3 called up - play a good bunch of notes in fast succession and Sonar crashes and the report window points to ST3 as the cause.
I wondered if it was because I had the ST3 plugin on the system drive and the sample data on the sample drive - but tonight I tried moving all the sample data on the standard installation path on the system drive but to no avail - 1 instance, handful of notes and boom.
Strangely ST3 runs absolutely fine on my older, slower laptop with only 8Gb and a mech HDD - Go figure?
Anybody got any wisdom to impart on this problem I would be glad to hear it!!
Thanks in advance