In the last step, you have to click the drop down again and actually select the new drum map file.
Then you can close the Drum Map Editor window. Select and open the previously extracted drum map file. Switch to the Drum Editor by clicking the button on the top left.Ĭlick the top drop down menu and select Open drum map editor from the list. Make a right-click on that MIDI event and select MIDI Editor. Drag and drop a random MIDI groove from the plugin into MAGIX Music Maker. Open Music Maker and assign the drum plugin to a track. You can find drum maps and instructions for these DAWs within the help section of this website as well. Other DAWs like Cubase, Reaper and Studio One have their own drum map file format. I have just been here to get myself up to speed on REAPER 5.2x and I thought I would join in on the conversation.Please note that this drum map file only works with MAGIX Music Maker. But then, you are probably not the apologetic type are you? In my opinion, you owe the OP an apology for side tracking the conversation with your giant LiCap animations that added nothing to solving their problem. If your just trying to be argumentative and prove me wrong - I don't care. If you are trying to impress me - I am not impressed. That doesn't make me an expert by any means, but I certainly didn't just fall off the turnip truck.
I've been at this a long time as a home recording enthusiast. So, the improvements to REAPER 5.2x were welcomed.
I now have to run that in a virtualBox as it is a 16 bit program (but runs fine on any 32 bit Windows).
The reason I didn't need to upgrade is because I have used a standalone MIDI Editor Cakewalk 3.01 which I purchased in 1995. The audio portion of REAPER suited my purposes just fine.
My previous license only applied up to version 3.78 which I have been happily using up until now because the main reason I would have for updating my license would be improvements to the MIDI editor, which were not up to snuff IMO until just recently. I have been using REAPER since version 2.x. Take a look over there <- at the date I joined this forum. Your demonstrating something completely out of context to do what? Nitpik and prove my statements weren't absolutely true? Impress me with your expertise? And, if the OP were using a custom setup, they probably would have (or should have) mentioned it. But the common user is going to use the method that's easiest for them. If your building your own specially designed multi out setup, knowing these things are important. Who on earth would do such a thing? From a practical stand point, why would anyone do such a thing? So, your adding tracks to otherwise perfectly working muti out scenarios. I use an Alesis DM10 kit for VSTi controller. Mapping, is telling MTPD which notes from your controller to use for which drum or cymbal. Make sure you are using either all or just channel 10. Now in that track control there is a listing for midi input. Note you need to have the new track "Armed" for record to be able to hear/monitor anything until you record some midi data. Drag MTPD to the empty space and a new track will be created for you. That should open your FX browser and list all of your VSTi. In your project Opposite Click on empty space under the track control in the track panel and pick Insert virtual instrument on new track. Make sure Reaper sees your midi controller: Options>Preferences>Audio>Midi Device.
Point to that by: Options>Preferences>Plugins>VST.
In Reaper you need to make sure that the folder that contains MTPD is seen by Reaper. MTPD uses midi channel 10 by default, so set your midi control to that. Try that and then see if it recognizes your midi controller. You should be able to run it all by itself. First off MT Power Drums will run in stand alone mode.