banner

Announcement

Collapse
No announcement yet.

Slaving... a DAW

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Slaving... a DAW

    Yes, you can slave a DAW within a DAW.

    For example, Reaper can be slaved into ProTools via ReWire.

    ***mind blown***

  • #2
    Re: Slaving... a DAW

    can't imagine how slow my computers would go with two of those dumb things running

    Comment


    • #3
      Re: Slaving... a DAW

      What would be the point?

      Sent from my MotoE2(4G-LTE) using Tapatalk

      Comment


      • #4
        Re: Slaving... a DAW

        Because you can... like you can sync multiple computers and run multiple daws together.
        sigpic

        - http://www.soundclick.com/bands/defa...?bandID=804435 -
        - https://soundcloud.com/mr-ds-bigband/tracks -

        Warning: May contain traces of NUTS

        Comment


        • #5
          Re: Slaving... a DAW

          I never knew this, but I can't quite think of a practical application for it, at least the way I record.
          Administrator of the SDUGF

          Comment


          • #6
            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.

            Comment


            • #7
              Re: Slaving... a DAW

              Originally posted by Demanic View Post
              What would be the point?
              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.

              Comment


              • #8
                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.

                Comment


                • #9
                  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.
                  sigpic

                  - http://www.soundclick.com/bands/defa...?bandID=804435 -
                  - https://soundcloud.com/mr-ds-bigband/tracks -

                  Warning: May contain traces of NUTS

                  Comment

                  Working...
                  X