Cubase: sending FX channels to groups?

Audio Plugin Hosts and other audio software applications discussion
RELATED
PRODUCTS

Post

SJ_Digriz wrote:Ok, read my post again. I fully understand that you can use the effect DEVICE outputs for this in the hardware world. This is NOT the channel output.
I actually don't exactly care how it is called.
See, in VST I could set up a group with an effect as an insert. This literally makes effect and group output the same.
The groups in VST worked just like any other channel (the only difference being that you could route whatever signal but the soundcard input into it).
You could just send something from a send into the very same group again.
The result (apart from latency, which we're not talking about yet)is 100% the same as in my last described hardware scenario (send > effect > stereo/2mono channel > send to FX unit again), thus creating a feedback loop.
My point is there are alternatives that aren't that difficult.
Well, as you allready said by yourself, there's no alternative once you only got a 2 I/O card.
And that's what things are not about either. Even if your card supports virtual channels, straight internal rerouting (without passing the converters again), it's not exactly the same because things wouldn't happen internally - which is what all us 100% native people want. So, for instance, a song utilizing the workaround you posted, wouldn't play back properly on a different machine.
Also, please explain the send thingy that I quoted. I actually respect your understanding of the apps Sascha. I want to make sure I know what it is you are referring to there.
If I understand correctly, you'd like to know about why I said the FX channels aren't exactly like what you may find on a hardware console.
They are, but they're simple returns (something you often find on hardware consoles, just a button or a reduced channel strip with stereo ins) that don't feature certain things, namely sends.

And that's the very reason you're using groups instead of FX channels (or racks, or whatever you may call them): To be able to setup sends to other FX devices.
A very common thing would be to setup a delay that way and send some portions of it to a reverb effect (in case you just insert it into the FX channel, the complete delayed signal would be effected by any reverb following).
And yes, this is VERY well possible with the current implementation of groups and FX racks.
It's just like it allways was, with the (highly welcomed) addition that FX channels per se are allready more flexible (nothing like the lame standard send FX rack in VST), so often you may not even need groups (because you can allready insert, say, an EQ into your reverb FX channel).
So, what I am doing is: use plain FX channels for more or less simple FX routings and groups in case I need something more sophisticated (such as sending portions of an effect to another one, as described above).

Phew - so, what am I complaining about?
Actually, I am not, at least not exactly. The ONLY thing being impossible with SX's recent implementation is that you can't create your own feedback loops (which was possible in VST).
I only used them once or twice, so I'm defenitely not missing much at all.
All I wanted to point out during these rather lengthy posts was, that a) it was possible in VST and b) it's possible more or less easily when using hardware consoles.
Personally, I wouldn't even complain if they never re-implemented it, since I really wouldn't use it much anyways (if at all), but parts of this thread were about the possibility (or lack thereof) to create your own feedbacks.

To Stefan: Well, from a mathematical point of view, you're somewhat correct, the feedbacks would most likely sound totally different in case you changed your buffersize, still, there's some interesting FX possible. Just run a signal through some overdrive, delay it, and feed things back into the same channel. Really weird, defenitely more dramatic than simply using the delays onboard feedback control.
In case you control the delay feedback (of the delay that is) via some controller, there's some great and nasty FX possible that you simply can't get from any other routing scheme.
I used to do such things a lot back when I had only cheap hardware but wanted some sound FX though.

As said before, these days it's of less importance to me. But it might make more sense for others though.

Hope this makes it clear.
Actually, I wasn't attacking the SX mixer (at least not for the routing portion of it), for me it's pretty much sufficient and rather easy to set up.
There are 3 kinds of people:
Those who can do maths and those who can't.

Post

Sascha Franck wrote: Phew - so, what am I complaining about?
Actually, I am not, at least not exactly. The ONLY thing being impossible with SX's recent implementation is that you can't create your own feedback loops (which was possible in VST).
I only used them once or twice, so I'm defenitely not missing much at all.
All I wanted to point out during these rather lengthy posts was, that a) it was possible in VST and b) it's possible more or less easily when using hardware consoles.
We are actually saying just about the same thing. The only thing that is missing to create a closed feedback loop is for a group send to list itself in the connections list, or at least upstream groups.

As you pointed out, the need to do this is just so minor that its not necessary to call out the deamons of wrath against it. If this post was on the Cubase boards asking about or suggesting the implementation that would be one thing. Coming here with all guns blazing ticks me off. It gives people the total wrong impression of routing in Cubase.

I just hate it when people go all app bashing over something that is not that important. And in this case has a fully functional implementation for anyone other than maybe a soundblaster user. Don't get me started on the unbelievably stupid bitch about being required to use group channels instead of FX channels.

I really feel that most of the other routing concerns will be addressed at some point in the life of the VST-3 implementation. I don't see them adding upstream routing though. It has been discussed to death in the vst dev group and it causes more problems than benefits by far. At least that has been the stance to this point.
If you have to ask, you can't afford the answer

Post

SX is a bugridden POS anyway... :hihi: :wink:

Post

flex42 wrote:SX is a bugridden POS anyway... :hihi: :wink:
hehee
If you have to ask, you can't afford the answer

Post

As you pointed out, the need to do this is just so minor that its not necessary to call out the deamons of wrath against it. If this post was on the Cubase boards asking about or suggesting the implementation that would be one thing. Coming here with all guns blazing ticks me off. It gives people the total wrong impression of routing in Cubase.

I just hate it when people go all app bashing over something that is not that important. And in this case has a fully functional implementation for anyone other than maybe a soundblaster user. Don't get me started on the unbelievably stupid bitch about being required to use group channels instead of FX channels.
OK, so maybe my explanations weren't plain enough. Now you see why I don't like the routing lack in SX?
I for one couldn't see what all your stuff about bussing was about - I'm talking analogue desks - As Sascha so eloquently explained, you don't need to dick around with bussing to feedback - you just use aux send on the return channel. Simple as that. But anyway, initially it was other things I was asking about.

And if we're going to talk about misinterpretation, then go back and reread my original post and several immediately afterwards - I wasn't actually bashing SX with all guns blazing - I've very easily stated that apart from this one glitch, I really got to quite like SX. You're the one who was getting all defensive about SX. I'm an SX user - I choose to use SX, so why get all territorial on me? I just asked if it was possible to reroute FX channels - so......as we all see, no it is not.

And it may be immaterial to you and many others. Personally I do alot of dubby trippy stuff with delays and all manner of routing and rerouting of FX...to me it can be very important. Yes, I know I have some workarounds, but as I repeated many times, that is not an elegant or simple way of doing what IS extremely simple to do on an analogue desk.

So can we put it to rest at last?
No, I cannot reroute FX channels. (FX channels - not group channels). Yes...you have some workarounds that work for you, but not ideal for me. And yes, I'm going to continue to use SX for the foreseeable future, as I happen to think it's a pretty powerful app.

You know...normally I wouldn't even waste energy on coming back again and again to a silly argument. Seems we both misunderstood where the other was coming from. We're both right and we're both wrong. Still doesn't alter the fact that SX doesn't do everything I would like it to...yes, hopefully that will be put right in future releases. And no, it's not enough to make me want to use another host.

Kind of makes me think I'll just carry on using my own workarounds to host problems - if such an innocent (and I didn't think it was an aggressive question to start with) topic causes some to go all out host war on me (and I'm even on the SX side!).
Posting any question on hosts is like religion and politics around here. :roll:

Post

alright, if I over-reacted I give too.
If you have to ask, you can't afford the answer

Post

Cool.

:love:

Post

maybe you guys were a little defensive, but nowhere near the levels of spit flying back and forth I've seen in other posts, and I for one appreciate the discussion, because I've learned a lot, and from both sides of this discussion... for example, when the reason for the need for feedback loops came in...

I completely understand how frustrating it is when a virtual world isn't working to full potential for a particular need,

but still, in threads like this, as soon as a physical mixer is compared to the cubase world, I feel like shouting praise due the virtual world, so that someone like me can have most of the functionality of a basically unlimited channel mixer desk that sounds damn good without needing 60,000 dollars to buy it and a room fifty feet wide to accomade it

and definitely props to you both for talking about this and working it out without resorting to cheap shots... I guess I'm just tired after a long and finallly terribly depressing election

Post

flex42 wrote:SX is a bugridden POS anyway... :hihi: :wink:
I hate to feed this fire, but... no it's not.

I just finished a 30+ audio track, and 9 VSTi' project, with a number of dynamic and timebased plugins. This was a major production, and Cubase SX2 didn't choke once. If it were so buggy, I wouldn't able to do this things I did in this session. All that lame Cubase bashing is pathetic. :P

EDIT: spelling :oops:
Last edited by ahja on Fri Nov 05, 2004 2:23 am, edited 1 time in total.

Post

yeah, lamers !

:D

Post

hi everyone

if've been following this thread and agree with SJ_Digriz that there are limitations which we might have to live with until VST3 and his workaround suggestions. one question still puzzles me a bit.


I have a drumset routed to a drums group, with some gated reverb on snare and toms, as well as ambience on the whole drumset. I create two fx tracks, one for rev, one for ambience. I would like to route the fx back to the drums group, so if i decrease the group volume, the fx volume decreases as well.

I don't assume that sx works like a vca console where that would be taken care of. :?:


is my only possibility to create group tracks w/ the fx as inserts and route them (forward) to the drums group? has the following disadvantages:
  • adding a third fx would mess up grouping (or not allow routing), this has been mentioned many times in this thread

    i can't have all my fx return channels together. instead i would have to put them in front of the group they are routed to
question might be little stupid, but this is one fact which bothers me on a daily basis

cheers,
instyle

Post

why not have two groups?
pre-fx and post-fx?

Post

why not have two groups?
pre-fx and post-fx?
sorry, didn't get this one. :shock: where do you route the different channels? you need a group for each fx in this case, as i mentioned in my previous post.
those groups would take an fx as an insert and the groups itself go into the drums group.

what would you route to pre-fx and post-fx groups?

Post

instyle wrote:
why not have two groups?
pre-fx and post-fx?
sorry, didn't get this one. :shock: where do you route the different channels? you need a group for each fx in this case, as i mentioned in my previous post.
those groups would take an fx as an insert and the groups itself go into the drums group.

what would you route to pre-fx and post-fx groups?
Drums to pre-fx
pre-fx to post-fx
fx to post-fx

Should be doable, no?
Actually I don't see the problem at all, as long as you're not trying to route to a lower group number you're ok, right?

So if you have:
group 1, drum group
group 2, drum fx 1
group 3, drum fx 2
group 4, drum fx 3
group 5, drums with fx

should that not work?

Post

instyle wrote:I have a drumset routed to a drums group, with some gated reverb on snare and toms, as well as ambience on the whole drumset. I create two fx tracks, one for rev, one for ambience. I would like to route the fx back to the drums group, so if i decrease the group volume, the fx volume decreases as well.
Why not set your sends to pre-fader?

Forever,




Kim.

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”