[traynor_garnet]

You were right.  Thank you so much for helping me out on a Saturday during the holiday season.  Much appreciated.

 

TG

1

Thanked by: Scott

[traynor_garnet]

Thank you!  I will try it.  I honestly thought the “product manager” was embedded within “My Account” where I can see everything I own and download updates etc.

TG

 

 

[traynor_garnet]

I am having exactly the same problem.  Installing EZ Drummer 3 on a second PC.  The program downloaded, installed, and authorized perfectly.  I then downloaded the EZ Drummer 3 core library, tried to install, and I am receiving the same message as above (missing files etc.)  The midi files from the Core Library also installed perfectly (as above).

 

Since I have the EZ Drummer 3 “upgrade”, do I need to also install EZ Drummer 2 on my second PC?  I was hoping to just do 3 and keep the disk space to a minimum as this second PC is not my main recording PC.

 

TG

Reply To: EZ drummer 3 Core Library Won’t Install version: 3.0.6

[traynor_garnet]

I tried this, but it didn’t work.   I’m not sure I understand the instructions.  The ezdp file I am copying IS my default project.  Copying and pasting it to the same file does nothing.

 

[traynor_garnet]

This has been driving me crazy!  I knew I was doing things correctly (it’s not hard to “set current project as default”) but it would never work upon startup.  If I manually load the program I called default, everything was perfect.

 

Pushing four years later and this still seems to be a problem?

 

I will try the above fix.  Hoping it works.

 

TG

Reply To: Set as Default Project not working version: 3.0.6
Operating system: Windows 7

[traynor_garnet]

You are arguing against yourself and purposefully obfuscating my point.  I know how midi works.

Have a good one

TG

[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

 

 

 

[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

[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.

[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]

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

 

[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

 

 

 

[traynor_garnet]

The problem is that the “default project“ is married to a particular set of  drums. If my default project uses a drum set that consists of two rack toms and a floor tom snare and base, the mapping doesn’t translate if I switch to a drum set that has one rack tom and two floor toms.

it seems that I have to save a number of projects that are married to a specific kit rather than having one default mapping that translates out perfectly to the various available drum kits.

TG

[traynor_garnet]

I looked into this morning. I don’t understand the relationship of “projects” and “drum kits.”

My e-kit is a Roland Roland TD-17KVXS:  5 drums (snare, two rack toms, one floor tom, kick) and 4 cymbals (hi-hat, two crashes, ride).  When I cycle through the presets it gets annoying because each kit seems mapped differently.  For example, when I play the basic pop/rock kit everything is mapped perfectly.  When I switch over to the classic rock kit (John Bonham kit), however, the drums don’t match up.  Both my ekit’s rack toms trigger the classic rock kit’s loan rack tom.  One of the two floor toms isn’t triggered by anything.

I can remedy this by remapping.  I use the “learn” feature to make sure each of my edrums is assigned to a different drum.  Now my first rack tom triggers the classsic kit’s only rack tom, my second rack tom triggers the classic rock kit’s first floor tom, my floor tom trigger the classic rock kit’s second floor tom. Viola!  All my edrums trigger a different drum.  For fun I switch the snare to another sound, and make my hi-hat foot pedal trigger a hi-hat tambourine.  Finally, I have John Bohnam’s kit all set up.  Now the tricky part:  do i save this as a project or as a kit (I have mapped and changed sounds)?

If I save it as a project, then change the drum kit, the mapping is all off on other kits (if the kits consist of a different drum configuration:  three rack toms and one floor tom for example).  If I save it as a drum kit, the next time a load this user kit the mapping is gone!

So my first question is:  what is the relationship of projects and kits?

To me it seems that all the pretty graphics of drum sets lead to unnecessary problems (both my rack toms trigger the same tom in one kit for example).  It also seems that calling things “projects” makes sense if you are song writing in ez drummer, but makes no sense when you are just using the program to trigger sounds (as I am).

I wish the configuration of the drum set stayed the same but the sounds could switch as I change drums sets.  In other words, every kit, be it jazz, metal, pop, or classic rock, would use the same (configuration, two rack toms and a floor tom in my case) but obviously the kits would sound different.

As it stands, I see no reason to save a user drum kit:  every kit needs to me married to its own unique “project” or else the match between my physical edrums and the virtual kit is broken.

TG

• The post has been modified 2 times, last modified 9 months, 2 weeks ago by traynor_garnet.

[traynor_garnet]

That worked perfectly!  Thanks so much.

 

TG

1

Thanked by: Scott

[Author]

Replies