Slaving... a DAW
- Thread starter LLL
- Start date
GoldenVulture
Braindeadologist
Re: Slaving... a DAW
Because you can... like you can sync multiple computers and run multiple daws together.:friday:
Because you can... like you can sync multiple computers and run multiple daws together.:friday:
LLL
New member
Re: Slaving... a DAW
One example use: Pro Tools.
Say you've got some tasty VSTs that you just gotta have in your project.
Pro Tools doesn't (and never did) allow VSTs (AAX only since versions 11,12; RTAS before that).
But you can use for example Reaper ReWire on a track in Pro Tools to pull it in; Reaper of course allows VST usage.
One example use: Pro Tools.
Say you've got some tasty VSTs that you just gotta have in your project.
Pro Tools doesn't (and never did) allow VSTs (AAX only since versions 11,12; RTAS before that).
But you can use for example Reaper ReWire on a track in Pro Tools to pull it in; Reaper of course allows VST usage.
vinta9e
New member
Re: Slaving... a DAW
Good question!
The fact that whole DAWs can now function as plugins opens a world of possibilities in workflow flexibility; With such easy workaround each DAW's shortcomings you can now do different tasks in separate environments as you please. It is tremendous help when you think "A" sucks at tracking and "B" at programming abilities.
DAW "slaving" is IMHO one of the greatest inventions in audio engineering because it gives the user the choice to mix and match audio tools, virtually rewiring the chain just the way we do with pickups, pedals, preamps, processors, etc.
Owning my workflow instead of cursing the software engineers for imposing their ideas about way of working upon me sounds like a very practical proposition. The reduced effort of being productive is an immense ergonomic benefit.
Good question!
The fact that whole DAWs can now function as plugins opens a world of possibilities in workflow flexibility; With such easy workaround each DAW's shortcomings you can now do different tasks in separate environments as you please. It is tremendous help when you think "A" sucks at tracking and "B" at programming abilities.
DAW "slaving" is IMHO one of the greatest inventions in audio engineering because it gives the user the choice to mix and match audio tools, virtually rewiring the chain just the way we do with pickups, pedals, preamps, processors, etc.
Owning my workflow instead of cursing the software engineers for imposing their ideas about way of working upon me sounds like a very practical proposition. The reduced effort of being productive is an immense ergonomic benefit.
Re: Slaving... a DAW
Guys, Linux world had jack (e.g. qjackctl ) for ages. One thing of concern would be latency and synchronization. If lets say , one DAW does tracking/recording and the other one does the dirty job of applying the VSTs/LADSPA/lv2/etc , then the second one might not be up to the job, if all happens real time. Or one could record clean, and then just process a single track with the DAW/plugin of choice and then remaster.
Guys, Linux world had jack (e.g. qjackctl ) for ages. One thing of concern would be latency and synchronization. If lets say , one DAW does tracking/recording and the other one does the dirty job of applying the VSTs/LADSPA/lv2/etc , then the second one might not be up to the job, if all happens real time. Or one could record clean, and then just process a single track with the DAW/plugin of choice and then remaster.
GoldenVulture
Braindeadologist
Re: Slaving... a DAW
With todays Multi Core Proccessors , running two Daws on one machine should be a fairly acheivable thing to do.
I've got an eight core @4.7gig running my Daw computer. It can also take a stack of Ram. I've got sixteen gig in it.
You can tell some Daw's how many cores to use.
With todays Multi Core Proccessors , running two Daws on one machine should be a fairly acheivable thing to do.
I've got an eight core @4.7gig running my Daw computer. It can also take a stack of Ram. I've got sixteen gig in it.
You can tell some Daw's how many cores to use.
