Drum Map Mgr Needs MAJOR UPGRADE

Feature Requests here:
http://www.cakewalk.com/support/contact/featurerequest.aspx
 
Cheers...

sonar comes loaded with drum maps but if you need to make your own its actually very easy.
it takes a little while but once done, it can be saved and re used over and over again.
 
Addictive drums has one going around here some where on their site  (for download)
 
this is the best tut on making a drum map for sonar, treat it like gold
https://drive.google.com/folderview?id=0Bz8iPy9mIkNyX2dTcXRzSEVSUlNscXdETTROZTIyZw&usp=drive_web&urp=http://forum.cakewalk.com/Video-quality-m2949938.a&pli=1#
 
sonar info on drum maps
http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR%20X2&Lang=EN&Req=DrumEditor.04.html
 

Ah...I don't create hybrid kits these day so I forgot about the issue, but now I remember it. It's about the Out Port field not remembering the correct synth (out port) after you delete a synth that was listed before it, isn't it? I also want to see a new, modern-looking interface. Thanks for sending in the FR.

Have to say, I agree with everyone about Drum Maps.
 
Even though I use them in every project, and not just for drums, and I know how to create/edit/delete maps & presets without issue, I've probably spent more time on this than any other single activity.
 
An overhaul would be very welcome here.

I love drum maps but hate that I can't use the solo button.

Yup been banging on about it for years. This monstracity need replacing! (Used the M word to get more traffic ;) ).

Do this

1) Get rid of it from preferences and give it a dockable form. That way we will at least be able to audition changes on the fly.

2) Redesign the UI to be more like AD2 maps.

The only hard work development wise would be designing a slick UI. Most of the back end code already exists of course. It's a fairly simple job in the grand scheme of things.

This is meat and potatoes functionality ! :) Right now the meat is missing giving us a rather disappointing meal..

(Okay maybe remove the exclamation mark next time).

The work around that I figured out was the following:
Take a certain softsynth (SampleTank 3), as opposed to many different synths, like I used to do, and make maps for each "section" of drums.  For instance ST3 - Kicks, ST3 - Snares, ST3 - Toms, ST3 - Cymbals, etc.  This way if it disappears for whatever reason, which it will, when you need to use it again, you obviously know how to map it because the channel output #'s remain the same.  Also, what's cool about using this approach is you can use a LOT more samples for each "section".  So, here's an example.
 
In ST3 I set it up where I assign ALL 16 chs to my favorite drum kits, and that, more than likely, will give you more than enough samples for each "section". Then, create the maps and use whatever channels you need to assign to whatever, and however many samples you need for kicks, snares, toms, cymbals, etc.  Now, the only drawback is if you use the Sonar Step Sequencer then you'll only be able to use one section at a time; so essentially, you CAN'T use Sonar's Step Sequencer.  However, I DO believe that SampleTank has it's own step sequencer, as do quite a few other software synths.
 
So, until the developers at Sonar decide to AT LEAST take this OUT of the Preferences, and do MANY other updates, I'm afraid this is what we're stuck with.
 
BaDumpBump...PSSHH!
KC
 

andyhamm
 

I sure wish Cakewalk would focus on getting existing features working correctly before they add in more.  This is surely the most consistently buggy software I have ever used and I've been using this since Sonar 7, when I once had hair.

Amen Inc the hair bit.

Once you've built 30 or so , the process is fairly intuitive