No products in the cart.
Seems like there’s a limit of 16GB (16384MB) for loading samples into RAM.
My workstation has 64GB of RAM and I would really like to load all samples (incl. all Bleed) into RAM.
Is there any reason I can’t, a reason for this limitation?
I’m on Windows 10 Pro, Superior Drummer 3.2.1
Do you get an error message? Could you post it here? Which kit and preset are you having trouble with?
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)
The RAM usage indication in the top right of SD3 rises while loading a rig with All Bleed enabled on all microphones.
Once it reaches 16384MB (16GB) it suddenly drops down and loads again, for example to only 2870MB RAM Usage. No error message.
PS: I’m not having problems with factory presets. I’m making my own presets with All Bleed active on all microphones … and I route all microphones individually and raw to individual outputs because I want to mix the drums in Cubase, not in the SD3 mixer.
Are you working on these presets within SD3 as a plugin within Cubase? Does the same thing happen when you run SD3 standalone?
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)
I had 20GB kit once, so works here and I have 48GB men 🙂
Are you working on these presets within SD3 as a plugin within Cubase? Does the same thing happen when you run SD3 standalone?
Happens with both, Cubase plugin and standalone software.
As mentioned in the first post, I’m on Windows 10 Pro with 64GB RAM in my workstation.
Just tried again with Legacy of Rock. This ones 19.5GB
Then it looks like a Windows specific issue.
I’ve already tried on 2 studio workstations (Win10 Pro, one with 64GB RAM, the other one with 80GB RAM).
Loading until 16384MB … then poooof. 🙁
Have opened a support ticket earlier today, still no answer. Let’s see.
Then it looks like a Windows specific issue.
I’ve already tried on 2 studio workstations (Win10 Pro, one with 64GB RAM, the other one with 80GB RAM).
Loading until 16384MB … then poooof. 🙁Have opened a support ticket earlier today, still no answer. Let’s see.
Just to check, have you ran some memory diagnostic software and stress tested your RAM? Otherwise, like you say it could be a Windows issue, but unless someone else running windows has the same issue that can’t be confirmed either.
… like you say it could be a Windows issue …
I meant “an issue with the Windows version of SD3”.
I do some pretty heavy lifting on both workstations, not only audio production but also quite a bit of video post production. No issues.
Ok, I did some further investigation monitoring the actual RAM Usage vs. the RAM Usage display in SD3. Looks like it’s a bug in the Windows version of SD3 because the actual RAM Usage grows beyond 16384MB but SD3 seems to have a threshold in the RAM Usage display where RAM beyond 16GB isn’t just added but counted from zero.
Yes, the RAM load wraps after 16GB on Windows. The samples load fine but the display number resets to 0 after hitting 16GB. No it’s not supposed to do that 🙂
It’s been reported to the programmers and they are looking into the fix to be included in an update.
Scott Sibley - Toontrack
Technical Advisor
It’s been reported to the programmers and they are looking into the fix to be included in an update.
Thanks Scott for confirming this. I also received the mail regarding my support ticket.
Cheers
Martin
It’s been reported to the programmers and they are looking into the fix to be included in an update.
Now that was a quick fix even though it turned out to only be a cosmetic issue 🙂 Thanks a lot!
1
Thanked by: ScottNo products in the cart.
Get all the latest on new releases,
updates and offers directly to your inbox.
Note: By clicking the 'I WANT IN' button, you will not be creating a Toontrack user account. You will only sign up to get our newsletters, offers and promotions to your inbox. You can unsubscribe at any time from a link at the bottom of each email. If you want to learn more about our privacy policy, please find detailed information here.