There some tracks where drawing a CC curve with the new Cubase 11 ramp tool works. But some others where it does not.
I made a video. The curve of CC11 is not read. Only the points. And the displayed value is frozen at 0.
https://drive.google.com/file/d/1foLOrQndXKOqzwbzK0p_zDkXrxvbP4Kg/view?usp=sharing
Hi,
Do you mean the MIDI CC11 in this case?
Would you be willing to share a snipped of the project (only this track, this one MIDI Part), please? I can’t reproduce it here on my side so far. Thank you.
Yes MIDI CC11. The VST loaded is Kontakt. Strangely if I replace the VST by another one like Dune, it works.
https://fromsmash.com/EGt6ktNujV-ct
Hi. I downloaded the project and am experiencing the issue you have discovered.
I have experimented a bit. If you duplicate your instrument
track it breaks kontakt on my end. The volume and pan controls go haywire on the original and the duplicate.
Interestingly if I make a kontakt instrument in this project and manually recreate your two notes and cc data with kontakt and SSS violin 1 legatos it works fine and the controllers move monthly on the ramp.
What version of kontakt are you using?
Kontakt 6. I am not at the studio so cannot tell about the exact version. Some Kontakt libraries work while some other do not.
So you also experienced that there is a bug?
Hi,
I can also reproduce it here with the attached file. Reported to Steinberg CAN-32769. Thank you.
Hi,
The problem is, the track’s channel is set to Any. The Ramps/Curves of MIDI CCs are not supported in this case.
1 Like
I tried by setting a midi channel. It was the same
Hi,
The MIDI Channel on the track, directly? Could you add a screenshot, please?
Hi,
I had the same issue, and what is said above is true but imcomplete in my case.
Changing the MIDI channel of the instrument track from ANY to 1 will allow newly created MIDI parts to use ramps, but not existing ones. Is it intended, or a bug, or because it’s a project created in a previous version of Cubase, I have no idea.
So for the record, and for people who might bump later on this issue, you need to change the MIDI channel, duplicate your MIDI parts, then remove the old ones. That’s the only way it would work in my project.
Hope this helps!
2 Likes
Hi,
Reported to Steinberg. Thank you.
1 Like
I know it’s 2024 now, but this thread has just relieved me from weeks of headache, after I had started to dive deeper into these continuous curves for orchestral programming and was not able to decipher why these were causing CC jumps on some but not on all tracks regardless of the vsti. Turns out having changed the midichannel to “all” on some tracks for articulation-switching was exactly the cause.
And I am basically just here to say a heartfelt thanks to you and the ones involved in this thread.
The only maybe at least slightly useful information that I can provide for others is that this behavior discussed above is still a thing, also in Nuendo (v13.0.20 in my case), although for me it was at least not necessary to further mess around with midi clips after switching back to one distinctive channel.
I hope you’re having a good day and thanks again!
Hi and welcome to the forum,
Try with the latest Cubase/Nuendo 13.0.30, please.
Same thing happens there. Honestly I don’t understand this issue.