The No.1 Website for Pro Audio
 Search This Thread  Search This Forum  Search Reviews  Search Gear Database  Search Gear for sale  Search Gearslutz Go Advanced
Steven Slate Drums 4 Crashing DAWS Virtual Instrument Plugins
Old 25th March 2017
  #1
Deleted User
Guest
Steven Slate Drums 4 Crashing DAWS (SOLVED)

SSD4 is crashing Cubase, Reaper and S1 here, Mac OS X current Sierra.
I run EZ2, Superior 2, AD 2, BFD2 with no issues at all.
Ive been back and forth with support and tried . all the options Logic seems OK but its AU format .

Anytime I click on a drum in the kit POOF, DAW goes down.

anyone read these OS X crash reports? Every crash report I have ALL have Slate listed as the culprit on thread Zero, this is the first one I got on thread 40


Thread 40 Crashed:
0 com.slatedigital.SSDSampler 0x000000012598bcd2 CWaveData::FillBufferWithSampleDataDiff(long, float*, float*, CVoiceRenderCounters&, CSamplerEngine*, bool&) + 914
1 com.slatedigital.SSDSampler 0x00000001259baec1 CInterpolatorEngine::InterpolateStereoLin(float*&, float*&, float, float, int, double, float, float&, bool&) + 545
2 com.slatedigital.SSDSampler 0x00000001259bb28f CInterpolatorEngine::Interpolate(float*&, float*&, float, float, int, double, double, float, float, float&, bool&) + 767
3 com.slatedigital.SSDSampler 0x000000012598885c CVoicePool::RenderVoicePool(unsigned long, unsigned long) + 3516
4 com.slatedigital.SSDSampler 0x0000000125970cb1 CSamplerEngine::Render(int, unsigned long) + 273
5 com.slatedigital.SSDSampler 0x00000001259998fb Filter::plug_audio_and_events_process(float**, int) + 315
6 com.slatedigital.SSDSampler 0x0000000125999c05 Filter::processBlock(juce::AudioSampleBuffer&, juce::MidiBuffer&) + 181
7 com.slatedigital.SSDSampler 0x00000001257677da JuceVSTWrapper::processReplacing(float**, float**, int) + 3146
8 com.presonus.vstservice 0x0000000119158b5e 0x119127000 + 203614
9 com.presonus.studioone2 0x0000000107807990 0x107096000 + 7805328
10 com.presonus.studioone2 0x00000001075f54be 0x107096000 + 5633214
11 com.presonus.cclsystem 0x00000001093602b0 0x1092cf000 + 594608
12 com.presonus.cclsystem 0x0000000109360d68 0x1092cf000 + 597352
13 com.presonus.studioone2 0x00000001075b45c6 0x107096000 + 5367238
14 com.presonus.studioone2 0x00000001075b4eed 0x107096000 + 5369581
15 com.presonus.studioone2 0x000000010759e050 0x107096000 + 5275728
16 com.presonus.studioone2 0x000000010759f878 0x107096000 + 5281912
17 com.presonus.cclsystem 0x00000001092de402 0x1092cf000 + 62466
18 com.presonus.cclsystem 0x00000001093634aa 0x1092cf000 + 607402
19 libsystem_pthread.dylib 0x00007fffb1426aab _pthread_body + 180
20 libsystem_pthread.dylib 0x00007fffb14269f7 _pthread_start + 286
21 libsystem_pthread.dylib 0x00007fffb14261fd thread_start + 13

Last edited by Deleted User; 25th March 2017 at 05:37 PM..
Old 25th March 2017
  #2
Never had a problem and I use SSD4 almost every day. This is NOT common IMO. What OS version, what computer how much RAM? Is this a hackentosh?
Old 25th March 2017
  #3
Deleted User
Guest
Quote:
Originally Posted by climber View Post
Never had a problem and I use SSD4 almost every day. This is NOT common IMO. What OS version, what computer how much RAM? Is this a hackentosh?
2010 MacPro Dual 2.4, 8 core machine, 14 GB Ram, running separate internal drive for the drums, same as the other drum stuff. I tried it int he documents folder too for giggles, same thing.

Sit there and click the crap out of the drums on the kit view and see what happens. Current Sierra OS X here 10.12.3

