Cubase 4.5.2 (OSX) and TIOS3 "Sidechaining" the Input WORKS!

[cYrus]

Originally Posted by marc

we would be done with a VST3 version but unfortunately steinberg broke things we need so we all have to wait.

m

that's great i guess you had the VST 3.0.2 SDK preliminary which was released yesterday. or is it a bug in the cubase host implementation?

[h4nc0]

Originally Posted by marc

we would be done with a VST3 version but unfortunately steinberg broke things we need so we all have to wait.

m

Is it broken in Cubase 5, assuming you have access to the beta version?

[isaac anthony]

holy FAIL!!!

Dear Isaac,
I simply can't answer this. Sorry.

Best wishes,
Joerg Huettner


--- Original Message ---

hello Joerg
Thanks, but... What about cubase 5 ? Do you know if it works in
cubase 5 for windows? And is this something that Steinberg needs to
fix, or Access needs to fix?
thanks!
isaac
On Mon, Feb 16, 2009 at 2:12 PM, Access Music Customer Support

[Cantankerous]

Originally Posted by marc

in a way you're right. but since not everybody will use side chaining i think it would be questionable to declare cubase 4 to be incompatible. here's a list of host based limitations we found in regards of side chaining:

- cubase 4 doesn't support it for instruments (not a part of VST2.4)
- cubase 4.5 / 5 does support it but the VST3 implementation is buggy and other aspects of VC stop working unless steinberg fixes somethings (which they hopefully will)
- logic works but the input is not delay compensated

on the other hand:

- live seems totally fine, even with VST 2.4

best, marc

Hi Marc,

have you guys at Access let Steinberg know of the issue that needs to be fixed, and have requested that a fix indeed be implemented? I am not calling you guys stupid, but I wouldn't hand it to Steinberg to just fix things on their own. They are not the most flexible company when it comes to implementing fixes and listening to user requests. I hope something will come of this for us Cubase 4 users. I would be extremely disappointed if they fixed whatever was need only in Cubase 5 as it is their newest product, leaving us 4 users in the dust.

[Cantankerous]

just a quick bump to see if anyone has gotten this to work Via Cubase on PC?

[isaac anthony]

hey guys

I've got the same problem.

I'm hoping cubase 5 will fix our problems, cuz I'm gonna bet there will never be another v.4 update.

I don't know why I don't switch to ableton.

[digitalgeist]

Originally Posted by isaac anthony

I don't know why I don't switch to ableton.

I just switched to Ableton Live a week ago, despite figuring out how to do this in Cubase it's an absurd workaround, and Steinberg's usual response is "well, sorry it doesn't work but we have a new version out for $299!" I'll keep Cubase 4.5.2 and use it for final touches, but I think I'm done with Steinberg. Between the problems with this and other instruments, lack of really helpful support and being told to pay up every 2 years...

/offtopic rant

[marc]

Originally Posted by Cantankerous

Hi Marc,

have you guys at Access let Steinberg know of the issue that needs to be fixed, and have requested that a fix indeed be implemented? I am not calling you guys stupid, but I wouldn't hand it to Steinberg to just fix things on their own. They are not the most flexible company when it comes to implementing fixes and listening to user requests. I hope something will come of this for us Cubase 4 users. I would be extremely disappointed if they fixed whatever was need only in Cubase 5 as it is their newest product, leaving us 4 users in the dust.

yes, we are in touch with steinberg. they need to fix those issues on their own, there is nothing we can do about it. there are things which we have reported more than 2 years ago and they only got fixed in cubase 5. i simply don't know if those bug fixes will make it into cubase 4 generation products and i also don't know how long it will take them to repair what got broken in cubase 5.

marc

[Cantankerous]

Originally Posted by marc

yes, we are in touch with steinberg. they need to fix those issues on their own, there is nothing we can do about it. there are things which we have reported more than 2 years ago and they only got fixed in cubase 5. i simply don't know if those bug fixes will make it into cubase 4 generation products and i also don't know how long it will take them to repair what got broken in cubase 5.

marc

Thank you kindly for the reply. What you state about Steinberg is not at all surprising. They are so thick headed sometimes when it comes to admitting to faults and bending, even just a little bit towards customer requests. They are instead so rooted in only showing off what new stuff 'they personally' thought of and don't want to see beyond anything else.

I am glad you are at least in touch with them, hopefully things will get sorted soon. Processing external audio through the Virus is pointless as it is no longer delay compensated once it leaves my system into the Virus and back via S/PDIF OR ANALOG. I need the sidechaining to work to FINALLY be able to do what I thought I was able to do when I first bought the unit. Let us hope for the best.

A little miffed that my perfectly working Cubase 4 will probably have to be upgraded just to get what I need working.

BTW, if at all possible, can you state what was finally fixed in Cubase 5 that wasn't previously? You mentioned this in your post commented above. Thanks.

[marc]

Originally Posted by Cantankerous

BTW, if at all possible, can you state what was finally fixed in Cubase 5 that wasn't previously? You mentioned this in your post commented above. Thanks.

hi,

it's pretty simple. some of the functionality we need to make sidechain work doesn't exist in cubase 4. it has a lot to do with VST3 support. we intended to have a Virus Control for VST3 by now but when completing the initial implementation, we found that core aspects of MIDI communication were either not implemented or simply broke (poly pressure, for instance). VST3 support, at least indirectly, also holds us back from having a 64 bit version. i don't want to say that i cannot be done with VST2.4 but there is reasons, beyond what needs to be shared here, why it holds us back.

it is not unusual at all in development that once you try to put together the pieces you run into unexpected issues. the problem here is that we need others to fix things which of course makes it difficult to define timeframes. and since every company runs through it's own development cycles and deadlines sometimes those unexpected things have to wait. it certainly wasn't in steinberg's intention to create this situation.

best, marc