I don’t think Cubase needs clips Ableton style grid, I don’t know how much it is used in Logic or Studio One instead of Ableton.
3 Likes
Something as simple as auto-filter could spur a hit track.
Certainly, plenty of hit tracks have been made with clip-launchers in Ableton, which is why you should go make one in Ableton, and then edit and mix it in Cubase…
And then, if Steinberg improves what already exists - you’ll be able to edit and mix faster in Cubase, giving you a quicker turn around time to start more hit clip-launch created tracks in Ableton/Bitwig.
1 Like
Ok, no more thinking about Reason or ReWire for me. Reason was bought by LANDR.
R.I.P. Reason. The AI bros will f"*** you hard.
3 Likes
Bad news travels fast.
It already has. It’s called Ableton Link.
I was under the impression too that Link was somewhat of a successor to ReWire, but after a bit of research, it seems the concept is quite different.
While ReWire worked as transmitter/receiver with song position sync and audio return channels, Link is more of a peer-to-peer clock sync protocol. Link seems geared towards synchronizing multiple devices/performers across platforms. ReWire was more about connecting multiple applications on a single platform.
I don’t have any personal experience with Ableton Link so the above is based on what I found and read online. Please correct me if I’m wrong.
Is Link/ReWire needed today?
Wouldn’t VST3 be more than capable of the VST plugin just being the cliplauncher “DAW” itself.
If there is such demand on this, why has no developer out there created the Ableton/Bitwig in a plugin?
VST can input and output multiple audio streams
VST can input and output full MIDI
VST can drag and drop audio files
VST syncs to DAW
Really this is what Steinberg should do. They’ve already toyed with it - Loopmash for example.
My guess is, if Steinberg does do/is doing this - it will be incorporated into the new pattern track instead of Clip Launcher built into the DAW foundation.
Link is, but like all things, it depends on who you ask. 
Because you don’t need that if you just implement Link instead. Why try and wrap a DAW when you already have the other DAW in operation? Today, we can already transport sync in Cubase via virtual midi, etc. And that “works.” But Link expands that use case out to all Link enabled devices in your studio, even other systems.
Sure, and Blue Cat connector already does this, if you want to pipe audio / midi over a network (or local IP loopback) and accommodate additional latency/dropouts. Nor is it necessary for MADI/Dante/ADAT routing already in place. Bitwig supports Ableton Link, and I would content that they are rivals. So I wouldn’t using Blue Cat or “VST midi I/O” to pipe midi between DAWs when I can just sync tempo/phase directly to the other DAW and let it handle it’s own instruments. Sure, you can pipe MIDI around when necessary, which I do between workstations when needed via my mioXLs, and there’s definitely use case for that. But the multiple device tempo following, syncing, and transport features all built into Link are already there.
Clip launcher or not, Link support should be built in just like it already is in Cubasis (though I’ve never used that). And if you have that, then there’s no reason at all to even try clip launching in Cubase. I mean, to your point, people buy TONS of VSTs and have them loaded all over the place. Why not just buy another DAW that does what you want better and link them all together?
So, “yes,” in my opinion, it’s needed. I don’t think the VST-based media/data routing between DAWs in that necessary. If it is, we can already do that today.
What are the current clip launching vst´s around? I mean something similar to this ableton workflow. I know MPC has it now, but there´s no vst around anymore
Presonus Studio One Pro has now become Fender Studio Pro 
I made a thread here: Presonus Studio One, is now Fender Studio Pro - Steinberg Lounge - Steinberg Forums
Seeing a lot of “switching to Cubase”