Im changing kits not he fly whilst its running a midi loop here and its staying up. If I stop he transport and click on the drums too long, whamo, so freakin weird. Ive tried diff mice as well as all diff USB ports to rule that out, same issue
Old 25th March 2017
  #4
Lives for gear
 
cavern's Avatar
 

Is it possible your SSD4 download is corrupt in some way. It happens.
Maybe Steven would authorize a new download given that you tried almost everything else, just to rule that out as well.
I don't get it cause mine runs fine on a much inferior machine than yours.
If all your other programs run well on your machine and SSD runs well on other people's machines, its conceivable that your download did not go as planned.
Old 25th March 2017
  #5
Lives for gear
 
tkaitkai's Avatar
 

Have you tried completely removing SSD4 from your machine and re-downloading + re-installing? If so, have you asked support for legacy installers?

Also, did you have the same issue on El Capitan or Yosemite? If not, do you have a machine running either OS where you could test this?
Old 25th March 2017
  #6
You have 14 Gig of RAM? How does that work? An 8 gig stick, a 4 and a 2? Don't those machines require pairs? I'll bet it has something to do with RAM! Do you have TechTools? I'd run some system diagnostics...
Old 25th March 2017
  #7
Deleted User
Guest
Quote:
Originally Posted by climber View Post
You have 14 Gig of RAM? How does that work? An 8 gig stick, a 4 and a 2? Don't those machines require pairs? I'll bet it has something to do with RAM! Do you have TechTools? I'd run some system diagnostics...
4
1
1
1 in both banks and that works fine per Apple and checks out fine per the memory check. My thoughts as well so I re seated them all and changed the 1 meg chips order just to make sure.

I don't have Tech tools here
Old 25th March 2017
  #8
Deleted User
Guest
Quote:
Originally Posted by cavern View Post
Is it possible your SSD4 download is corrupt in some way. It happens.
Maybe Steven would authorize a new download given that you tried almost everything else, just to rule that out as well.
I don't get it cause mine runs fine on a much inferior machine than yours.
If all your other programs run well on your machine and SSD runs well on other people's machines, its conceivable that your download did not go as planned.

Ive done the download 4 different times with a direct ethernet connection using Chrome and Safari here.

The downloads Unrar just fine and EVERY file says OK at the end of it
Old 25th March 2017
  #9
Deleted User
Guest
Quote:
Originally Posted by tkaitkai View Post
Have you tried completely removing SSD4 from your machine and re-downloading + re-installing? If so, have you asked support for legacy installers?

Also, did you have the same issue on El Capitan or Yosemite? If not, do you have a machine running either OS where you could test this?

yes, removed, trashed, re downloaded, re installed 4 times now.

Support points me to my account download which is what I used with the UnRar they say to use.

*Never notices the issue on the other OS because I never was clicking on the drum kit sounds, I just played them from the keyboard to check them out.

Im loading up a kit and clicking on the drums with the mouse.

**Crash DOES NOT HAPPEN when using the AU version of the plugin. However,
Im primarily Cubase and S1 here.

No other machine to check against mine.
Old 25th March 2017
  #10
Lives for gear
 
Lenzo's Avatar
Quote:
Originally Posted by shanabit View Post
4
1
1
1 in both banks and that works fine per Apple and checks out fine per the memory check. My thoughts as well so I re seated them all and changed the 1 meg chips order just to make sure.

I don't have Tech tools here
I had crashing issues awhile back. Freeware said the ram was fine. Took it to the genius bar and they had other software that determined that one stick was bad. Replaced it and no more crashing. You might want to pull a pair at a time and if the crashing stops with one of the pair gone, then you probably have a bad stick. If not, then ram is ruled out.
L.
Old 25th March 2017
  #11
Deleted User
Guest
Quote:
Originally Posted by Lenzo View Post
I had crashing issues awhile back. Freeware said the ram was fine. Took it to the genius bar and they had other software that determined that one stick was bad. Replaced it and no more crashing. You might want to pull a pair at a time and if the crashing stops with one of the pair gone, then you probably have a bad stick. If not, then ram is ruled out.
L.

Im swapping RAM around and trying all variations, getting interesting so far:

With just the Apple Ram, 6x1 GB chip=NO CRASH, slots 1,2,3,5,6,7

With just the Crucial Ram, 2X4GB chip=NO CRASH, chips in slots 1 and 5 or slots 1 and 2

