ISSUE: The "Rimshot 1&2" sounds in the Cubase 14 Drum Machine only play at 127 velocity

Cubase
,
1

UPDATE: I just added some more information at the bottom of this post.

The “Rimshot 1” and “Rimshot 2” sounds in the Cubase 14 Drum Machine only play at 127 velocity, after saving and re-opening a project. If you have a pattern that triggers Rimshot 1 or 2 at any velocity other than 127 it will not audibly play after the project has been re-opened. Even the “Preview” button in the Drum Track pattern editor view won’t play the sound (the Preview button triggers the pad at 100 velocity, versus the pads in the Drum Machine view, which always trigger at 127.)

Observations:

  • These are the only Drum Machine built-in sounds I’ve encountered this problem with. (Kicks and Snares work fine, for example.)
  • You can’t remedy this by tweaking the velocity range in the pattern editor, because the “Min. Value” has to be at least 1 less than the “Max. Value” and even triggering at 126 velocity doesn’t work.
  • Both Rimshot 1 and 2 will work perfectly fine and normally when you first add them to a kit. It’s only after you save the project, re-launch Cubase, and re-open the project that the behavior occurs.

I have created a Cubase 14 project that demonstrates the issue. It contains a drum pattern that plays a kick on every beat, and then a rim shot #1 on the eighths. You will only hear the first rim shot, because it’s the only one triggered at 127 velocity. The subsequent ones in the pattern (125, 95, 64, respectively) are not audible.

The sample project is here: https://drive.google.com/file/d/1NFRLQJMciiXCNg72sRflIq4mwzSKPU_v/view?usp=sharing

Click the Download button in the upper-right corner of the screen to download the ZIP file.

EDIT: I forgot to mention, I’m running Cubase Pro 14.0.20 Build 240 (x64). I’ve had this problem in three different projects on two different computers. One running Windows 10, the other running Windows 11.

EDIT 2: Oh- it looks like it actually happens with both Rimshot 1 and Rimshot 2, but in order to see the problem you have to save the project and then re-open it. When you do that, the velocity problems I describe above will happen until you replace the pad with any other instrument. If that new instrument is a rim shot, it will work normally for the current session, but after you close and re-open the project, the velocity issue will return.

2

Without downloading your project I just played Rimshot 1 at different velocities on a Drum Track. Works like a charm.
Either there is something fishy with the project or with your install (preferences?).

3

I had neglected to mention the following (just added to my original post): I’m running Cubase Pro 14.0.20 Build 240 (x64). I’ve had this problem in three different projects on two different computers. One running Windows 10, the other running Windows 11.

I’d be very interested to see if that project works for you. I created it explicitly for this post.

EDIT: I updated my original post AGAIN, because it looks like the problem only happens after opening a project that has one of the Rimshot sounds in it. It doesn’t happen when you first create the kit.

4

Confirmed here. Win 11. Cubase 14.0.20
Created empty project with a Drum Synth Track and Rim Shot 2.
Add some Pattern’s that are less than 127 velocity to test.
Save, re load.
None of the hits less than 127 velocity will sound.

1 Like
5

Well, glad I’m not crazy.

It’s weird, right?

6

Yep, have the same here.
I think it is the Velocity to Level parameter of the Rimshot that doesn’t work correctly. It acts like a threshold.
As a workaround try setting it to minimum or slightly above minimum.

grafik
grafik150×213 6.57 KB

1 Like
7

I just saw the sticky post about how to submit a bug report. I renamed my thread to meet those requirements. Looks like a confirmed bug…