Cubase 15.0.20 Maintenance Update Available

So for me the update did not work properly. Everytime when i want to import a file from the import menu or media bay it crashes instantly.That never happend with any other version of cubase. So the dump file says something like access memory violation. Cubase cannot acces the RAM. So i had to go back to version 15.0.10

Oh Man! This was the solution! Appreciate the help for all of you guys! The little curved ā€œresetā€ arrow restored the ā€œdouble-key-comboā€. You’re lifesaver thank you!
SOLUTION to fix, if anyone:

BTW, beside of this, I love this update 15020 and can’t say how happy am I with the new folder-track

You’re welcome!! I’m glad you’re back in business!!:slightly_smiling_face:

Hmm, is there usually a 50% summer discount? I feel like the current 30% deal is usually as good as it gets. But maybe I don’t remember it right.

Loving this new update, my sessions are now a bit smaller and a lot more organized, thanks a lot.

Thank you. Could you please fix the bug in the Mixer Sends? When trying to adjust send levels across multiple selected channels, the change does not apply to all of them as expected.

This issue was introduced in an update of Cubase 14. I recently upgraded to Cubase 15 Pro hoping it would be resolved, but unfortunately the problem is still present.

I cannot reproduce this with a quick test. Is there a topic in the forum about this already? Can you provide the link? Or can you please create the topic?

I have it too. I think that it was fixed in 15.0.10, but I may be mistaken, and it came back in 15.0.20

Hi! Mathias … I’m sharing a link to a suggested improvement for the Drum Machine Pattern Editor display. I can’t post the link here, so I’ll just give you the title of the thread I started. Congratulations on the new 15.0.20 update!

The post title is in case you’d like to take a look. Drum Machine ā€œImprovement suggestion: Visual MIDI Input Indicator in the Drum Editorā€

Thanks so much! :wink:

thanks a mill for implementing the horizontal inverted scrolling -option!! Godsent

Utterly broken thanks to midi logical editor setting values to 0 :melting_face: hotfix would be greatly appreciated.

To reproduce this bug:
Enable Q-Link in the Mixer window, select multiple channels, create a send to any FX, and double-click the value to enable write mode. Enter any value and press Enter.

The value should be applied to all selected tracks, but it only remains on the track that was double-clicked, even though they are all still selected

Aha, the text entry issue with Q-Link. Yes, I know this one. Thanks.

The Release Notes say that you get ā€œWaveLab Goā€ as an ARA audio extension, but it installed a standalone WL Go application, as well.

I already have WL Elements 12, so I bought the upgrade from 12 to 13, and the WL 13 app installed by Cubase now opens as Elements. So, presumably, there’s just one app and the licence type defines the feature set, as with Dorico and other apps.

Yes, a bit maddening… the other parameter values like faders, cue sends, the strip FX modules, all behave as expected regarding manual entry via Q-Link on selected channels. It’s just the Sends that don’t…

As you mention in your earlier post, this was the case in C14 too.

Deserves it’s own thread if there isn’t one already.

PS:- wonder if this is also seen in Nuendo.?

It behaves the same in Nuendo… for all values entered by keyboard aside from the volume values in the mixer and not only for sends.
And yes, this behavior is not new in version 15.

Interesting. so it’s a more ā€˜widespread’ issue there… Definitely needs reporting/bringing to their attention here (if confirmed)…

Nuendo 15 - official bug/issue collection thread - Nuendo - Steinberg Forums

Cubase Pro 15.0.20 Issue (Windows Pro 10) Mediabay previewer selection range: Cannot insert selection range into the project anymore. It inserts the whole file length.

Hey,

unfortunately it was the oposit for me. On 15.0.10 a heavy project was still running stable enough and with the new version Cubase would always freeze completely after a minute or so. Tried rebooting, deactivating WiFi and so on - no luck. Had to go back to the previous version where that same project runs fine :frowning: