[Wayne Anthony-Cole]

Dear Mr. Chillcot,

It’s clear like the rest of us here, you a level understanding of the complexities of the technology we are invested in.

Unfortunately you made a conscious decision to gaslight, & come with a series of conclusions neither I or previous persons had raised. Nobody is suggesting changes in SD just for themselves. SD is an amazing beast of a plug-in, & goes way further than any other in its class.

This is a *forum*.. An invitation from Toontrack (in this case) to engage with their customers for amongst other things, critique & some suggestions.

If you happen to disagree with a subject or posts within, might I suggest a little more decorum next time? It’s not that hard.

Reply To: New E-drum MIDI preset needed for every SDX version: 3.3.7
Operating system: macOS Ventura (13)

2

Thanked by: Mark King and Greg Busby

[Wayne Anthony-Cole]

You are right about the humongous variability of the library’s, but it not only a premium product, it’s also THE flagship drum library plugin on the market.

But I feel Toontrack are too smart a company to not solve this issue. It is a genuine problem & they do like to conquer difficult things. Creating different mappings for even kits with a particular library is counter intuitive.

Reply To: New E-drum MIDI preset needed for every SDX version: 3.3.7
Operating system: macOS Ventura (13)

[Wayne Anthony-Cole]

This is also my biggest bug bear with SD3. I flagged this same issue years ago.

I feel the whole mapping element needs re-vamping & SD standardised. To be able to set one map for ALL SDX’s & EZX’s

To be able to flit from one sound package to another  without re-mapping would be a dream. I honestly believe this is the way it always should have been.

As an extra, it’d even better would be if we’re able to further customise our maps globally across again ALL libraries.

 

C’mon Toontrack…..

Reply To: New E-drum MIDI preset needed for every SDX version: 3.3.7
Operating system: macOS Ventura (13)

1

Thanked by: Greg Busby

[Wayne Anthony-Cole]

Ahh, I did not know they had released EZD2 library. Oh well, here’s hoping!

Thanks Scott

Reply To: EZD 3 library version: 3.3.6
Operating system: macOS Ventura (13)

[Wayne Anthony-Cole]

Thanks for the reply Scott.

“Currently” seems to have me seeing this as NOT a “no, no way are we ever gonna do that 🙂

Grasping at straws here but if not as above – an alternative. How about the idea of a special EZD3 ‘back-grade for SD3 users?

Reply To: EZD 3 library version: 3.3.6
Operating system: macOS Ventura (13)

[Wayne Anthony-Cole]

I’m having the same problem.

I have every SD3 kit & EZX’s (except where they double).

Part of the problem is the mappings are different across libraries. I too wanna be able to to flit across libraries & presets & keep my own mappings. I have tons of other makers as well XLN Audio. Steven Slate, BFD3, Kontakt etc..

I simply want to be able to pick & choose say after I’ve captured the performance & not have my default library all over the place. I’m prepared to go through every library & preset if i have to just to get the user experience I think a high end product should have. I don’t think it’s too much to ask for.

Thanks

Reply To: cannot save custom midi mapping in SD3 version: 3.1.7
Operating system: macOS High Sierra (10.13)

• This post was modified 5 years, 2 months ago by Wayne Anthony-Cole.

[Author]

Replies