Crucial 4GB in slots 1,5 with Apple Ram in 2,3,4,6,7,8 = CRASH

Crucial 4GB in slots 1,2, with Apple Ram in 3,4,5,6,7,8, = CRASH

Apple Ram in 1,2,3,4,5,6, Crucial 4GB in 7,8 = CRASH But most stable with them all together


CONCLUSION:

I HAVE A MEMORY ISSUE HERE!!.

Crucial RAM by itself is OK,
Apple RAM by itself is OK,

Any combo of Apple RAM and Crucial RAM will bring down SSD4 and my DAW when clicking on the kit. This issue never showed up till Sierra I might add. Yes Ive done PRAM reset and all that.

SOLUTION:

1. Run Apple RAM only for 6 GB
2. Run Crucial RAM only for 8 GB until I can do #3
3. Order new RAM in equal GB size for each slot.

GOOD RAM to get, www.MacSales.com?? Suggestions welcomed

**I will run Rember for giggles to see if anything shows up.
ODD that this RAM issue is ONLY affecting SSD4 in the VST plugin version. I think its a GUI connection with the SSD4 VST plugin and that interfacing calls to the RAM thats killing things.



***Thanks to Paul Hessing at Slate for pointing me to a hardware issue even though I didn't want to hear that

Last edited by Deleted User; 26th March 2017 at 05:15 PM..
Old 25th March 2017
  #12
Deleted User
Guest
Follow up on something I noticed:

The Apple 1 GB chips are 1 GB 1 RX8 PC3 10600E-9-10-D0, Chinese made
The Crucial 4GB chips are 4GB 2RX8 PC3 8500E-7-10-E0, Singapore

Shouldn't they all be the same speed?
Old 25th March 2017
  #13
Quote:
Originally Posted by shanabit View Post
Shouldn't they all be the same speed?
I would think so...

in addition, I really think that 16 GB of RAM is pretty the minimum for doing stuff with VI's. just bite the bullet or CC as it were and spring for 16 of nice matched RAM.
Old 25th March 2017
  #14
Mixing RAM can cause problems best to buy them as a pack.
Old 26th March 2017
  #15
Lives for gear
 
Lenzo's Avatar
You should be able to match up that Crucial ram. I would call them and talk to them about it...they might offer a return if it doesn't work...but it should.
L.
Old 26th March 2017
  #16
Are the Apple RAM ECC? also the latency numbers should match.
Old 27th March 2017
  #17
Deleted User
Guest
Quote:
Originally Posted by Jax Pok View Post
Are the Apple RAM ECC? also the latency numbers should match.
Looks like it the latency CAS numbers dont match of course. Im gonna order 16 matched or 32, havent decided yet

Looks like they are ECC, The Apple 1 GB chips are 1 GB 1 RX8 PC3 10600E-9-10-D0
Old 27th March 2017
  #18
Quote:
Originally Posted by shanabit View Post
Looks like it the latency CAS numbers dont match of course. Im gonna order 16 matched or 32, havent decided yet

Looks like they are ECC, The Apple 1 GB chips are 1 GB 1 RX8 PC3 10600E-9-10-D0
Get 32 be done with it
Old 20th July 2018
  #19
Lives for gear
 
macgee's Avatar
I've been having this crashing too of SSD on load kit and then when the daw opens too.
Also my machine would crash randomly strangely if the CPU was not being utilised - running the CPU actually prevented it so when logic was running
Just got new Samsung replacement memory (switched out crucial) and will see what happens. Hopefully this was the problem with SSD
Post Reply

Welcome to the Gearslutz Pro Audio Community!

Registration benefits include:
  • The ability to reply to and create new discussions
  • Access to members-only giveaways & competitions
  • Interact with VIP industry experts in our guest Q&As
  • Access to members-only sub forum discussions
  • Access to members-only Chat Room
  • Get INSTANT ACCESS to the world's best private pro audio Classifieds for only USD $20/year
  • Promote your eBay auctions and Reverb.com listings for free
  • Remove this message!
You need an account to post a reply. Create a username and password below and an account will be created and your post entered.


 
 
Slide to join now Processing…
Thread Tools
Search this Thread
Search this Thread:

Advanced Search
Forum Jump
Forum Jump