[Miscreant]

Thanks for this. Yes, this sounds like what I’ve been doing. It’s taken a lot of time, as the MIDI Property Box assignments do not carry over to other presets, unlike the MIDI In/E-drums assignments.

But once you’ve put in the time, it makes things way smoother: now I can just pull up a track template linked to a Superior preset, all my routing both in Superior and my DAW is right there, and I can either begin mixing the drums right away, or if already wet audition them in a mix.

[Miscreant]

Thanks for taking the time to reply. I appreciate your time.

I do understand the distinction between MIDI In/E-drums on one hand and the MIDI notes in the MIDI Mapping Property Box, where only the latter is ‘destructive’ re: Grooves functionality. I also understand that custom MIDI In/E-drums configurations can be saved as presets, remain active upon library changes, and can be saved as part of a default project state.

My concern is that I would like to maximize the degree of MIDI compatibility between different libraries. For instance, for quick auditioning within my DAW I would like to be able to drop a MIDI file currently on Track 1, Kit A into Track 2, Kit B and minimize the number of mismatches. These mismatches are possible because different kits have different pieces and articulations, and therefore sample x on CC 125 of Kit A might not match sample y on CC 125 of Kit B–that is, the MIDI Mapping Property Boxes of different libraries are not identical (even if similar).

The possibility of these mismatches left me with two options:

• accept a more limited degree of MIDI compatibility between different libraries (undesirable for my purposes);
• reconfigure the MIDI Mapping Property Box assignments to maximize compatibility between libraries

I took the second option by taking my largest, most diverse library (Superior 3 Metalworks, for example), remapped the ‘base’ MIDI assignments, and then took my other libraries and ‘fit’ their assignments into this master map. Even though this means more complex kits like Metalworks are not downwards compatible, all simpler kits are upwards compatible: every sample will match 1-to-1 (eg. ride bow = ride bow = ride bow).

Now, maybe I’m still confused. I surely know this took me a lot of time (not least because MIDI Mapping Property Box assignments cannot be saved independently and then imported into new libraries). But I cannot assume I’m the only one who’s gone this far to maximize compatibility between libraries…

[Miscreant]

Right now just n my DAW

Reply To: Clarification on (Custom) MIDI Mapping: a few q’s version: 3.3.6
Operating system: Windows 10

[Miscreant]

Thanks, everyone.

Re: velocity. Between the hits you’re hearing in the clip I posted, there is a maximum range of 7 between their respective velocities, but they average out relatively evenly. So I do not suspect velocity variance is the culprit, unless I am wrong about how sensitive the samples are to variances of on average 3-4 or so. Maybe I am wrong about that.

As for the kit, it’s the Tama Star Classic Bubinga in Metalmachine EZX, run through S3.

I’m going to revisit the gating to see if I can shape the envelope more to my liking, even if the ‘woofs’ are relatively random right now. If that doesn’t work I’ll use the envelope shaper in S3, though I do always want to see if I can do more with my standard, core mixing tools. So a bit of a bummer.

[Miscreant]

Thanks for chiming in, Bryan. I’m familiar with the envelope control here, and I do use it frequently. But I am actually wondering why the tom ‘woofs’ only after some rolls and not others. Any insight here?

Relatedly, I am trying to learn how to mix drums outside the virtual environment, where I do not have access to all the tricks available to me in Superior. How would someone handle this woofing on a real kit? I’m assuming with compression and gating, which I am already using.

Any other tricks anyone uses to control tom sustain and woofing?

Reply To: Toms ‘woofing’ on final hits of some rolls (audio attached) version: 3.2.4
Operating system: Windows 10

[Miscreant]

Yikes, that’s embarrassing…corrected file posted here. Thanks.

Reply To: Toms ‘woofing’ on final hits of some rolls (audio attached) version: 3.2.4
Operating system: Windows 10

[Miscreant]

Thanks, everyone. Gotta admit: solution is as simple as it is clever; but I honestly just didn’t think of it this way, as I was trapped in ‘this snare sound is part of this track’.

 

Thanks again.

[Miscreant]

No bites?

Reply To: Can I process just one layer of a sample? version: 3.2.4
Operating system: Windows 10

[Miscreant]

*Ba-bump*

Reply To: Custom kits: consistent MIDI mapping b/t kits; adding instruments + mic routing version: 3.2.2
Operating system: Windows 10

[Author]

Replies