traynor_garnetHi,
I recently upgraded to EZD3. Loving it but my user kits are not saving properly. As soon as I exit the program, the drums I have assigned to each pad are not the same and my module (TD-17) is no longer the default. Any help? I saw another post like this here, but it was in the Superior drummer section and apparently I am not allowed to read it.
Thanks in advance
Hi,
I recently upgraded to EZD3. Loving it but my user kits are not saving properly. As soon as I exit the program, the drums I have assigned to each pad are not the same and my module (TD-17) is no longer the default. Any help? I saw another post like this here, but it was in the Superior drummer section and apparently I am not allowed to read it.
Thanks in advance
Bear-Faced CowIt’s not semantics but a lack of understanding how EZ Drummer works and MIDI in general.
It changes the midi note of my second rack tom to be the same as my first rack tom. If that isn’t changing “mapping” then fine, but it is changing the note. Why?
No, it’s not changing the MIDI note. It is grouping your rack toms. Again, this is because there are plenty of other MIDI related items that would sound rather empty if EZ Drummer didn’t group them. You don’t use them and that’s fine. However, plenty of others do.
You’d be changing your tune about grouping very quickly if your drum brain was output the MIDI note for a left kick drum where you only have a single kick drum and wondering why it is not playing.
Because the drum set I am looking at “doesn’t have a second rack tom.”
Irrelevant. Kits change from library to library. Again, were it not for grouping things would not sound right with respect to the other features you don’t use, yet others do.
On top of that, it leaves another drum (floor tom) unassigned on my kit because it “isn’t a rack tom.”
It’s not unassigned. If you were to check the map, you’d clearly see that it is expecting a MIDI note that you don’t have in your controller. This has never changed. And yes, a floor tom is a different grouping than a rack tom.
Assigning two of my pads to the same note because the picture only has one rack tom, while leaving another drum (floor tom) unassigned on my kit, seems silly to me and requires extra steps.
The graphics have zero relevance and again the other floor tom is not unassigned. Again, this is a lack of understanding of how MIDI works in general. MIDI is agnostic and EZ Drummer doesn’t know, nor care, the difference between your drum controller, a pad controller, a keyboard and MIDI data either from a DAW or groove file. This abstraction is what has made MIDI versatile for the last 42 years. It means that no matter where that note is coming from, EZ Drummer will play the drum kit articulation assigned to that note. The fact that your drum map has the brand name and model of your kit does not mean that EZ Drummer actually knows where it is getting its data from. It’s just a file name. It doesn’t know your drum configuration from someone else who does have two floor toms and three rack toms and perhaps five cymbals. It’s just a map that was made that’s common to what a typical user might have.
Your idea of auto assigning would have serious repercussions for everything else. That would mean any unassigned note on an 88-key controller would all of a sudden start firing notes they shouldn’t causing unpredictable behaviour. Even worse is when apps start remapping these notes (far different than grouping). Not only controllers, but grooves or MIDI data from a DAW. If you’re not seeing this, then the problem is deeper than is being displayed.
And seriously, changing a single MIDI note to work with your configuration is hardly an extra step. Even more so, you only have to do it once. To make it even easier, there’s a Learn button to quickly assign the note and you’re done. And if you save your intended kits as a project, it will automatically switch mappings. Easy as that.
And you’re right, it’s not a big deal to me because I have mapped far more MIDI notes than you will ever need to. Were it not for this, EZ Drummer wouldn’t be taking advantage of working Logic Pro 11 Session Players to its fullest. And switching between this to a regular mapping to a mapping that works with Reason or Maschine is nothing more than either a dropdown selection or a project change. Instant and no big deal.
jord
traynor_garnetYou are arguing against yourself and purposefully obfuscating my point. I know how midi works.
Have a good one
TG
Bear-Faced CowIf you did, modifying the map wouldn’t be such an issue with you.
Plain and simple.
jord
1
Thanked by: traynor_garnetNo products in the cart.