1. We noticed a different behaviour when using drum MIDI – small MIDI grooves are often dragged to the track where replace is needed. For example dragging down a 1 bar fill to the end of a verse – overwriting is more useful in those cases. But we have gotten some requests to have an option that it sometimes should move the blocks, like EZkeys (make it optional). We have taken notes of this in our todo-list for the future!
2. You can zoom with the mouse scroll wheel, but you need to press alt + scroll wheel (if you hover the + and – buttons right of the song track), you’ll see this info. The change from EZdrummer and EZkeys is made because SD3 has several areas where just scrolling the wheel without modifier means scroll down – the Grid Editor for example. The modifier key is necessary to keep consistency within the software itself.
3. This is the same reason, and behaviour, as point nr 1.
I know that it’s always better to be consistent between programs, and that is what we try to accomplish. However – sometimes we must do changes, because the new software has new features, the old way turned out to have a better way of doing it, or similar.
Thanks for the feedback! 
Henrik Ekblom - User Experience Designer
Toontrack
@Henrik said:
1. We noticed a different behaviour when using drum MIDI – small MIDI grooves are often dragged to the track where replace is needed. For example dragging down a 1 bar fill to the end of a verse – overwriting is more useful in those cases. But we have gotten some requests to have an option that it sometimes should move the blocks, like EZkeys (make it optional). We have taken notes of this in our todo-list for the future!2. You can zoom with the mouse scroll wheel, but you need to press alt + scroll wheel (if you hover the + and – buttons right of the song track), you’ll see this info. The change from EZdrummer and EZkeys is made because SD3 has several areas where just scrolling the wheel without modifier means scroll down – the Grid Editor for example. The modifier key is necessary to keep consistency within the software itself.
3. This is the same reason, and behaviour, as point nr 1.
I know that it’s always better to be consistent between programs, and that is what we try to accomplish. However – sometimes we must do changes, because the new software has new features, the old way turned out to have a better way of doing it, or similar.
Thanks for the feedback!
Henrik, thanks for taking the time to write.
1 and 3. I agree that in cases where the new block is shorter (e.g., a fill) then overwriting is a good default. If, however, one wants to insert a verse or chorus and the new block is the same length or longer, perhaps the default should be to move the existing blocks to the right so nothing is overwritten. Just a suggestion.
2. Thanks for the Alt+Scroll Wheel info.
Steve
