[Simone Frau]

So, for the record, I kinda manually did it (spoiler alert: it’s a pain).

Like you anticipated, copying the preset in the other library’s folder is not reliable per se, and let me explain why:

• the instruments are placed where they fit, which can lead to only partially copying them.
• routing and mixer settings for default channels are a hit and miss, covering only the intersection between the two libraries
• user defined channels are routed and copied correctly

It seems to me it’d be so easy to just create user channels where the default channel are not shared between the origin and recipient library (and then again – why do we need a distinction between default and user channels?)

Anyway, here’s what I found to work best:

• copy the preset and take it from there
• replace the missed instruments
• add the missing channels as user channels with names matching the routing options for the instruments
• create channel effect presets and apply them on the new preset
  • also manually set the volume, which is not copied
• go to routing view and for each instrument do “auto-assign”
  • in most case this nails it

In general I think this could be easily improved on their side, adding the missing channels as user channels.

And now I am refining the midi drum map. God that’s another pain =D

 

1

Thanked by: onewayout_1

[Simone Frau]

I don’t see any error log in that folder actually…

[Simone Frau]

@Henrik said:
Having SD3 library and the “Default” Drums and Mixer preset loaded, if you directly in the articulations drop down menu press Crash a couple of times, then press Mute Hit (with both of them enabled) – does that stop the ringing from the Crash articulation?  

No, it does the same. I made a little clip that I am attaching, where there’s initially only a Mute Hit, then there is a Crash Hit immediately followed by the Mute Hit, and finally only a Crash hit. The Mute Hit by itself is dead silent, which is what I am aiming at; the Crash followed by the Mute hit has still a lot of ringing – not as much as the Crash Hit alone, but definitely noticeable. Maybe it’s something misconfigured on my side?

[Simone Frau]

Yes, it is turned on. I don’t understand why it won’t work – I made sure also that the MIDI messages are not aliases but exactly those indicated in the PDF midi map…I’ll try to make a video later at home.

[Simone Frau]

Yeah, the library is the SD3 core library, and the cymbal is 18″ Paiste 2002 Medium Crash. The articulations are Crash first and Mute Hit second – but really this worked with other articulations too (e.g. bow tip first) and other cymbals I tried.

[Simone Frau]

@Henrik said:
Yes, you need to import the tempo map that you have created in your DAW. Superior Drummer 3 can’t know about the DAW’s changes in tempo otherwise. It will still sound correct if you don’t import the tempo map and play from the host, with Follow Host enabled – but if you want to play from SD3:s time line, you’ll need the tempo map.

Alright, as I thought. But how does one import the tempo track? Wouldn’t it be possible to automatically keep it in sync with Cubase?

@Henrik said:
The Power Hand doesn’t add any hits to your MIDI groove, it analyses the groove and puts the Power Hand sign on the instrument that seems to have the prominent, leading playing. So even if you could remove the power hand sign, it wouldn’t change how the groove sounds! However, it makes it a lot easier for you to try other instruments as Power Hand, by dragging the sign…

Ok, then now I think it must have been my mistake, I probably modified the parameters so that it was adding hits.

@Henrik said:
If you want to loop an area, and sync that loop both in your DAW and in SD3 – you need to put the loop in the DAW – not in SD3! The DAW won’t “respect” the loop area in SD3 and follow that, but SD3 will follow the loop area of the DAW 🙂  

Noted 😉

[Simone Frau]

@Henrik said:
The mute tail isn’t just silence – it replicates the sound a cymbal makes when you mute it, i.e. it’s has a small ringing to it.

Right, but what I mean is different: the mute hit by itself has the right amount of tail, no question; the problem is if another (non muted) hit on the same cymbal happens right before, the subsequent mute hit doesn’t stop the ringing of the previous hit. I tried: if I start playing after the first hit and right before the mute hit, there’s no unwanted tail.
Of course I can – and will – set the length of the first hit from the MIDI editor, but still I imagine this should be handled automatically by SD3.

[Author]

Replies