No products in the cart.
Hi,
I made some drum tracks (MIDI) in Cubase with Addictive Drums. Now I want to change the drums and use EZDrummers DFH exp, but I want to keep the drum MIDI.
I have EZPlayer Pro and if I understood correctly there is a way of using the MIDI created with a different drum sampler and have EZPlayer re-map it automatically to work with Toontrack drums like EZDrummer.
What is the best way of doing this witohut having to re-program the drums?
Do I have to change the drum map in Cubase?
Thanks in advance,
Lars
PS accidentally I posted this over here, but I think it should be on the EZPLayer subforum, so I re-posted it there as well.
Win7 home prem 64bit i7 CPU 920 @ 2.67 6GB RAM Cubase 7, 64bit http://www.larsbauer.com/
AD’s snares are not conforming to GM as much as TT is , so,its a matter of editing not remaking the midi.
TT snares that are spread out to midi notes D2 D#2 E2 and perhaps F2 ,all need to be selected and transposed to D2 only.
In Logic this is as simple as pasting all midi regions together and the selecting D#2 and then select
” All Similar” to D#2 and just dragging down to D2 and then same with E&F.Perhaps you then just use your ears to listen if your hats and cymbals/toms are right but from what i remember its mainly the snares that were different.
Im sure PLayerPro will have a similar or better way to do it.
Thank you very much!
So, basically that’s what I already thought I had to do, to re-arrange the MIDI keys in the drum mpa. That’s what you are saying, if I understood correctly?
I just thought in EZPLayer Pro there might be an easier way of doing this, but maybe that only works the other way aorund (ie to make TT MIDI to be playable on Addictive Drums), but I don’t know.
Win7 home prem 64bit i7 CPU 920 @ 2.67 6GB RAM Cubase 7, 64bit http://www.larsbauer.com/
EZPLayer can do it, provided (1) you’ve stored the midi track in a folder on disk and (2) you drag that folder into EZPLayer’s window and declare it’s AD midi: all files from there will be remapped on the fly and can then be dragged to your DAW again…
ORIGINAL: Jym Feat
EZPLayer can do it, provided (1) you’ve stored the midi track in a folder on disk and (2) you drag that folder into EZPLayer’s window and declare it’s AD midi: all files from there will be remapped on the fly and can then be dragged to your DAW again…
Thank you very much !
I actually did exactly what you described above, but still it’s not right, some hits are nit correct, like one of the AD cymbals ends up as a tom in my DFH exp.
Probably nothing I can do about that, but do that manually. But then I don’t know what is the best way of making those manual fixes.
Maybe just to re-assign the MIDI notes in the drum map?
Win7 home prem 64bit i7 CPU 920 @ 2.67 6GB RAM Cubase 7, 64bit http://www.larsbauer.com/
in this case, here is the conversion table:
05 = 68 snare brush muted
26 = 66 snare brush short drag
28 = 66 snare brush short drag
29 = 66 snare brush short drag
30 = 66 snare brush short drag
31 = 67 snare brush full circle
32 = 66 snare brush short drag
33 = 67 snare brush full circle
34 = 68 snare brush muted
35 = 68 snare brush muted
37 = 40 snare rimshot
38 = 38 snare right
39 = 40 snare rimshot
40 = 38 snare right
41 = 40 snare rimshot
43 = 33 snare left
44 = 71 snare rim only
48 = 44 HH pedal
49 = 42 HH closed
50 = 22 HH closed edge
51 = 42 HH closed
52 = 22 HH closed edge
53 = 119 HH closed bell
54 = 24 HH open 1
55 = 25 HH open 2
56 = 26 HH open 3
57 = 60 HH open max
58 = 121 HH open bell 2
59 = 23 HH foot splash
65 = 43 floor tom head
66 = 75 floor tom rim
67 = 45 rack tom 2 head
68 = 78 rack tom 2 rim
69 = 47 rack tom 2 head
70 = 80 rack tom 2 rim
71 = 48 rack tom 1 head
72 = 82 rack tom 1 rim
45 = 51 ride cymbal tip
46 = 49 crash cymbal
60 = 51 ride cymbal tip
61 = 53 ride cymbal bell schank
62 = 59 ride cymbal crash
63 = 118 ride cymbal mute
77 = 49 crash cymbal
78 = 54 crash cymbal mute
79 = 57 ride cymbal crash
80 = 58 ride cymbal mute
81 = 52 ride cymbal crash
82 = 83 crash cymbal mute
Wow !
Thank you !
Where did you find this table?
And how do I use it, what do the numbers refer to?
Win7 home prem 64bit i7 CPU 920 @ 2.67 6GB RAM Cubase 7, 64bit http://www.larsbauer.com/
those numbers are midi note numbers: for instance, 37 is D#
note that I don’t know what a DFH exp is: I thought you were using EZd or SD
ORIGINAL: Jym Feat
those numbers are midi note numbers: for instance, 37 is D#
note that I don’t know what a DFH exp is: I thought you were using EZd or SD
Thanks !
By DFH exp I mean the Drumkit From Hell expansion for EZDrummer.
Win7 home prem 64bit i7 CPU 920 @ 2.67 6GB RAM Cubase 7, 64bit http://www.larsbauer.com/
ah, just look up the keyboard layout for the drumkit from hell EZX and check whether the midi notes match… it will be easy to correct the offending drums!
ORIGINAL: Jym Feat
ah, just look up the keyboard layout for the drumkit from hell EZX and check whether the midi notes match…
OK !
Once again, thank you very much for your help. I appreciate it!
I also have SD2.0 and DFHS as well as Addictive Drums, but now I realized that mixing drums myself (as I tried to in SD2.0 and AD) is not really what I want to be doing in thep rocess of writing a song, so for that it’s easier to use the pre-processed sounds of EZDrummer and the expansions.
Win7 home prem 64bit i7 CPU 920 @ 2.67 6GB RAM Cubase 7, 64bit http://www.larsbauer.com/
Hi – I read through your topic and I can’t identify the problem… our translation maps are definitely correct and should play back as expected regardless of which AD revision you used to program these tracks (version 1.1, if I recall correctly had some additional assignments).
Could you upload a sample MIDI file, and a short audio extract rendered with AD so I can check what’s going on?
Rogue Marechal - Toontrack
Configuration Manager
Hi Rogue,
Thank you.
The problem was that even after using the translation mapping of EZPlayer some hits were still wrong (like a snare rimshot would become a rimclick, or some cymbal would turn into a tom or something like that), but I guess that is normal? or maybe I did something wrong.
Anyway I already reprogrammed everything in EZDrummer DFH, but I still uploaded a MIDI (created while using AD) and an AD-rendered file (very low quality and mono so it would be less than 200KB for the upload) for you to check.
Thank you very much!
Lars
Win7 home prem 64bit i7 CPU 920 @ 2.67 6GB RAM Cubase 7, 64bit http://www.larsbauer.com/
nothing unexpected in kit-piece triggering when operating EZplayer as stated above: snare rim shots are just that, crash 1 and 2 also, tom 2, 3 and 4 are rim shots like they should ; everything is properly remapped… even though EZdrummer does a bit of translation by itself, remapping tom 3 to tom 2 if the kit has only one floor tom
in fact, I’ve been using groove patterns from SSD 3.5, OddGrooves, FXpansion BFD, Groove Monkee, XLN Audio, you name it : EZplayer never failed…
perhaps you’ve missed the step where the source mapping is selected : see section 6.1 in the manual ; also, be careful to select the format in the map wrap menu according to the target plug-in : this is unclear in the manual, section 3.2, but EZdrummer is the default, and if you select something else, it might well trigger yet another set of conversion rules!
ORIGINAL: Jym Feat
this is unclear in the manual, section 3.2, but EZdrummer is the default, and if you select something else, it might well trigger yet another set of conversion rules!
hum, no, the default is not to transform the MIDI, aka as ‘Thru’. I’m not sure I understand what you meant though, and maybe it is important to clarify how EZplayer works herein, with a flow summary:
Input format -> GMExtended -> Output format
the Input format in this instance is AD, and should be declared when creating the mount point. The Output format would be EZdrummer which is in effect a null transformation (in other words selecting Thru in the Map Wrap menu of the browser or arranger would make no difference).
… maybe that is what you meant in which case you are correct (but can only add to the confusion when conveyed in that manner).
Rogue Marechal - Toontrack
Configuration Manager
yes, this is exactly what I meant: section 6.1 deals with the mount point creation (which handles the source format) while section 3.2 deals with the target sampler — EZd and its big brother beeing the default…
as a matter of fact, I was trying to nail the reason why cymbals would become toms, and I reckon these are the only crucial sections — sorry for the confusion!
No products in the cart.