14

[Olof Westman]

The Stereo Reverse Mode in SD3 is not part of the presets but it is part of the
saved project along with such things as master volume and cache mode.
I.e. you set it once in a session and then you can apply any preset and
change SDXs and the stereo reverse choice will stick. This is how it also
works in EZ2 (and SD1) but in SD2 (and EZ1) it worked differently. SD2 had
no stereo reverse mode but a button that would reverse all panning controls
in the mixer. That state would then be part of a saved preset.

So, when you load your SD2 presets they will not set the state of the
Stereo Reverse Mode. If you have the Stereo Reverse Mode active
then it will reverse your preset and if that preset was already reversed
then you end up with no reverse.

>A bug?

So no, no bug. One of the changes between SD2 and SD3 that aren’t
100% compatible.

It could be that the best thing for you would be to load your presets in SD2,
stereo reverse them back and then save them again and load them in SD3.

Olof Westman - Toontrack
Coder

[Olof Westman]

Check this out
https://www.toontrack.com/forum/superior-drummer-3-pre-sales/sd3-software-only-purchase/

Olof Westman - Toontrack
Coder

[Olof Westman]

>the “workaround” of extending the recorded MIDI block is the way I did it…

When you bounce through the mixer there may be all sorts of effects like
delays and reverbs with feedback built in so that there will be potentially
useful sound long after the last voice has stopped rendering. There are
also plenty of effects that put out sound/noise of their own making it
impossible to generally detect when ‘the signal is gone’. That is why
we leave it up to you, the user, to decide how long you want the bounce
to be.

>…sometimes I will use the surround files. But for a stereo only production
> there is no need for these bounces…

True. I have been thinking the same thing myself.

Olof Westman - Toontrack
Coder

[Olof Westman]

>Anyways, it wouldnt matter surely as with Logic running the MIDI…

Err… maybe. SD3 runs at 44.1 internally, always. As soon as you run another
sample rate the incoming MIDI has to be converted to 44.1 samples. I should
think that there is a risk of some difference in rounding placing notes on adjacent
samples rather than on the same sample, occasionally.

However, there would seem to be some other issue here. Thanks for
finding out!

Olof Westman - Toontrack
Coder

[Olof Westman]

>…replacing the following WAV files in 48kHz 24-bit mono …

That would be 44.1kHz. (Not that we support hacking our resource
installation like that, in any way)

Olof Westman - Toontrack
Coder

[Olof Westman]

What sample rate are you running?

Olof Westman - Toontrack
Coder

[Olof Westman]

As long as SD2 can pick up the SD2 user presets then so can SD3.
I see no reason why installing SD3 should make SD2 forget about
where your presets are but the straight forward approach is to
go into SD2 settings and click on the “Set Path To Presets” button
and browse for the location of your presets. From your picture
I gather that it would be Glyph-1TB > Toontrack > Superior2.

Olof Westman - Toontrack
Coder

[Olof Westman]

In SD2 you can set the path to where your user presets reside.

Olof Westman - Toontrack
Coder

[Olof Westman]

Turn off ‘Randomize Hits’ and ‘Use Adjacent Layers’ and you will hear
the machine gun effect. Turn them on again and it goes away. There should
be an obvious difference if everything is working correctly.

Olof Westman - Toontrack
Coder

[Olof Westman]

Yes, that is harder to get around. You can get the stacks to work
but articulations other than the first won’t work until a fix is out.

Thanks for trying the workaround and confirming the nature of the issue!

Olof Westman - Toontrack
Coder

[Olof Westman]

>So is this due to be fixed in the 1st update?

Unclear

>With the workaround does this also work when I want to use
>the macros on another kit or would I have to clear them all again?

Once done the macros should be in better shape and you can
use them for other kits.

>If this is fixed would it then break the macros I have created?

I hope not…

Olof Westman - Toontrack
Coder

[Olof Westman]

Mark, I can reproduce your woes. It is a nasty bug. You can possibly
work around it using the following non-obvious method:

1. Select the kick and use ‘Search For Instrument’ to load one of the
SD3 Core lib toms in that position, instead of a kick drum.

2. Clear and remake your Macro knobs.

3. Save that as a preset. (knobs are now volatile)

4. Load that preset. (knobs ‘form’ according to the ‘kick’ and become resilient)

5. Change the kick back to a kick.

6. Save that preset and you are good to go.

Olof Westman - Toontrack
Coder

[Author]

Replies