By dtaa pla muk
Wed Jan 21, 2009 4:24 pm
os2xl's drum grid edit is treating me very well.
it took a day or two (and a lot of workflow/bug reporting) to get the drum grid edit where i wanted it to be, but i'm very pleased with the results of using os2xl's DRUM GRID + QUANTIZE STRENGTH % to push my drums where they need to be.
the "blockiness" of the DELETE option still throws me sometimes. if you try to delete a single note on 1/8th TC setting, you delete that TC value's "block" of data. this way, you can accidentally delete a note that is right next door to the one you're trying to delete. this is a little ungainly and i hope it will be resolved (so that a single note will be deleted instead of a "block")
however, with TC strength, i'm finding that i have to do a lot less EDITING and a lot more overdubbing.
i come from programming drums in MIDI grid edit, where in ithe ERASE screen you have to erase a range of notes instead of selected pads. i have forgotten how sweet it is to just casually/quickly delete a single pad's notes in a sequence from the ERASE screen just by tapping it and hitting DO IT.
i'm also a big fan, of course, of the ZOOM IN/ZOOM OUT in the grid edit. this is so important, and SO necessarily separated from TC settings.
back in os2 i never used DRUM tracks simply because i disliked the grid editing. i'm glad now because not only do i use DRUM grid edit, but it's even better than midi grid edit for DRUMS. midi grid edit remains the best for inst pgms and controlling non-drum external midi modules, but for drums, grid edit is best.
also, regarding simult, it appears that after stereo crossfade, simult will be examined. no promises, just the grapevine.
it took a day or two (and a lot of workflow/bug reporting) to get the drum grid edit where i wanted it to be, but i'm very pleased with the results of using os2xl's DRUM GRID + QUANTIZE STRENGTH % to push my drums where they need to be.
the "blockiness" of the DELETE option still throws me sometimes. if you try to delete a single note on 1/8th TC setting, you delete that TC value's "block" of data. this way, you can accidentally delete a note that is right next door to the one you're trying to delete. this is a little ungainly and i hope it will be resolved (so that a single note will be deleted instead of a "block")
however, with TC strength, i'm finding that i have to do a lot less EDITING and a lot more overdubbing.
i come from programming drums in MIDI grid edit, where in ithe ERASE screen you have to erase a range of notes instead of selected pads. i have forgotten how sweet it is to just casually/quickly delete a single pad's notes in a sequence from the ERASE screen just by tapping it and hitting DO IT.
i'm also a big fan, of course, of the ZOOM IN/ZOOM OUT in the grid edit. this is so important, and SO necessarily separated from TC settings.
back in os2 i never used DRUM tracks simply because i disliked the grid editing. i'm glad now because not only do i use DRUM grid edit, but it's even better than midi grid edit for DRUMS. midi grid edit remains the best for inst pgms and controlling non-drum external midi modules, but for drums, grid edit is best.
also, regarding simult, it appears that after stereo crossfade, simult will be examined. no promises, just the grapevine.



