[Dave_26]

Performance will always be better when you put sample libraries on a different physical drive than your OS drive. That being said, if you have enough RAM and don’t have a lot of constant swapping around to do with your drum kit, once you load it, it’s not some horrible awful thing if your samples are on your OS drive.

I have a mid 2014 MacBook Pro with my SD3 library installed right on the internal 1 TB SSD and it works just fine.

[Dave_26]

Thanks much. That’s great to hear.

[Dave_26]

I am the original author of this thread/post, so I’m not sure why you’re talking about me in the 3rd person unless you truly weren’t aware of who the original poster was and that I just replied to you.

And I can appreciate that someone who doesn’t know much about SD3 and is unaware may like hearing another way of working, so your suggestion may have benefited others and thank you for trying to help.

I did, though, mention exactly “I know staying in SD3 permanently is an option, it’s just not one that I desire” so it wasn’t something I was looking to get convinced about otherwise.

If anyone else has stories to share about they ways they’ve exported from SD3 for good mixing control after-the-fact, I’m still all ears and would love to hear.

For now it seems like changing what’s bleeding into the OH stereos and even doing multiple exports of OHs stereo pairs with different instruments in them at a time is probably going to be the way to go for me.

1

Thanked by: cydemind

[Dave_26]

I’d think it would be obvious that there are a ton of reasons any user may desire to leave SD3 after completing programming

• Not everyone we collaborate with has SD3 and everyone needs to be able to open the session and hear and tweak
• If a mixing engineer other than us is hired, that person will surely not want to use SD3
• We don’t want to have to go into the SD3 plugin UI just to rase the volume of the kick drum in the future
• We want to use individual plugins within Pro Tools to process different parts of the kit
• We don’t want to make sure we have an old system compatible with SD3 just to open this session and change something about the mix of the drums 10 years down the line
• Tons of reasons why printing to actual audio once you’re done is useful. Very useful

[Dave_26]

Thanks for your reply. Yeah after posting this I watched a video about taking cymbals and hat out of the OH dyn and only having them in the OH cond.

And of course all the combinations of that sort of thing – amb stereos as well depending on what you have loaded, etc.

I’m realizing there are just so many options and I’ve got to figure out what works best for me.

I’m partially thinking it would be great to make multiple versions of the OH dyn and OH cond – so that I can dial in exactly what I want of everything once I’m in PT. But I could also go down a major rabbit hole with that for not a lot of return in the long run.

The issue is balancing how much I want to be able to tweak with how long that takes to achieve endless printed options — and how much those options will just clutter things.

Maybe I need to just do the minimal and have more faith that these kit sounds have been extremely well-crafted already.

Lots to learn in SD3! Still been using for just a little over a year. More to go.

Anyone else have helpful suggestions, too? 🙂

[Dave_26]

Thanks for the reply, John. It was a while ago that I thought I was having the midi import issues and decided to ask for help before trying again.

But now I honestly don’t know if I was just not noticing that the meter changes were actually importing and are sort of not displayed very well in the GUI or if I was really experiencing a problem.

Regardless, I’m now retreating with embarrassment because I do see that it’s working now.

I’m thinking that the fact that importing a meter map into a blank “track” in SD3 doesn’t exactly show up very well in the GUI is probably what was happening and I probably just didn’t realize that it was working.

Apologies if I’ve ended up crying wolf!

Will report back if I somehow see it happening again as I continue to work. And I’m on 3.1.4, FYI.

• This post was modified 5 years, 9 months ago by Dave_26.
  Reason: typo

1

Thanked by: John

[Dave_26]

Support helped me now solve this by trashing the file called “MidiDB” that’s in the USER’s Library/Application Support/Toontrack/Superior3/OnlineMidi folder. Make sure you go fully into the OnlineMidi folder to trash the MidiDB file in there and NOT in the parent folder called Superior3

You may have to keep trashing this file and restarting SD3 whenever the issue occurs.

[Dave_26]

Still a problem. Even when using Superior Drummer 3 in standalone mode instead of as a Pro Tools plugin. And I have an internet connection speed of over 200 mbps down and everything else having to do with the internet is functioning quickly and without problems, so it can’t be my connection.

[Dave_26]

Same here. I bought the full new version of SD3 from sweetwater.com and installed and registered yesterday.

I emailed a support ticket about the NY SDX Vol.1 not appearing in my account yet, but haven’t gotten a response.

[Author]

Replies