As for the native support, I hope so too, but Steinberg donât seem to care about UX, like, AT ALL.
All they need to do is to hire a few young (25-40) programmers and designers who know the value of time in the modern world and have experience with modern ultra fast user interfaces.
They just donât care.
I guess, itâs time for a next-gen open-source DAW, created with the help of LLMs. This is probably the last decade for Steinberg, unless they really fix everything quickly.
Regarding Steinberg, nah⌠donât think so I guess I was not able to make sense of your script then⌠now I see. But looks like I just found an even better option: at least in C15⌠Granted, you still have to first slice the section you want to compress/expand⌠but at least you can do so from within the Key Editor⌠Hurray
Steinberg doesnât need AI to fix Cubase. The only thing AI would accomplish is to remove jobs like itâs been doing for years.
This only takes one thing, which is common sense. For a DAW that is legendary for its MIDI editing capabilities, it drops the ball when it comes to a very simple function like scaling groups of notes in time. To me itâs impossible to understand how this is still not implemented in Cubase 15.
Recently I bought Studio Pro One 7 as a backup DAW because I owned an old version so to me it was only $115. And even that DAW, which is mostly considered great for audio but not so much for MIDI, has a great implementation of scaling for selected notes. It surprised me that it has several MIDI-oriented features that go beyond Cubase Proâs. Of course I find it hard to switch because I spent 3 years learning Cubase Pro, and itâs hard learning how to do all the things I take for granted in another DAW, and some are not available.
But how is it that this basic feature is still a discussion in late 2025? I mean, the workaround I mentioned when I created this thread years ago was just that, a workaround. Itâs not a great way to achieve note scaling, itâs not that precise and takes several steps. It may work fine for people who create small regions or parts, events, whatever you call them, in each track, and they want to scale just that. But I donât work that way, I like the whole track to be just one region when it comes to MIDI parts. Itâs easier and faster that way.
You are right but it is inevitable to some extent. I personally donât believe that LLM will ever take any jobs except some junior positions, but the newer sort of technology might.
You just can not stop it in any way. Even if we ban all big tech companies from doing this, there are already local opensource models.
LLMs write more than 50% of my code now. And I know it is true for most programmers. We just can not afford to not use it.
What I mean is that in the next 10-15 years we will see a dramatic increase in actual high quality open-source alternatives to established commercial software. Like Blender-level, but made in a fraction of the time by small teams or even solo individuals.
If Steinberg (Adobe, Autodesk and the rest) canât keep up, bad for them. Their programmers most likely will find jobs elsewhere, but the software will be free.
The worst of it can be stopped when lawmakers have the will to do so and stop bowing down to corporations and start working on behalf of people. If there are laws that say that no AI can ever replace a job, and it can only be used by people as a help like a complex math problem, or research or anything else, but not replace any employee, or a position that would require a human employee, then we might be saved.
The Terminator future is fiction, but the AI takeover is real. It wonât end with the machines killing humans, the world will end when most people donât have jobs anymore because AIs and robots with AI brains end up doing everything, and as usual, only the richest people benefit from it.
Was just âdabblingâ with some MIDI stuff this morning, curious after watching a friend at work in his studio yesterday, inside StudioOne. He was selecting or rubber-banding several notes (events) together and simultaneously stretching/compressing them (changing length/start position) by just click-dragging on one of them, left/right. Job done.
As described in this whole thread, I found that a similar elegant, simple, quick, friction-free workflow is still lacking at C15.0.30
Did a quick search, but couldnât find an actual âFeature Requestâ thread for it though⌠Is there one.?
I think the mere presence and availability of the Stretch Mode in the Key Editorâs toolbox might be a reason why people donât actively make a feature request about this. Maybe some consider it a missing feature that is halfway there? I donât really know, just saying.
Personally, I have a use for this feature and would certainly use it.
I guess I was not able to make sense of your script then⌠now I see. But looks like I just found an even better option: at least in C15⌠Granted, you still have to first slice the section you want to compress/expand⌠but at least you can do so from within the Key Editor⌠Hurray 
