once again there's some discussion about a drum editor ... since I have no experience with other sequencing apps, perhaps i'm missing the point of what some of you want to do in such an editor, BUT as a long time user of Notator/Logic, and being a drummer, I thought I'd describe my own process of drum editing and hope it helps some of you ... I use the transform editor extensively (and not just for drum programming) ... I have several velocity randomizing templates, set to various ranges, i.e, 54 - 63, 78 - 89, 101- 121, etc. ... very fast, very easy to limit processing to a limited section of a sequence, to a specific instrument, and especially to a specific sub-position ('select equal sub-position' is one of my favorites) ... and familiarity with the drum, percussion and other (mostly orchestral) samples I use, gives me a pretty good idea of what velocity ranges work in a given context ... in the Transform editor, randomizing note lengths and positions is equally effective for 'humanizing' functions ... if you're talking about something besides the controlling and humanizing of velocities, note lengths, and 'feel', i've missed your point ... i never use the matrix editor, and work in the drum mapping instrument rarely, only when i need to print drum parts hope this helps Steve Raskin http://members.aol.com/SRaskinNYC * * * * * * * * * * * * * * * * * * * * * * * * * * “the sea urchin roe was not arrogant at all in this dish” - Shinichiro Kurimoto, Iron Chef judge