So can you tell me more how buffer might affect CPU ? I never have had any time to learn about buffer.īuffer size generally affects cpu use in that the shorter the buffer the harder the cpu has to work to keep it filled. On the other hand I think NI instruments (especially REAKTOR) are very inefficient as well. Even if one uses sent tracks it will take some CPU power (and I'm not talking about using the CPU when they process the soun but the case when the sound is not going through them).Īmazingly I truned off every instrument, effect and pretty much everything in the project (it is only 10 tracks + 3 sends) and CPU is still on 2% - why ? I have no idea !!! I would say that Ableton should really review this and com out with some solution. For example 3 Filetered Delays (on separate tracks with different settings) eat up 1%. They do not use much but if you stack them up in different tracks the power adds up duickly. I also found that many Ableton FX eat up CPU even if not used (another words they are placed in track but no sound is going through them). NI REAKTOR-Prism eats up 20% of the CPU - wooow! OK, I just did some experimentation and found that: Then I could sync the two PCs with hte LAbleton LINK. I wonder if I purchased another midi-audio interface and route its outpub to the 1st interface then route the sound from the 1st to the speakers I can get this working (?). To be honest this is something that should be build in into Live. The only thing so far I have found was some add-on for Vienna Ensamble but they do not sell this separately and I'm not interested much in muying their Orchestral library just to get thie add-on. I'm also thinking about suncing two computers together, but so far not much info on that. No.2 was Ableton Weave Synth, so I really do not understand why Ableton device might cause this (as I have used some factory preset).Īny idea or experience how much would I gain by replaceing my i7 6-core with i9-8-core or AMD equivalent 12-core ? The majo CPU drag was caused by REAKTOR (with the its own plugin). ![]() ![]() I did some experiment and went through all track turning off devices one by one. I also changed my ASIO buffer size to 1014 samples but I think it is not only a sampled instruments causing this but rather processing. I do not have to save on memory as I have plenty of it. So can you tell me more how buffer might affect CPU ? I never have had any time to learn about buffer. Please share how you manage the CPU or if you know any tricks. I'm thinking how much gain would it make to replace it along with new mobo. Would replacing my i7 with i9 or 12-core RYZEN change a lot ? I wonder if there is any solution to that ? It seems that 2-3 years ago when I was running only Win7 and had less powerful PC I did not have that many CPU issues, or at least did not experience them when the sound was not played.I removed pretty much all unnecessary software possibly running in the background (not related to Live). I'm running 6-core I7 processor with 64Gb RAM on GIGABIT mobo and Win10-Pro. With 35% already used when I start playing some of the instruments PC already chokes and I get of course cracking sound and all kind of distortion. Why LIVE uses so much of a processor while nothing is played ? Is there any way to resolve this. When I open a project and do not do or play anything the processor use is already on 30-35%. I also have 2-3 effects on the routed channels. ![]() Omnisphere, Ableton Weave Synth, Serum, and some NI-Reaktor plugins). On those tracks I have some power hungdy devices installed (ie. I have a projects with 10-14 tracks (so basically not many). I want to know if everybody experience this issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |