Extremely slow startup and kits not fully loading

[Chris Gilmartin]

I am using Cakewalk (by Bandlab) and have SD 3.1.2.  I have noticed that when an instance of SD3 is in my Cakewalk file, the Cakewalk file takes a really long time to open.  Once the project is open in CW, and I open SD3 within, I look at the memory gauge (upper right that shows the kit as it’s loading) and it seems to stall.  For instance, I am loading the NY Avatar kit,the memory is showing 580 as the total RAM, but loaded is only showing 120…  then a minute later it creeps to 150, then a little bit later 168.  THis is not while song is playing  nor am I in cached mode.  I just want the entire kit to load, but it doesn’t seem like it is doing that.

Also, switching kits seems to take a long time, and even changing a drum out can cause it to hang.

I feel like it worked much better with it was Sonar Platinum (prior to Bandlab taking over) but I can’t image the DAW changed that much.

i feel like this may have started after a reinstallation of SD after a drive failure.  I house the sound files on an internal (SDD) drive (p: drive) that is separate from my operating system drive (c: drive).

I am also getting errors – occasionally) that the sound files are corrupt, but I click ok and they seem to work.

Windows 10, 64bit

 

Any help would be appreciated!

Thanks!

Topic

[Sedge73]

This 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.

[Chris Gilmartin]

Thanks for the quick feedback.  Are you using Cakewalk by Bandlab?

[Brad]

Does this happen when running SD3 stand-alone?

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

[Chris Gilmartin]

Brad wrote:

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.

[Chris Gilmartin]

Sedge73 wrote:

This 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.

[Mark King]

I can’t see that speeding it up. Most people have the dll on the C drive and samples on another. I use a spinning disk drive and my loading time is nothing like yours. Probably around 10 seconds. With an SSD drive it should be much better.

SD3 with older sdx,s plus Rooms of Hansa and Death & Darkness. Cubase and wavelab current versions. Roland TD50x using all trigger inputs for triggering SD3 only. Windows 11 computer. Various keyboards and outboard gear as well as VST instruments. Acoustic drums: Yamaha 9000 natural wood and Pearl masters. Various snare drums. RME BabyFace Pro FS and Adam A7X monitors

[Olof Westman]

BEST ANSWER

I think your hard drive is broken. HDDs usually load
at about 50MBs per second.

Olof Westman - Toontrack
Coder

1

Thanked by: mileyondrumz

[Chris Gilmartin]

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 Ekblom

[Author]

Replies