![]() Hit Apply and then OK to close the Performance Options window.Ĭlick OK to close the System Properties window. Under the Processor Scheduling section, select the Background Services option. ![]() In the Performance Options window, click the Advanced tab. Under the Performance section, click the Settings button. (or type in advanced system settings) in the search (this was taken from Protools optimization suggestions)Ĭlick on the Start Menu, type System, and press Enter. ![]() This optimization seems to allow the computer to run Cakewalk more efficiently. Here you all go for a potential solution. The plugin is still there sleeping with settings intact if you need to access it again. Freezing is reversible as you can unfreeze a track with just a click if you want to modify the FX, then re-freeze it. Freezing bounces that track down to audio in-place with the FX baked in, then sets the plugin to an offline state. Even if you are maxing out only 1 of your 6 cores, that will result in audio breakup.Īnyway, try recording with AmpliTube 5, and then freezing your track as you go on to record the next track, etc. Don't know why Reaper and Cakewalk would be that much different, but there could be differences in their audio engines or load balancing. If you are using it on more than one track at a time it will add up quickly. so very little reason for this that i can see.ĪmpliTube 5 is pretty computationally intensive (CPU usage), with their new modeling technology. i hit the alt G to watch during the playback. so may have to mix there.Ĭakewalk does not show much resource use. Had no problem in Reaper with AMPLITUDE clicking. The only thing that seems to work is to record with another vst. Running i-7 8700, 2 x m.2 2tb, plenty of disk space, ASUS Prime 370A MB, win 10 圆4 no problems with guitar rig 5 or 5guitar rig 6 Or, as you are done with a track, freeze it before working on a new track.Ĭlickety clack scratch scratch with cakewalk and amplitude 5. if you are not using the latest stuff, Mesa Boogie 2 and the X pedals, you can revert to version 5.0.3 which uses quite less CPU.And in any case you would have to do it every time you start your project. It is a known bug that I have reported to IK last September. And in last summers group buy thread, if I remember is right that changing the routing decreases the CPU usage. The CPU usage of Amplitube 5 has been discussed in this thread. If any can help me fix this, I would be more than happy. I have tried setting the buffer size to maximum, during playback and it is still cracking.įor some recordings it would be fine to have no effects as I can add them later, a little bit like reamping, however, the song I am currently working on, really needs effects, as it needs them for the recording vibe. I have set everything correctly, buffer size ASIO etc, I can make the cracking stop by putting most tracks on standby via the fx bypass rack, this would be no problem if I was mixing or Gain staging. I downloaded Amplitube 5 free a couple of months ago and last weekend, I upgraded it to Amplitube Max.Īfter spending time enjoying the different sounds and settings, I decided It was time to start recording.Įverything started off fine, however, the more track I recorded, the audio started to crack, this has got worse with the more tracks I have added, causing audio dropout.
0 Comments
Leave a Reply. |