Current Velocity Value doesn't show up

Is there any solution for this bug for now?
When will this be updated?

Hi,

What exactly do you mean? Velocity of what? Which window?

스크린샷 2023-08-07 오전 12.35.29
Velocity value on key editor

Hi,

Thank you for the screenshot. This is a known and already reported issue.

When will this be solved?

Hi,

I’m sorry, I’m not allowed to share this kind of internal information.

Isn’t it solved yet?

Hi,

Yes. As Cubase 13.0.30 has been released, I’m allowed to share the information, this has been fixed in Cubase 13.0.30.

This is not fixed yet.
When I enable lower zone key editor, velocity value doesn’t show up.
And If I select other controller lane and select velocity lane again,
then velocity value does show up.
Nevertheless, if i disable lower zone key editor and enable it again,
It doesn’t show up again…

Hi,

Could you attach a video screen recording, please?

It works on my side, here.

screen-recording

Hi,

Sorry, I don’t understand your video.

There is no MIDI data in the MIDI Part and I don’t see the Cursor. What would you expect to get/see, please?

When I press the note of the instruments, the velocity value has to be shown in real time.
But when I enable lower zone key editor, velocity value doesn’t show up.
And If I select other controller lane and select velocity lane again,
then velocity value does show up.
Nevertheless, if i disable lower zone key editor and enable it again,
It doesn’t show up again…

Hi,

Where would you expect to see the Velocity of the selected MIDI Note? It shows in the Info line, not in the Controler lane, the same way, as it was in previous Cubase versions.

Attach a proper video, with MIDI Notes and controllers, please.

I mean Not Selected MIDI note. The Pressed Note.
When I press note of a instrument, the velocity value should be shown in real time…
HERE
스크린샷 2023-08-07 오전 12.35.29
But Its not in Cubase13.

Hi,

OK, I got it, now. I can reproduce it.

When this problem will be solved?.

Hi,

Earliest in the next update.

When this will be solved?
How can you release a new version, without fixing this simple bug?

Hi,

This has been fixed in Cubase 13.0.30.