REAPER ran well, there was throughput I to O, sounded great.
VOILA! Very good latency setting, no problems listening and overdubbing. So I had him hunt down CoreAudio Mgr, open it, and set it to 64 there. So, first I had Uncle set the buffer in Protools Hardware Setup, then quite, then open RPR and see (the two programmes were never open at the same time!) Still no joy. Setting it only in RPR did nothing, and I realised (I have almost always used TDM, so have never messed with buffer settings for input latency) pretty quickly that this must need to be set either in Protools, or in Digi CoreAudio Manager, which is what would then tell RPR what is going on. So he called me, and together on the phone we went through some procedures trying to get the buffer down from 512 to 64. He very quickly set up a new tracking session, and everything worked well.except for latency in input monitoring. So I left, and Unc started messing around, learning how tings work in REAPERLand. It played fine, plug-ins all god, everything very fast and stable (except UAD-1, which crashes on VT insertion, but is fine as AU (I found this same issue on my Mac G5 PPC system).
#DIGIDESIGN COREAUDIO DRIVER 10.6.8 PLUS#
REAPER immediately recognised the 002, and in the Routing Matrix showed 16 inputs plus 16 outputs (although he only uses 2 outs, mixing and monitoring ITB).Ĭreated a new session, dragging in a 44.1 stereo WAV. His interface is a Digi 002, and there is also an Apogee Rosetta 800 feeding another 8 inputs via ADAT.
#DIGIDESIGN COREAUDIO DRIVER 10.6.8 PRO#
I went over there, and installed RPR OS X 32 bit, 4.261 plus SWS on his Mac Pro tower (Intel) running 10.5.8. He has been using Protools 7.4 LE up to this point. OK, I am liking working in RPR for the mixing I am doing recently, so I suggested to my friend "Uncletiffy" that he try it out in his very nice studio.
0 kommentar(er)
