No products in the cart.
Chris Gilmartin
Participant
Topics Started: 5
Replies Created: 5
Has Thanked: 0
Been Thanked: 2
Turns out it was my drive. I am not sure what I did, but I actually had the sounds files stored on a HDD. It was failing. Moved them to SDD… works like a champ. Thanks!
1
Thanked by: Henrik EkblomThis is my experience only, but I recently purchased a Samsung EVO SSD 250gb and connected it to the motherboard and I use this exclusively for SD3. Since I bought this, it absolutely flies. I can load in a 3gb kit in about 8 seconds.
Not sure if a new dedicated drive would help? There’s a Samsung driver that keeps it optimised and it sits in the tray icon on Win 10 64bit.
So, ironically enough, I have a Samsung EVO SSD drive that I house all of the sound samples, but the SD3 VST dlls (along with the standalone app, which also hangs) are housed on my C: drive. I wonder if I would get better performance if I put everything on the SSD drive?
since the sound files are already there, I am hoping I can just reinstall the app and dlls on the SSD.
Does this happen when running SD3 stand-alone?
Great thought. I never really use it stand alone. When I launched the stand alone it had a similar issue. A little faster load of the application, but the sound files a(i.e. kit loading) is slow.
No products in the cart.