Ableton Forum

Yes, yes.. with all the gripes about this and that, i'd thought i'd post about this. It's not really a gripe, but more of a question of reasoning.

Why is it that Ableton doesn't allow vst's in rewire mode?

Simple question, but very complicated answer i'm sure. Personally, the only reason that i can see is a 'choice' on the part of the management. I'm saying this only because it doesn't seem to be a limitation of the rewire protocol, as Fl Studio has been able to implement this feature successfully. I'm wondering because i'm an avid protools user (no pun intended), and i'm dying for this feature (as i'm sure i'm not the only one.) It's been left out of the Live 6 feature list, so i can only assume that it's because that's how management wants it.

Personally, i think it's a mistake. That's my opinion, i know. But, i know that a million PT users would be crying out in enthusiasm to be able to use their favorite progs side by side, without having to be stuck in one without the other for any length of time. I think enabling this ability would sell your product even more, especially since there's not another product out there that can compare with your midi mapping capabilities alone.

So, again... can you enlighten us as to the reasoning behind this 'feature'?

*bump*


I can't believe no one else is interested in this... does anyone else have any input in this regard...

Dr. Henke does not know. He will figure out monday and tell you.

R.

Thank you my good man.. wonderful to hear some kind of official position on this subject. Cheers.

no rewire slave app can hold vst(i) s
go ask steinberg why.... ( is it steinberg? )
its a rewire limitation

ikke wrote:no rewire slave app can hold vst(i) s
go ask steinberg why.... ( is it steinberg? )
its a rewire limitation

according to Fruity Loops users, Fruity Loops can hold vst(i) while in rewire slave mode.

no rewire slave app can hold vst(i) s
go ask steinberg why.... ( is it steinberg? )
its a rewire limitation

Sorry but you're wrong... as i've already stated in this post, FL Studio has implemented this. It's not a limitation of the rewire protocol.

its propellerheads. so is it true that fruity loops can host vst plugs as a slave?
because its indeed a limitation from the rewire protocoll, but I can also imagine that there could be a conflict with two hosts trying to run vst plugs at the same time because of a limitation in the vst protocoll. so stinky are you shure fruity loops can do it?

so the others where faster then me
allright, so fruity loops found a way. so ableton could also do it, thats right....
cheers

stinky wrote:

FL Studio has implemented this. It's not a limitation of the rewire protocol.

yes, many are those who ponder this mystery.


.

So can Project 5 V2

Cheers
Jed

Of course i'm sure... go download the demo yourself... ask any Fl Studio user on this board, he'll tell you the same thing.

conflict with two hosts trying to run vst plugs at the same time

There's no conflict when you run the same vst plug in multiple hosts, i do it myself all the time...

because its indeed a limitation from the rewire protocoll

Please, show me the Propellerhead's documentation that states this clearly. Otherwise, it's just hearsay from companies not willing to implement this feature. It's not true, and until you prove it otherwise, my statement stands.

it IS a rewire limitation...
go pull yourself a Google and find out yourself

it IS a rewire limitation...
go pull yourself a Google and find out yourself

Sorry, i'm not going to waste my time. Saying it's a limitation sounds like you're just bellowing out the corporate diatribe from all the companies not willing to implement it to lock their users in.

I'm not going to waste my time searching for it, because unless it's directly stated by PROPELLERHEADS, then it's just bullshit garbage that companies are telling their support staff to fuck off users like you who are willing to eat that shit hook, line, and sinker.

If it's such a limitation, then why has it been implemented by Fl Studio and Cakewalk?

If you're so certain of this so called limitation, then you'll post a link directly from propellerheads stating exactly that!!

Hi folks,

before you start to scream... some few words on this issue:


1) The support of plug-ins so VST(i), AU,.. as ReWire slave is not! impossible and therefore not limited by the ReWire protocol.


2) But ... ReWire makes it harder from the development side. This is because the fact that the audio part of the plug-in has to run in the process of the ReWire host. Which again needs a lot of code to be written and (re)written.


3) The ability to support plug-ins in ReWire slave mode is one amongst many other feature wishes we have. So it does compete against all the others wishes we have too. And like usual doing one feature means to skip another.
It is a feature like many others which needs a certain effort to be implemented. But don't ask me how much as I only guess that it will need a lot of time.


4) It is theoretical possible that a certain plug-in does not work properly when several instances of this plug-in are running in several processes (or applications) at the same time. But this is not related to ReWire but the plug-in itself.


So mainly I recommend to vote for this feature in the wishlist forum (as other people already did).

Regards,
/Alex