DRUMS interface – mouse click sends velocity 127, too high!

Superior Drummer 3 Help
Viewing 9 replies - 1 through 9 (of 9 total)
  • monospace
    Participant

    I too would like this option.

    Previewing at 127 does not give you an accurate impression of what a drum or cymbal would sound like in a normal work flow.

    E-drummer. eDrumIn trigger interface with various Roland trigger pads. MacBook Pro (mid-2015); MacOS High Sierra; Logic Pro X 10.4.8. Superior Drummer user since 2009.

    Mark King
    Participant

    You can open the preview pad which you can click from the bottom to top getting different velocities. The pad will stay on screen and work for the pad you have selected. Check the menus at the top. Sorry I can’t tell you exactly as I’m away for a bit and don’t have my DAW pc with me.

    SD3 with older sdx,s plus Rooms of Hansa and Death & Darkness. Cubase and wavelab current versions. Roland TD50x using all trigger inputs for triggering SD3 only. Windows 11 computer. Various keyboards and outboard gear as well as VST instruments. Acoustic drums: Yamaha 9000 natural wood and Pearl masters. Various snare drums. RME BabyFace Pro FS and Adam A7X monitors

    monospace
    Participant

    The problem is that you still have to select which drum you want to preview first, which then triggers it at 127. Ouch!
    When you right click a drum, it doesn’t play, but then you have to click out of the context menu first.
    Sometimes all you want to do is quickly click a few drums on your screen to hear how they sound together.

    The preview pad is definitely useful, but not in this particular scenario.

    It should be trivial to add a global preference for the interface volume.

    E-drummer. eDrumIn trigger interface with various Roland trigger pads. MacBook Pro (mid-2015); MacOS High Sierra; Logic Pro X 10.4.8. Superior Drummer user since 2009.

    Darin Kadrioski
    Participant

    A year and a half later with no solution 🙁

    How can this not be a problem for practically everyone?!

    1

    Thanked by: Andreas Dahle Aagård
    Paul Mueller
    Participant

    Not a solution: It is terrible behavior and I still am scared to click the drums with headphones on.


    Operating system: Windows 10
    Dé Palmeira
    Participant

    Why updates should take that long? I’m still waiting to be able to name midi regions the way I’d like.

    the spider
    Participant

    Has this been solved yet?

    Mark King
    Participant

    No but it’s not actually a bug. Feature requests on any program can take years to be implemented if at all. It would be a nice to have but I actually prefer to get full velocity as I know what the sound will be like. Something you can’t tell on lower velocities.

    SD3 with older sdx,s plus Rooms of Hansa and Death & Darkness. Cubase and wavelab current versions. Roland TD50x using all trigger inputs for triggering SD3 only. Windows 11 computer. Various keyboards and outboard gear as well as VST instruments. Acoustic drums: Yamaha 9000 natural wood and Pearl masters. Various snare drums. RME BabyFace Pro FS and Adam A7X monitors

    David Casas
    Participant

    Actually I’m annoyed by the fact that mouse clicks on the UI drums are not exactly 127 velocity but some value slightly below 127. You can check this if you disable randomize hits and adjacent layers for a drum, then click on it, then click the preview pad on max velocity, at the top. You will notice that the sample played back is not the same. I understand that this is intended as 127 would probably be too much to preview for most drums and cymbals when clicking on them.

    But yeah, it would be nice to have an option to set the mouse click velocity.

    Also ability to have multiple preview pads on screen would be useful.

    • This post was modified 1 year, 8 months ago by David Casas.
Viewing 9 replies - 1 through 9 (of 9 total)

No products in the cart.

×