If you need a lot of PLAY instruments, loading up multiple instances of PLAY (with convolution reverb off until you absolutely need it) is always better than trying to pack everything in one instance. Also, I've posted this elsewhere, but definitely try to avoid putting more than one instrument on any instance of PLAY, two might even be pushing it. There's a few workarounds: 1) turn of pre-render 2) make sure your hardware buffer is set as high as it will go, which will off-load a little of the processing to your interface and 3) try setting your project sample and bit-depth down to 44.1 kHz/16-bit during the composition phase, then, turn it back up to your preferred sample rate/bit-depth when it comes time to lay off the audio. In my case, it's a tradeoff, because I can run more instances of PLAY on my dinky MacBook with pre-rendering on, but having more instances of PLAY (along with whatever other VIs you're running in your project) seems to overload the processing. Unfortunately, I think the dropouts, which seems to happen a lot in DP 6, are due more to overloading the processor with pre-rendering than the OS. The newest version of PLAY (1.23) runs fine on Tiger (which is how I'm using it). I can't speak for the new machines with the 2.5Ghz firewire buss, but I've found that SATA and eSATA work much better than the older 33Mhz firewire busses, which simply do not handle the quantity of data or drives nearly as well. My MacPro has a 5-drive eSATA "brick" connected to a Sonnet PCIe eSATA host card. Important note: I am running each section of the orchestra from a different hard drive. I knew then that I could scale back my templates and still have a more than enough sounds to work with.įor EWQLSO Platinum Plus, I have recently purchased a second license and am running brass and percussion from my G5 2.5 Dual (8GB) in 10.4.11 and DP 5.13 and the winds/strings on my MacPro in 10.4.11 with DP 5.13 as well as with DP6.02 in 10.5.6. DP ran sluggishly and was practically unusable with all that data, but it didn't crash. In both cases, it was clearly much more than I would want to run at one time- especially a dozen drum kits and basses in FabFour (which doesn't make musical sense), but it was just a stress test. In both 10.4.11 and 10.5.x I've gotten nearly all of FabFour loaded (40+ instances) and in another project pretty much all of the EWQLSO key switch patches loaded at once (20+ instances with a dozen or more patches in each). If it's of any consolation, I have a late 2006 MacPro 3G Quad with 8GB RAM. One unfortunate reality DAW users must still deal with is some trade off between latency and stability. Smaller projects can benefit from smaller numbers. Larger projects will require larger numbers. That will be your performance threshold based upon a given amount of samples you have loaded. If so, dial back these numbers to see where things begin to choke again. In DP, make sure Pre-fill buffers for quick start is turned OFF (ie: unchecked). In DP, set your Work Priority to Medium- and then try the test again with Work Priority set to High.Ħ. In DP, set VIs and all plugins to run in real time.ĥ. In the PLAY Settings, set your PLAY buffers to 512.Ĥ. In the PLAY Settings, set your Engine Level to 2.Ģ. I have no experience with rewire, although that may be a solution until EASTWEST and/or MotU resolve whatever is causing the problem.ġ. I have upgraded to Leopard and doubled my RAM and just bought Logic Express in order to see whether PLAY is more stable with a different host. I have 4 - 5 hours days ahead, if anything pops up, will let you know.Maswot wrote:Thanks for all your posts. Using Lynx Aurora (n) 16 channels of conversion. Using Fabfilter EQ, latest version, on most of the tracking channels when needed. The template also has a headphone feed built in. The template is loaded with Omnisphere, and Keyscape for quick access to some layers of sound while tracking. Not had one hiccup after about 10 hours of running the DAW, routing to 4 different hardware effects units and 3 different hardware compressors. I am tracking an album for the next couple of weeks here and I spent last weekend setting up a new template in Win11 and PT 20.12. I will really like to upgrade to the latest Windows OS and want to ensure I do not have any hiccups with pro tools. Anyone running pro tools on Windows 11 and what is your experience. It has been one month since Windows 11 came out and I am struggling to find information on whether Protools is compatible with windows (unlike some other DAWs we have already confirmed their compatibility). I am using latest version of pro tools (2021.10) on a windows-10 laptop and my windows laptop is compatible to run Windows 10.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |