User Kits won’t save properly

[traynor_garnet]

Hi, I recently upgraded to EZD3.  Loving it but my...

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

EZdrummer version: 3.0.6
Operating system: Windows 7

• This topic was modified 8 months, 1 week ago by traynor_garnet.

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

EZdrummer version: 3.0.6
Operating system: Windows 7

• This topic was modified 8 months, 1 week ago by traynor_garnet.

Topic

[Bear-Faced Cow]

If your drum mapping is consistent and won’t change. Saving a default project should suffice. If your mappings change, then save as different projects.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[traynor_garnet]

I’ll make it as simple as possible.

I made a default “program” with all stock Roland TD-17 mappings and a basic 5 piece drum kit.

If I switch to another drum set, such as the classic rock Bonham kit, both my rack toms will now trigger the lone rack tom on Bonham’s kit.  Why?  Why would my rack toms suddenly switch to the same sample/midi note?

To make it work properly, I need to make another “program” for the Bonham kit, let EZ drummer “learn” the triggers, then save this “program” with the Bonham kit included in the program.  But I switch to another drum kit within this program, all the mapping is screwed up again!

I cannot create an entire program for each drum kit.  At least, I shouldn’t have to.

TG

 

 

 

[Mick Avoidant]

traynor_garnet wrote:

I’ll make it as simple as possible.

I made a default “program” with all stock Roland TD-17 mappings and a basic 5 piece drum kit.

If I switch to another drum set, such as the classic rock Bonham kit, both my rack toms will now trigger the lone rack tom on Bonham’s kit.  Why?  Why would my rack toms suddenly switch to the same sample/midi note?

To make it work properly, I need to make another “program” for the Bonham kit, let EZ drummer “learn” the triggers, then save this “program” with the Bonham kit included in the program.  But I switch to another drum kit within this program, all the mapping is screwed up again!

I cannot create an entire program for each drum kit.  At least, I shouldn’t have to.

TG

 

 

 

I’ll return the simplicity favour. Your ekit has two toms; Bonham kit has one. EZD makes up for a missing drum or other instrument, by playing the nearest of the same kind. Both ekit toms play the lone Bonham tom.

Which expansion pack or EZD room are you working in?

[Bear-Faced Cow]

traynor_garnet wrote:

I’ll make it as simple as possible.

I made a default “program” with all stock Roland TD-17 mappings and a basic 5 piece drum kit.

If I switch to another drum set, such as the classic rock Bonham kit, both my rack toms will now trigger the lone rack tom on Bonham’s kit.  Why?  Why would my rack toms suddenly switch to the same sample/midi note?

To make it work properly, I need to make another “program” for the Bonham kit, let EZ drummer “learn” the triggers, then save this “program” with the Bonham kit included in the program.  But I switch to another drum kit within this program, all the mapping is screwed up again!

I cannot create an entire program for each drum kit.  At least, I shouldn’t have to.

TG

 

 

 

I think I see where this is going. From what I am reading from this you have two rack toms and one floor tom on your drum controller. When you change to the John Bonham kit, which has two floor toms, you are expecting that the rack is automatically going to be mapped to the floor tom. The mapping doesn’t work that way as the other floor tom has its own MIDI note assigned to it. To someone that does have another floor tom pad, this will work without issue and the situation you describe with the rack toms will apply to the floor toms when a person with two floor tom pads switch to a kit with one floor tom. EZ Drummer will map similar kit piece categories, such as rack toms, floor toms and cymbals, to the nearest working kit piece, as you have discovered. For kit pieces that have a MIDI note assigned to it, you need a controller to send the note to it. In your case, yes, if you want the rack tom to trigger the other floor tom, then yes you will have to assign it either on the controller or on EZ Drummer 3’s MIDI mapping.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

1

Thanked by: Shootie

[Shootie]

^^^Also why Edrum map presets are important and very handy.

EZD3 Tutorials | EZBass Tutorials | Toontrack themed FB Group | Toontrack themed Discord Group

1

Thanked by: Bear-Faced Cow

[Bear-Faced Cow]

What Shootie said!!

In this case, you would only have map it once and when you switch to the a kit similar to the Bonham kit (there are a few), you just load the map preset. If you save the kit with the map in a project, you will have the mapping you designated in the project.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[traynor_garnet]

Mick Avoidant wrote:

traynor_garnet wrote:

I’ll make it as simple as possible.

I made a default “program” with all stock Roland TD-17 mappings and a basic 5 piece drum kit.

If I switch to another drum set, such as the classic rock Bonham kit, both my rack toms will now trigger the lone rack tom on Bonham’s kit.  Why?  Why would my rack toms suddenly switch to the same sample/midi note?

To make it work properly, I need to make another “program” for the Bonham kit, let EZ drummer “learn” the triggers, then save this “program” with the Bonham kit included in the program.  But I switch to another drum kit within this program, all the mapping is screwed up again!

I cannot create an entire program for each drum kit.  At least, I shouldn’t have to.

TG

 

 

 

I’ll return the simplicity favour. Your ekit has two toms; Bonham kit has one. EZD makes up for a missing drum or other instrument, by playing the nearest of the same kind. Both ekit toms play the lone Bonham tom.

Which expansion pack or EZD room are you working in?

Bear-Faced Cow wrote:

traynor_garnet wrote:

I’ll make it as simple as possible.

I made a default “program” with all stock Roland TD-17 mappings and a basic 5 piece drum kit.

If I switch to another drum set, such as the classic rock Bonham kit, both my rack toms will now trigger the lone rack tom on Bonham’s kit.  Why?  Why would my rack toms suddenly switch to the same sample/midi note?

To make it work properly, I need to make another “program” for the Bonham kit, let EZ drummer “learn” the triggers, then save this “program” with the Bonham kit included in the program.  But I switch to another drum kit within this program, all the mapping is screwed up again!

I cannot create an entire program for each drum kit.  At least, I shouldn’t have to.

TG

 

 

 

I think I see where this is going. From what I am reading from this you have two rack toms and one floor tom on your drum controller. When you change to the John Bonham kit, which has two floor toms, you are expecting that the rack is automatically going to be mapped to the floor tom. The mapping doesn’t work that way as the other floor tom has its own MIDI note assigned to it. To someone that does have another floor tom pad, this will work without issue and the situation you describe with the rack toms will apply to the floor toms when a person with two floor tom pads switch to a kit with one floor tom. EZ Drummer will map similar kit piece categories, such as rack toms, floor toms and cymbals, to the nearest working kit piece, as you have discovered. For kit pieces that have a MIDI note assigned to it, you need a controller to send the note to it. In your case, yes, if you want the rack tom to trigger the other floor tom, then yes you will have to assign it either on the controller or on EZ Drummer 3’s MIDI mapping.

jord

Yes, this is exactly what I am getting at.  Why would the Bohnam kit map both my rack toms to the same note?  It makes no sense (who would want that).  Surely there must be a way to include a “never map to the same note” setting.  Personally, I would rather have the expansion patches just include a bunch samples, rather than being tied to an arbitrary and unnecessary visual presentation of different set ups.

To @MickAvoidant, I hope my “make it simple” comment didn’t come off as snarky.  I simply meant that this is one of those things that is 100 times harder to explain in words than it actually is.  I appreciate your input and taking the time to answer my question.  That appreciated also extends to everyone involved here.

TG

 

[Bear-Faced Cow]

As mentioned earlier, it’s making sure that there aren’t abandoned MIDI notes grouping them by category. It might not make sense to you, but it does to us when we’re using various MIDI grooves and controllers that fire those notes as not handling orphaned mappings would leave a hole in the grooves.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[Bear-Faced Cow]

Personally, I would rather have the expansion patches just include a bunch samples, rather than being tied to an arbitrary and unnecessary visual presentation of different set ups.

They aren’t arbitrary at all. In fact, it is highly functional for people like myself who use various maps on a regular basis. Perhaps, you need to understand how it all works together.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[traynor_garnet]

Bear-Faced Cow wrote:

Personally, I would rather have the expansion patches just include a bunch samples, rather than being tied to an arbitrary and unnecessary visual presentation of different set ups.

They aren’t arbitrary at all. In fact, it is highly functional for people like myself who use various maps on a regular basis. Perhaps, you need to understand how it all works together.

jord

Functional and arbitrary are two very different things.

It is great that it works well for you.  For me it is a big PItA  to have to create a new project and remap just because somebody decided to visually represent a drum set in a different way.

[traynor_garnet]

Bear-Faced Cow wrote:

As mentioned earlier, it’s making sure that there aren’t abandoned MIDI notes grouping them by category. It might not make sense to you, but it does to us when we’re using various MIDI grooves and controllers that fire those notes as not handling orphaned mappings would leave a hole in the grooves.

jord

Yes I get this, especially when working with a keyboard in which you have so many potential ‘triggers’  (88 on a keyboard!).

 

By remapping to the visual presentation (turning both my rack toms into the same sample/drum because the visual graphic has only one rack ton) it is essentially  ‘abandoning midi notes’  for me.

[Bear-Faced Cow]

It has nothing to do with the visual representation. I’m not sure where you get that. It has everything To do with the playability from all sorts of controllers, as well as the countless MIDI grooves that are available through both ToonTrack and 3rd Party sources. You’re feeling of “abandonment” is misplaced since you can easily create mappings of your own To respond to your controllers in anyway possible. The fact that something is not working the way you want it to bears no significance in this case because you can change it Into something that works for you. EZ Drummer 3 is hugely adaptable to any type of MIDI input. Not taking advantage of it is not a ToonTrack issue.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[traynor_garnet]

I’m glad it’s working for you.  I upgraded because version 3 was billed as being way more ekit friendly and the ability to instantly map to your specific ekit was a big draw.  The visual representation of the kit is quite relevant because it changes the mapping between your kit and the samples.  It isn’t as straightforward as it could be and makes switching kits more work than it could be.

I did need to spend more time with the software and I thank you and others for helping me get things sorted out.  Personally, I have very little interest in midi grooves or playing drums sounds from anything other than a drum set.  I recognize my interests are not the same as others.

Thanks for helping me work through this.

TG

[Bear-Faced Cow]

The visual representation of the kit is quite relevant because it changes the mapping between your kit and the samples.

No.. it doesn’t. The mapping never changes. The 2nd floor tom always maintained a specific MIDI mapping. It’s not any different when you are changing over to a library that has three racktoms. The mappings don’t change. In your case, your expectation of the rack tom triggering the other floor tom is what’s getting in your way.

I upgraded because version 3 was billed as being way more ekit friendly and the ability to instantly map to your specific ekit was a big draw.

It is far friendlier than EZ Drummer 2. EZ Drummer 3 has the ability to map to anything. It doesn’t mean that it is all automatic. Sometimes, it’s necessary to make it yours.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[traynor_garnet]

Bear-Faced Cow wrote:

The visual representation of the kit is quite relevant because it changes the mapping between your kit and the samples.

No.. it doesn’t. The mapping never changes. The 2nd floor tom always maintained a specific MIDI mapping. It’s not any different when you are changing over to a library that has three racktoms. The mappings don’t change. In your case, your expectation of the rack tom triggering the other floor tom is what’s getting in your way.

I upgraded because version 3 was billed as being way more ekit friendly and the ability to instantly map to your specific ekit was a big draw.

It is far friendlier than EZ Drummer 2. EZ Drummer 3 has the ability to map to anything. It doesn’t mean that it is all automatic. Sometimes, it’s necessary to make it yours.

jord

 

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?  Because the drum set I am looking at “doesn’t have a second rack tom.”  On top of that, it leaves another drum (floor tom)  unassigned on my kit because it “isn’t a rack tom.”  It is awesome that EZD3 has better integration than the previous two versions (I didn’t dispute that), but I think it could be better.  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.  Clearly it doesn’t to you and that’s cool.

Thanks again for helping me think this through and sort it out.   I think we have entered the realm of semantics and personal preferences so I am going to move on and enjoy the awesome sounds pounding out of my PA 🙂  I am loving EZD3 as my new “drum brain.”

 

TG

 

 

 

[Author]

Replies