TBH, I’ve just watched Dom’s intro to Cubase 15 and there’s really nothing there that applies to my very simple workflow. But if I can scale up several of my VSTs that would make me happy. It’s probably about time I leave Version 12 and get with the program.
Yeah, nothing in the upgrade makes me jump at it. I am a professonal of over 30 years with quite a complex workflow, 14 was so on point in terms of features, I’m not sure how they can make a massive step up.
resizing is always welcome so that might get me to upgrade after all the kinks have been worked out in 15.1 or 15.2
I’ve been using Version 12 for what seems like forever. I also realize there is value in keeping one’s software current and up to date. For that reason and that reason only I’ll probably be updating to version 15 (currently ver 12).
I don’t need a new pattern sequencer. I don’t need new electronic drum kits. I don’t create “beats”. Anything with the nouns “dub”, “house”, “trance” etc is wasted on me.
About all I’ve seen that is relevant to me is the plugin scaling and improved expression maps.
Thing is, they have to make money so they have to make new versions and have to add new stuff.
I’m 61, retired due to health, have Pro 14, Absolute, Dorico. NI 14 collectors, Arturias V collection etc etc etc.
I could stay with what I have and be perfectly happy until the day I die, Compared to what was available when I was 20, I’m in a dream land, could want for nothing more.
I still upgraded Omnisphere 2 to 3 last week and I’m still about to upgrade to Cubase 15 Pro.
I don’t need it as such. I will probably play with the new features, whether they will ever get touched after a few weeks, who knows. I’m sure I’ll find things I like.
But, I first heard of Steinberg when a friend bought around a copy of Pro 12 for my Atari ST, I then purchased Pro 24 and the rest is history. I want the likes of Steinberg to still be around in 20 years time, to me, spending £83 on a new version, well I’m happy to do so to help keep them funded and appreciate the work they put in.
Wife and I had a coffee and a toasted cheese sandwich each a few days ago. That was nearly £20 and lasted minutes.
How exactly can I rescale my plugins in C15?
I can’t seem to find the option anywhere.
Right Click in the plugin window.
And I agree with OP. That was the reason I didn’t use Frequency as much as I should have.
Ah, instruments aren’t “plugins”, they refer to insert effects. Didn’t even think of that, but now I’m a little disappointed, too
Padshop desperately needs scaling.
I don’t even use Groove Agent or any of the other junk. Although Halion 7 is convenient for some drum mappings I have. I would be happy if it had all the features of Cubase 5, but with better GUI.
I’m an audio-purist, and play guitar and bass. Steinberg should understand their core-market is audio recording, and stop pandering to the ‘preset’, ‘one click’ world - who’s ‘music’ often resembles a blind man with a chainsaw in a ball bearing factory, with a robot voice tacked on for good measure.
I will have a look at Cubase 15 in August 2026, when I next update my Mac OS.
Ah, now it makes sense. Yes, now it works with insert plugins, like Reverb, etc.
Yes, Padshop has tiny GUI - I have scaled everything up to 150% DPI on my Win10 - seems to work fine, so far.
Dang! I thought it was going to help me increase the size of some VSTs. Seeing that it’s only plugins has me rethinking my upgrade path.
The stock effects can be resized but two stock instruments, Pad Shop and Retrologue can’t. As for 3rd party instruments they can be resized if they support it themselves. Which most do now.
Looks like only Groove Agent SE is scalable (which I am most excited about), Halion and Halion Sonic don’t seem to be scalable either (unless I’m doing something wrong!).
I didn’t check sonic as I have 7 and you can drag that out to change the size.
For sure, but dragging Halion out doesn’t make the text etc actually any bigger, so fully scalable Halion would be very welcome!
Good job you’re not head of their development team.
Ah this is true. Fair point mister ![]()
The release notes list the limitations on scaling in the Known Issues section:
It works only with stock plugins!
