Jason Moore LAcReposting from an earlier thread due to changing circumstance:
So…. I am fairly new to SD 3 (covert from EZ Drummer). I am using Studio One. Early 2015 MacBook Pro 8 GB RAM. 2.9GHz Dual Core I5 processor.
All libraries are on a 1TB external SSD with 3/4 of it empty. Internal HD is 512 GB SSD with only 125 GB on it.
I was having no performance issues at first.
I recently discovered mic bleed and the ability to turn on surround channels. Now I have a horrible glitch issue but it’s only in the one track I am working on that has all of the mics and bleeds turned on. I have completely optimized my system. I have done everything in the world that could possibly free up more space. I am thinking to buy a new MacBook that is supercharged but I don’t think I really need to because all other tracks and drum configurations (I’m working on 11 different tracks at the moment) are working totally fine.
When looking at the performance monitor in Studio One I can see that SD is fluctuating between 20-30% of CPU usage. CPU Usage in Activity monitor however shows Studio One at over 100% on this track. Now for the interesting part……
At first I went into activity monitor in my Macbook and I see that studio one is taking up about 40% and FONTD is also taking up 40-50% ONLY during the tracks that’s giving me fits. On all other tracks Font D is completely irrelevant.
That problem then went away. No more FONT D issue. I emptied the cache anyhow (at advice from my earlier post) but nothing changed. FONTD now not an issue.
I can use mic bleed without the surround libraries no problem.
What I am seeing now is this.
10 out of 11 tracks are fine.
The one that has surround with mic bleeds throws Studio One into over 100% CPU usage.
Yes, I’ve tried changing Cache settings in SD3. Yes, I have done everything imaginable to free up space, RAM, and optimize my computer.
I have disabled AU, VST, etc…. to track it down. It is absolutely the SD3 plugin.
What’s interesting is that CPU usage of SD3 shows to be around 20-40%. BUT….. Studio one bumps up to over 100% from abut 30-40% with SD3 enabled (after disabling it).
I am stumped. Something about mic bleed and surround is killing my CPU
This is ONLY an issue when mic bleed is turned on in most of the channels, including surrounds. It’s not an issue at any other time. It’s not just an issue when the files are loading…. it continues throughout the track even if I play it over and over again.
BradSo I guess I didn’t read your entire last thread or missed the specs. I loaded Studio One, SD3 only and enabled all the bleeds on the surround channels and am using up 14.5 GB of RAM memory. So on an 8GB RAM machine, there’s a lot of huffing and puffing going on that poor processor trying to juggle memory in and out of swap space.
So far I would say RAM may be an issue. Is there an opportunity to upgrade the RAM on that machine?If it’s anything like my old 2013 MBP, there answer is no. YMMV.
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)
1
Thanked by: Jason Moore LAcJason Moore LAcCool. Thank you for doing that, Brad!
Unfortunately no. The machine I am using was upgradable to 16gb but only at purchase. They soldered the RAM to the logic board and it is forever 8 GB. I could theoretically get a new (used) logic board that has 16 GB on it but at that point I would rather just get a new computer.
It sucks….. but I’m a little comforted to have a good idea of what’s going on rather than keep chasing possibilities. I kind of figured that was it and have been pricing new MacBooks but I wanted to make sure it wasn’t something more simple.
Thank you again for all your help! This forum (and software) rocks!
BradYes it’s the same with my old MBP, memory soldered on the board. Fortunately I don’t use it for audio.
Sorry I didn’t have better news.
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)
1
Thanked by: Jason Moore LAc
ErikHey Brad,
You could work around this in two ways, both from the memory details menu. The first is to enable 16-bit mode, the second to instead use cached mode. In both cases, once you’re happy with the drums, you transform the instrument track to audio in Studio One (or bounce/export it in Superior Drummer if that doesn’t work). Unloading instruments or articulations you know you’re not going to use is also an alternative.
You can read more here about the ups and downs of either method:
https://www.toontrack.com/manual/superior-drummer-3/11
Erik Berglund — Toontrack
1
Thanked by: Jason Moore LAcJason Moore LAcThank you for this, Erik.
I just used it as an excuse to get a faster Macbook
I’ve already invested about $2,000 in EZD, SD3, EZX, SDX, MIDI Packs….. I’m not holding back now because of a RAM Issue 😛
Seriously though… Thanks again. I love the support and willingness to work with the user of Toontrack and the community in the forums. It’s great!
No products in the cart.