how to save computer resources when producing music?

[IXM]

I have a computer that is not too similar, it is a laptop I7 6700eq 8gram, do you know the methods how to limit the use of the CPU and RAM memory in production?

 

[Archon]

There are surely DAW-specific guides on the interballs. I know there is an official one for FL Studio.

Other than that - dump dry/wet channels to WAV individually once you're satisfied with their sound and arrangement. It's always better to play raw audio than it is to generate it. You can even sample synths if it suits you. Keep in mind the automation if you have it and always dump stuff that is processed but static (such as kicks with a reverb, drums with delay/reverb which don't change etc.).

And also, be wary of the CPU-heavy plugins and processes. Modulation, delay and reverb can be quite intensive. So when you dump channels, dump them with delay/reverb on but without EQ/compression etc. which are generally easier on the resources. Know your synths too - Omnisphere and Diva are a bit heavy, whereas Predator and SynthMaster aren't. So you know which channels to dump to audio, and which ones to keep.

 

[Br8k L3gnd]

Yes, bouncing your midi and whatnot to audio will save greatly on cpu. Try not using the net on your production computer helps.

 

[IXM]

There are surely DAW-specific guides on the interballs. I know there is an official one for FL Studio.

Other than that - dump dry/wet channels to WAV individually once you're satisfied with their sound and arrangement. It's always better to play raw audio than it is to generate it. You can even sample synths if it suits you. Keep in mind the automation if you have it and always dump stuff that is processed but static (such as kicks with a reverb, drums with delay/reverb which don't change etc.).

And also, be wary of the CPU-heavy plugins and processes. Modulation, delay and reverb can be quite intensive. So when you dump channels, dump them with delay/reverb on but without EQ/compression etc. which are generally easier on the resources. Know your synths too - Omnisphere and Diva are a bit heavy, whereas Predator and SynthMaster aren't. So you know which channels to dump to audio, and which ones to keep.

thanks for the answer. will try to implement your tips, there's a bit of it. The only limitation is that my projects are very mobile until the end. I often change synthesizer sounds, I like to work with many effects to get an approximate picture of the whole thing, it always motivates me to work. I have to sort it out in my head and implement it, the more so because the projects are very simple and the resources are already scarce.

thanks

 

[Br8k L3gnd]

You can either always tweak synths or you can set it and forget it. I am the former, but the latter is supposed to be better.

 

[IXM]

You can either always tweak synths or you can set it and forget it. I am the former, but the latter is supposed to be better.

after 4 p.m. I come back home, dial the leads and pads and put them on wav. In fact, these are the elements that I adapt everything to.

 

[Archon]

thanks for the answer. will try to implement your tips, there's a bit of it. The only limitation is that my projects are very mobile until the end. I often change synthesizer sounds, I like to work with many effects to get an approximate picture of the whole thing, it always motivates me to work. I have to sort it out in my head and implement it, the more so because the projects are very simple and the resources are already scarce.

thanks

Well you can always dump and mute the instrument channel, then if you want to change something unmute it, change and dump again. And repeat.

 

[LostLegend]

Using BUS processing or send/return channels can help so you aren't using as many individual instances of things like reverb/delay etc.

Stock plugins are optimised for use in their respective DAW's so will usually be less resource intensive than their 3rd party counterparts.

For those using Ableton, it has a great 'Freeze' option, which allows to you convert an entire channel to audio (with the option of switching back when you need) and that can be a massive CPU saver!