Funny to see that each and every one among us hasn’t the same concerns/expectations : actually, I share none of the @arkdzo ones. FWIW, here are mine, letting ‘bugs’ and misbehaving features aside :
My essential FR concerns the UI in the arrange page : allow us to use two distinct settings for horizontal and vertical grid lines colors.
16 Quick Control slots (been waiting for them since the beginning, which is quite a while…)
MIDI Remote Control : NRPN INC/DEC messages recognition, as defined in the MIDI 1.0 standard specs, using the graphical assistant : the Remote Control, beside having an overcomplicated layout, is still unable to manage them without scripting.
Result : I’m still using the Generic Remote definitions.
A presets management overhaul (the disappearing displayed preset from one session to another - see, in example, the Input Transformer window).
A more consistent keystroke management (especially the Tab one) in several dialog windows.
The preservation of the VST 2.4 compatibility as it is now (since Cubase 12, I’m living with the fear of its end - a clarification from the Steinberg team about it would help).
That sounds interesting. I’m picturing something like Bitwig’s modular grid environment? Where you’d have the track as part of the arrangement view but then double-clicking it would enter open a new window that is the grid environment where you can build modular connections and patches?
IMO the biggest thing missing in Cubase is some way to create and split audio chains for parallel processing. The current workflow with sends is extremely clunky.
Effective copy protection, a much higher price point to pay for 24/4 support and a really active officially hourly policed paid user forum.
That is really what’s missing
Oh dear they won’t like that!!!
Pretty much yeah. I do like how the current modulator options are embedded, but I come from the rack environment of Reason where complex webs of connections are trackable with cables, the visual feedback makes it simpler to keep tabs on signal flow. Sure, I get that Cubase is primarily a composers DAW, with excellent midi and audio options, but it’d be wonderful if the mad sound scientists had a nice little corner of the playground.
As a composer myself with a love for modular/eurorack synths & guitar pedals and patching crazy effect chains – I’m here for it! I have a lot of hardware synths too so having a modular-style grid environment with midi functionality could open up a lot of exploration in the studio. Love the idea!
It was the lack of modulation options that kept me as an elements user since 2019, I would often boot up Cubase when I just wanted to write a simple song with few bells and whistles. But after the modulators came along I knew it was time to go all in, I’ve spent the past few months playing with all the Cubase stock effects, the modulators have really reincarnated them. With a mod environment (and automation clips) I seriously doubt I’d use anything else.
Always a pleasure to meet a fellow chain enthusiast
Well some are no longer living and didn’t pass on the code. Also, there are VST2 gems that have no equivalent today. However I totally understand finally forcing everything to VST3.
I’m confident there will be developers who will release “wrappers” for VST2 to VST3.
I just want stability and no more bizarre CPU spiking behavior even when Cubase is left idling. This doesn’t happen with either Ableton or Bitwig on my system, but working in Cubase has become a nightmare because of it.
I really would like this release delayed indefinitely in favor of reaching a much higher quality bar and “always shippable” main repo. There is no way a program this riddled with bugs should be released publicly. “Delusions of adequacy” comes to mind.
FYI, there are peoples that still use VST 2.4 stuff : I’m one of them and certainly not only. Why so ? Simply because there is no satisfying replacement for it in a VST 3 format.
I would suggest you to widen your gaze. I assure you : you are not alone on this little planet…
Indeed. That’s not to say people still don’t have options, they just won’t be natively “supported” going forward. I’ll continue to use my Iris2 example, as it’s out of production - reportedly, there will be no further production on it, so there will be no VST3. For me, since I use MacOS in Native Apple Silicon mode, this makes things even more complex because I can’t (won’t) load VST2 anyway without Rosetta. However, as @Greg_Purkey mentioned, Blue Cat Patchwork, MetaPlugin, etc allow you to host VST2s inside Cubase. This still doesn’t help me, but Iris2 has an AU, which DOES work. So I can just load Iris2.au inside Blue Cat (even as an effect) and it works perfectly.
If I absolutely required a VST2 x86, then I could do the same in Rosetta. Or just run it in Live and use my virtual audio channels into Nuendo as I already do (or even make an external instrument to Live if it is an effect).
So we have options, even if inconvenient. But from a supported architecture perspective for SB, we should consider VST2 EOL.
Man Iris was awesome. I should’ve known when they were giving it away at Plugin Boutique its days were numbered but it was a really cool way of working with samples.
I still have the archives here taking up space but haven’t used in ages it seems like. Sadly quite a bunch of my iZotope stuff went that direction, I still miss iDrum even.
I THINK Plugin Buddy might be able to host VST2/AU in a VST3 app? I only use it for sound design sessions or testing out stuff without having to open the DAW up so I’ve never used its plugin version, but I think it can do it as well.
