ProVerb has to do its thing no matter how many tracks you have. But 128 is definitely stretching it with two ProVerb instances and Omnisphere. Now, I can leave most things running (if they don't have a built in delay such as look-ahead compressors) and track at 256 or 128. In order to track back in the PowerPC days (Dual G4), I had to turn off all plugins and instruments and track with MIDI at 64 or 128 samples to avoid noticeable latency. I used to have to run at about 1024 samples for mixing.
So, the buffer numbers aren't really going to go down as much as you'd think.
Put another way: lower read-time latency means less time to process other stuff.
Thus, any speed increase is negatively compensated by the resulting decrease in processing time, compared with a slower computer which requires more time to read the samples. (I've finessed that statement, because it DOES improve, but not as much as you would expect.) The reason, as I have thought it through, is probably because it does read them so fast, narrowing the processing margin as a result. My experience has been that the faster CPU doesn't necessarily make lower buffer rates much more desirable. In fact, it may be preferable to 128 samples, because it reads so fast, yet it still has to process the tracks, instruments, and plugins in that short time. A 256 sample buffer shouldn't cause much latency with that rig. But really, three tracks of ANYTHING shouldn't stifle a yawn out of that computer, much less break it into a sweat. Omnisphere (from what I've heard) can be pretty CPU intensive, too. Work Priority = Medium (you can read about it in the "Getting Started" (the little) manual, page 23) Hamburski wrote:Ok, I'm wondering how this is possible. One thing to keep in mind when you get to a higher track count: DP works better on multi core machine using a separate instances of the VI, each with a small number of sounds, than a small number of VI instances each with a lot of sounds loaded. Switching to WordClock or Internal made that go away. You might not expect the timing problem reported by DP would be the cause of CPU overload, but I've had the same symptoms (reports of CPU overload) using an ADAT source for timing. With MachFive, I set this to the maximum possible, taking advantage of as much RAM as the VIs are able to use. Maybe there's a problem with disks.įollowing on the possible disk problem, look VI settings that determine how much sample data your VIs preload. Look in Activity Monitor to see if CPU spikes happen at the same time that disk activity spikes. Look at Activity Monitor and see what it says. Turn off the Audio Performance meter, and never look at it again. Things settled down and I haven't see the problems since although I don't which, if any of these solved the problem. My bad for drinking the Cupertino Koolaid, I guess. Obviously I was assuming that, having upgrading so dramatically after seven years on my old machine, this sort of thing would be nonexistent. I've opened the Audio Performance window and there seems to be room to spare, though I see that when starting or stopping playback there will be a momentary spike into solid red, which seems suspicious. Oh yes, and I'm using an Apogee I/0 (2圆) with the latest firmware and software.īased on other threads, I've considered monkeying with other hardware configurations - currently I have the work priority on High and the host buffer multiplier on 1.
No sound audio overload software#
Check to make sure hardware or peripheral settings are setup correctly or disable the audio hardware for MIDI playback only."Īnd, sure enough, then there's no sound, and I have to reboot my interface, relaunch its software (Maestro), and reboot DP. If I click Continue and hit play again, there's no click, and soon after I get: "DP is not receiving a clock signal from the audio hardware. I have the buffer on 128 - ok, but I've done that on my old dual-core Snow Leopard rig with a lot more running.Īnd yet - I am getting this: "Audio playback has overloaded your computer's processor. And I'm bussing the acoustic guitar out to two parallel instances of DP's Proverb. I'm currently working on a session with a 10-minute quicktime file loaded and just three - count 'em - tracks so far: an acoustic guitar track with one DP plugin on it, an electric track with one instance of Guitar Rig 5, and one Omnisphere instrument. I'm running all the latest updates of my Spectrasonics and Native Instruments plugins.
No sound audio overload mac#
New 6-core Mac Pro, 16GB Ram, OS X 10.9, DP 8, two 1TB external SSDs for samples and sessions.
0 kommentar(er)
