• Software
  • Spitfire Audio (SABLE STRINGS) Eats CPU
2015/02/17 05:13:52
reza
Any buddy here has issue with loading the sable strings? After I load violins and cello on my sonar x3e + some lighter samples the first core of my 8 cpu's core goes to max and makes pops and clicks. If I mute them, everything is fine but as soon as they start playing, problem comes back.
I have i7 +12GB RAM which after I load them, ram indicator on sonar shows 8GB ram already used.Can the lack of ram makes this kind of issues? 
I already changed the buffer size but still have the same problem.
2015/02/17 09:31:39
JonD
I don't have Sable, but have you tried turning off multi-core support in Kontakt preferences?
 
 
2015/02/17 13:58:46
reza
No , Honestly i even didn't know it. Shall I turn it off? Isn't better to be on to fully support mull-core?
thanks
2015/02/17 16:09:17
JonD
Yes, some Kontakt instruments perform better this way in Sonar.  So try it: Multi-core on in Sonar, off in Kontakt.
 
Also, make sure your PC's power profile is "High performance".  Surprisingly, this can have a big affect as well.
 
2015/02/17 19:10:24
reza
I turned off the multi-core in Kontakt even worst. I am not sure if the ram can cause this issue because i have 12 GB RAM and RAM indicator in sonar shows %70 of my ram already used.
2015/02/17 21:32:07
JonD
I took a quick look at the Sable Strings Kontakt info... How many articulations and mic positions do you have enabled for each instrument?  These use extra ram so that might explain your heavy memory usage.
2015/02/18 14:07:23
reza
really appreciate JonD for following up. I enabled all the mic positions but not all the articulations. last night i bought 1 4GB DDR3 and wanna replace it with 1 of my 2GB RAM, so my pc will have 14GB instead of 12GB RAM. I will post the result as soon as I run the project.
Thanks again
2015/02/18 14:45:03
Elffin
Please update.. I tried the free/demo version and to be honest it was extremley heavy latency wise. Any pointers would help... is this only evident with Sable or does it appear on other Spitfire libraries
2015/02/18 19:09:28
reza
I added 2 more GB RAM but problem didn't solve. I turned off the mic positions. problem solved . it is all about size of the samples. they are really heavy. but doesn't make sense to me because i do have a really high end powerful CPU and 14GB ram after loading them in full size cpu gets maxed out . i am not sure if it is just on sonar or also on the other DAW.
I really like the sable strings but have difficulty to use it :(
2015/02/22 21:42:57
Vastman
I have the full range of Albion and it operates fine. I load up several templates giving 32 to 64 tracks with no problem.
 
Each mic (different locations/mixes of the players) and each articulation is essentially another instrument/set of samples and until you get down Spitfire's magical 20 ways to do articulation switching and dynamics...which I still get confused over...you're probably better off to use one or two per instrument.  Separate instruments for other combos.
 
What is "a really high end powerful cpu" REZA? I'd suggest editing your sig to provide such info as it will always come up... 
12
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account