Once I start playing a 25th track though, things grind to a RIDICULOUS halt - huge dropouts all over the place, the whole thing becomes unusable.Ģ4 tracks is a very hard limit - it goes from sounding smooth to total stuttering garbage in the blink of an eye. This makes sense since a 12-core machine with Hyperthreading = 24 virtual cores. Live: 24 tracks is as far as I can go without issues. Duplicate that track until you start getting CPU dropouts during playback. (c) No other plugins on the track - just the one instance of ACE. The VSTi used is u-he ACE on the default preset, but with Set up 1 VSTi track, playing a 1 bar monophonic MIDI sequence Audio interface buffer size = 512 samples U-he ACE is one of the most CPU-intensive synths around, especially when you start to stack voices, so I tried a simple test to gauge comparative CPU usage between Live and Reaper. Power-wise this thing is a behemoth, but Live brings it to its knees well before it should do, on a consistent basis.Īs an experiment, I set up a simple test project. Basically, depending on the specific content of a project, it's often the case that projects with a puny number of tracks can start to really produce major dropouts. Lately I've been frustrated by the state of multicore support in Live. Let me start by saying sorry - this kind of turned into a bit of a lengthy post.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |