Julibee wrote:Bavanity, that's a great tutorial for like a NY Compression sort of drum tracking. I will use that at some point. Good find. Thank you. Maybe I should clarify a little. This video is chaining multiple tracks together and processing them as such. What I want to do is chain out a single track into multiple fx... Meaning... I'll have one main Vox track, that I want to fx the single track in different ways*. I was able to do this in Reason, simply by creating a parallel in the mixer and adding fx/pans directly in the mixer. I know I can do this in any DAW, but I'm not sure how. Do I follow the same processes as outlined in this video? Because it seems to me that he is working with multiple tracks. I think QVProd's idea sounds like a different animal, and I THINK that's what I want. Yes? Auxiliary tracks... That may be the term I was looking for. *Originally, I'd achieve the same thing by duplicating tracks and having a million tracks to deal with. I loved when we got the functionality to more easily split the sends without physically having to duplicate tracks. Bear in mind that a single chorus of mine might have four or five backing tracks-- each with a parallel... Or two. That adds up pretty quickly.
You could always try the rewire tip I suggested and do your parallel stuff in reason, and then output them to separate rewire outputs, then apply delay compensated AU or logic plugs on them - just another idea.
Another way is to simply create a duplicate of that vox track and minus 6d db on each one to match the original volume then treat it as a parallel track. There is no difference to reason there.. if you have a cloned track and put effects on one, that's a parallel effect and what reason is doing, albeit in reason you can do it for busses, etc.
So you are saying you want something paralleled and putting different effects on each one, and maybe even more than one parallel channel, right? The same duplication principle applies, just do as many as you need.
Then they can all have different output destinations if you so choose, and those can then have any output destination and so on and so on. You can create infinitely complex chains, save the chains as a logic "channel strip setting" for recall any time in any project, and the beauty is it's all delay compensated in the case you are using effects with latency.
otherwise the solution QV gave is also correct. I just find it a bit confusing to do it that way cause i traditionally use sends in any daw for just one purpose.. reverb or delay. But that's just me! hehe.
I'd rather create duplicates and just name them parallel # whatever.
same principle applies in reason with parallels, you need to lower the DB in most cases to get a normal volume output.. the only difference IMO is that in reason it's done at the mixer where as in logic you would need to make sure the data actually playing back on both tracks is in the same spot. But the duplicate function ensures this. You will need to copy and paste if you change data on the main track later on. No big deal.
And it's not a solution for busses, if you want to create a parallel of a bus in Reason.
Don't forget the wet/dry suggestion also, because with one of these sub hosts you can create any sort of FX chains you like and control the amount of the effect for ANY type of effect. Of course this means the effects feed into eachother, so in your case it's obviously not suitable all the time.
As with any DAW, there are multiple ways to do anything, but NOTHING has one button parallels like Reason, and that's just the way it is, so everything is a "workaround".
You just need to find the method that suits you and you feels comfortable with in Logic, and go with it. Or perhaps depending on the project, a combination of methods!
Would you like me to create a basic audio track and 2 parallel copies of it for example, using QV's method, and send you the project? And also the other method i spoke of with duplication?
per instance!
Share and download patches!
Join ReasonTalk on Slack!