[Bug] Dynamics of Kontakt instrumental is reset to zero after restarting Cubase

ToyosuY22 · 2024-04-07T02:43:31+00:00

There was an error rendering this rich post.

ToyosuY22

What I need

Could you tell me how to prevent behavior below or some workaround? Thanks.

How to reproduce

On Cubase 12, add an instrument track, and then select Kontakt 7.
Select any instrument. (e.g., Kontakt / Horn Ens)
Modify some parameters. (e.g., set Dynamics = 127)
Quit Cubase and restart it.
Open settings of that instrument again.

Expected behavior

All parameters of it are not changed. (e.g, Dynamics = 127)

Actual behavior

Some parameters are reset to default values (e.g., Dynamics = 0)

Possibility of reproduce

There are parameters to be reset and ones not to.
However, at least, the parameter "Dynamics" is always reset after restarting Cubase.

Environment

macOS Sonoma 14.4 (Apple M1)
Cubase 12.0.70 Build464 (Rosetta 2)
Kontakt 7.9.0
Data of instruments are saved in an external SSD.

Images

Find more posts tagged with

Apple Silicon

Bug

Cubase

Kontakt 7

Accepted answers

ToyosuY22

@Royal Tee

Thanks for your suggestion.

Unfortunately, the page you shared didn't help me, but in this case, I've just found that we can set the automation so that Dynamics gets 127 at the top of the event as a workaround for this issue.

I'll close this thread.

All comments

Jeremy_NI

IIRC the dynamics are assigned to modwheel (aka MIDI CC#1). Do you have any MIDI assignment to modwheel (or MIDI CC1) inside Cubase?

Can you also check if that still happens if you untick that box:

As explained in this article: KONTAKT's Volume Resets When I Press Play in my DAW

ToyosuY22

@Jeremy_NI

Thank you for your prompt reply!

However, unfortunately, the resolution you suggested didn't work. As I mentioned, please note that this issue will happen not after I press "Play" but after Cubase (DAW) is restarted.

Royal Tee

The solution is here:
https://forums.steinberg.net/t/kontakt-volume-gets-reset/130841

Right click to remove automation.

ToyosuY22

@Royal Tee

Thanks for your suggestion.

Unfortunately, the page you shared didn't help me, but in this case, I've just found that we can set the automation so that Dynamics gets 127 at the top of the event as a workaround for this issue.

I'll close this thread.

Quick links

Unanswered questions