I got used to the new GUI after the last update and using it almost constantly. It's much better to me now, and I don't like going back to 12. Funny how that works! It still needs some important updates/adjustments like the tiny font sizes in some areas like the inspector, and increasing visibility/legibility in the mix console in some ways.
Cubase 13 released! Now available for purchase
- Thread starter mducharme
- Start date
Yeah and I keep looking for an update but seems like slow moving on that front. And it looks a lot of people are experiencing problems. : / It's eating into my 60 day trial too which stinks. I really am intrigued by the easy midi mapping for devices....but it won't stay running long enough for me to do anything.
Man that must feel frustrating. It's gotta be something like a plugin or other software that's interfering in some way that C13 for some reason can't handle but C12 can. I say that because I'm running gigantic scoring sessions with VE Pro both on the same Mac Studio M2 Ultra running Ventura, and C13 is almost as stable as C12 was. Usually I can run a huge scoring almost all day without a crash, though it does crash a bit more than C12 did overall.
It’s incredibly frustrating because everything else on my system runs great! Logic. Bitwig, Ableton, Studio One. Alllll fine. : /
And extra frustrating because I truly wanna explore it.
But honestly, in the grand scheme of things, not that big of a deal.
I’ll keep looking for updates and maybe something will fix it. Glad it’s working so well for you! Have fun!
Is it possible to edit simultaneously CC of multiple MIDI events in Cubase?
e.g. I have bunch of midi events, which have certain and unique CC curves.
And I want to increase/decrease them a bit, evenly and relatively. Like I do it within one event.
Can I do that without editing each event separately?
e.g. I have bunch of midi events, which have certain and unique CC curves.
And I want to increase/decrease them a bit, evenly and relatively. Like I do it within one event.
Can I do that without editing each event separately?
ALittleNightMusic
Professional Amateur
Maybe via the PLE, but not within the piano roll that I know of.
Nope. This has been requested for years. Cubase has many longstanding little issues like that which get in the way of fast workflow, and this is one of the big ones IMO.
Last edited:
I'm starting to feel that one of the biggest problems that might be happening with Cubase is that the code is so old, and so many of numerous workflow issues are baked into this old code and might not be changeable/fixable.
I could be wrong -- please tell me if I am (but I need facts about this regarding Cubase, not just assumptions/opinions).
If I'm right I hope Steinberg has been working on a complete rewrite from the ground up, otherwise we'll be stuck in this old code for a lot longer and not get some of the features that have been asked for many, many years. I look at an app like Reaper, which is as deep as it gets yet is so incredibly fast and efficient with how it works. That might be old code at this point, too, but it seems to be programmed much more smartly in order to be so fast and efficient yet be so deep.
I could be wrong -- please tell me if I am (but I need facts about this regarding Cubase, not just assumptions/opinions).
If I'm right I hope Steinberg has been working on a complete rewrite from the ground up, otherwise we'll be stuck in this old code for a lot longer and not get some of the features that have been asked for many, many years. I look at an app like Reaper, which is as deep as it gets yet is so incredibly fast and efficient with how it works. That might be old code at this point, too, but it seems to be programmed much more smartly in order to be so fast and efficient yet be so deep.
Pablocrespo
Senior Member
You can do that with the logical editor, I have cc1, cc11, increase, decrease, increase and decrease by 10%, etc mapped to touchscreen buttons so I can change the values without entering the key editor
Obi-Wan Spaghetti
Senior Member
Yea you pretty much have to go back in time for this one. hehe!
Totally forgot about the list editor.
Yes, I'd guess that a third party plugin might be causing your stability issues. Try disabling all third party plugins. Cubase Pro 13 is running perfectly fine here too. Just as stable as 12 was. I've been using Cubase since the first PC version in the early 90s. Early on it was the OS that dictated how stable Cubase was. Especially when USB was introduced.
Thanks guys! I did uninstall and reinstall it last night. I proceeded to spend about an hour without any crashes. That's progress! : )Yes, I'd guess that a third party plugin might be causing your stability issues. Try disabling all third party plugins. Cubase Pro 13 is running perfectly fine here too. Just as stable as 12 was. I've been using Cubase since the first PC version in the early 90s. Early on it was the OS that dictated how stable Cubase was. Especially when USB was introduced.
jonathanwright
Senior Member
Further to @Pablocrespo 's tip about using the logical editor, you can also set it to affect all MIDI CC values at the same time, if you like.
So by using your custom key command, you can adjust all values, like CC11 and CC1 at once. (Add filters to the LE preset to ignore CCs you wouldn't want to change, like vibrato and sustain).
Another advantage of this approach is that you can adjust the CC values of multiple MIDI parts at the same time, without opening them in the editor. Just select all the parts you want to adjust, and use your key commands.
Pietro
Senior Member
I can make your perfectly fine Cubase 13 freeze, hang, crash or run abnormal in 10s :D. Easiest thing to try is to abort Bounce Selection or to use presets in Offline Processing window. First one will hang Cubase forever and the other one will make all presets default to some weird values.
Use octave pitch shifting on audio much? Well, don't try it with presets. Cause presets don't work at all.
Many times applying offline processing will also result in Cubase crashing.
Not to mention occassional unmatching waveforms, which has been around for years. And I use a lot of sounddesign-ish audio processing in some of my work, so these things bother me all day.
After using 13 for over 2 months, it's not the best release. But I'm sure most of it is getting fixed. Anyway, I've gone from the "Cubase is running perfectly fine" team to noticing and reporting all the little things, though. Makes you see many more issues on the way, but hopefully spending 5 minutes on a report will help improve it.
- Piotr
Thanks guys for the help, logical editor did the thing.
But its still would be awesome to do that within pianoroll via curves manipulating.
