10

[Olof Westman]

You would have to Add the same snare as a new Instrument (X-drum).
Then you would deactivate all its articulations except the SideStick and
assign the proper MIDI notes to it. In the normal snare you would then
deactivate the SideStick articulation. Then you route the mics of the
new snare to your liking, probably creating a few new mics in the mixer
in the process.

Olof Westman - Toontrack
Coder

[Olof Westman]

I think they are all 16/44 except String Machine which is 16/88.
At least, I know Studio Grand is 16/44. Note that the sounds
are not raw but somewhat processed so 16bits is not that bad
considering that that’s what you put on a CD anyway.

And it is looped, after about 8 seconds, and that means that you
won’t hear the sounds ‘farting out’ at the very end due to the
bit depth.

Olof Westman - Toontrack
Coder

[Olof Westman]

>..looking in the Manual i could not find any information concerning this setting ..

9.3.3 Settings Window Performance Tab

We have no reports of problems using multi-core with Cubase as host.
John mentions Reason and Reason is the only host we know about, right now,
for which you cannot use multi-core in SD3 without first disabling it in the host.

Start out by running SD3 on 1 core only. If you experience glitches you
can try to raise it to 2 and see if that improves the situation. Ultimately you
are in control. You can use any value that works for you. What values those
are depend on the host, your hardware and the sort of projects you run.

Olof Westman - Toontrack
Coder

[Olof Westman]

CPU usage for the sampler engines in SD2 and SD3 is very similar if not identical.
SD3 also offers to use multiple cores.

Olof Westman - Toontrack
Coder

[Olof Westman]

>>Using 236 on a 250 SSD is usually not recommended:….

In your quote, note:

>>You’ll see write performance start to slow down as you go above that mark

Nothing bad happens to your read performance and reading is all you
do from that disk.’

>Get a bigger drive for the drums, you need the drums to react quickly.

Also, the disks performance affects the loading time of the drums not
how well they play.

Olof Westman - Toontrack
Coder

[Olof Westman]

You cannot apply the wisdoms of gaming here. In the audio world low latency is accomplished by having a soundcard with native ASIO drivers and running it with as small a buffer as possible. The better CPU and RAM you have the smaller buffer you can run, so a reasonably good rig is useful too. I guess similar rules, as in gaming, apply for all the stuff you need to turn off in Windows in order to make sure that resources aren’t suddenly waisted on something irrelevant.

So, try a soundcard with native ASIO support. Borrow one. It doesn’t have to be an RME.

Here is a good page https://help.ableton.com/hc/en-us/articles/209072289-How-to-reduce-latency

Olof Westman - Toontrack
Coder

[Olof Westman]

There is a bug in ‘Level Envelope Releases’ for S3.0.3, and earlier, making it not affect the Curve Slope of the envelope. I found that out thanks to this thread back in November, 3 months ago. After I read the first post here I tried to damp some drums in SD3 for the first time and found out that the results were far from what I expected. Once I fixed that bug the problems went away.

The method I used was pretty much what John is hinting at:

1. Solo the close mic/s of the drum and put in an EQ that reduces its longest ringing frequencies.
2. Put the drum in question on its own new AMB mic. (Route Instrument Microphones)
3. Move that EQ to this new AMB mic.
4. Enable the ‘Envelop and Offset’ for the drum and dial in a Release value below 2s.
5. Adjust the ‘Curve Slope’ until the drum is as damped as you want it.
6. Go back to the new AMB mic and extend the ‘Level Envelope Releases’ until the room is wet enough.

That last step doesn’t work until you get an updated SD3 with that bugfix.

Olof Westman - Toontrack
Coder

[Author]

Replies