Straight to the point;
My projects require too much CPU. My Fruity Loops is crackling and lagging when I have some automations, eq's, synths, compressors, you name it running.
Tomorrow I get a new GPU and PSU from a friend, but my guess is that those wont solve my problems.
I really dont know anything about my sound card, or if I even have one at all. I think I have about 2/3 gigs of RAM DDR2. And thats about it from what I know of computers.
I could use some advice on what I need to upgrade.
Thanks in advance.
Go in to your audio settings and turn your buffer size/latency up.
What CPU do you have and how much RAM do you have? How many tracks/effects can you use before you having problems?
Yeah tweaking buffer settings is really the only thing you can do now. And even that won't probably help. I used to have a shit ass computer (2 gigs of ram, old as hell intel dual core CPU) and making tracks was HELL with it. Just get like 8 gigs of ram and a real CPU and you will be fine. You will probably have to change out your motherboard too.
If you can't afford that kind of money right now, try bouncing tracks to .wav and getting rid of the effects and shit. That's what I did for a while
Also make sure your computer isn't on balanced power mode (go to control panel -> system and security -> power options and make sure you are on high performance)
If you're working with MIDI, bouncing the track down with all its effects and using a WAV or something will reduce the CPU usage like crazy. Right now, your computer might be trying to process every instrument and its effects on the fly.
[QUOTE=KSCK26;43540296]If you're working with MIDI, bouncing the track down with all its effects and using a WAV or something will reduce the CPU usage like crazy. Right now, your computer might be trying to process every instrument and its effects on the fly.[/QUOTE]
Once you've laid down the midi track convert it to raw audio always, with no effects. mute the original midi track in case you need to reuse it later. This saves on CPU usage and you can still mix. It's no use rendering tracks with effects on them because it's destructive - if you need to change it later you're stuck.
Could you post your specs?
[QUOTE=KmartSqrl;43538553]Go in to your audio settings and turn your buffer size/latency up.
What CPU do you have and how much RAM do you have? How many tracks/effects can you use before you having problems?[/QUOTE]
It was half was, so I put it all the way up now. This solved most of the crackles, but now some visuals lag. But what ever, this is by far alot better then FLS making some tune -10 bpm which is actually 140 lol.
My RAM is about 2/3 gigs DDR 2.
[editline]15th January 2014[/editline]
[QUOTE=CLungcancer;43539959]Yeah tweaking buffer settings is really the only thing you can do now. And even that won't probably help. I used to have a shit ass computer (2 gigs of ram, old as hell intel dual core CPU) and making tracks was HELL with it. Just get like 8 gigs of ram and a real CPU and you will be fine. You will probably have to change out your motherboard too.
If you can't afford that kind of money right now, try bouncing tracks to .wav and getting rid of the effects and shit. That's what I did for a while
Also make sure your computer isn't on balanced power mode (go to control panel -> system and security -> power options and make sure you are on high performance)[/QUOTE]
I never knew I was able to even change that on a desktop. Turned it to High Performance now, thanks.
Also the cracky ass computer you talk about is about what I use at the moment, hehe. But today I get my new GPU, I'll post the details later. (NVIDIA GTX 460)
[editline]15th January 2014[/editline]
[QUOTE=KSCK26;43540296]If you're working with MIDI, bouncing the track down with all its effects and using a WAV or something will reduce the CPU usage like crazy. Right now, your computer might be trying to process every instrument and its effects on the fly.[/QUOTE]
I've thought of that very often, but wont I loose alot of quality by doing that? Since I export, import, and export it later again?
[QUOTE=Nubcake.;43545283]I've thought of that very often, but wont I loose alot of quality by doing that? Since I export, import, and export it later again?[/QUOTE]
No, because when you need to make changes you just delete the audio and edit the original midi clip and then bounce it to audio again. You can also absolutely do this with effects included in the audio file because that will save you even more processing power, not sure what killerteacup is on about because you don't need to delete any of your original bits.
A lot of DAWs have a button you click that does all this and unloads the plugins for you and then just reloads them when you click it again to edit the track. This is called freeze/unfreeze in most DAWs, but FL studio has no built in button for it for some reason.
[QUOTE=KmartSqrl;43548178]No, because when you need to make changes you just delete the audio and edit the original midi clip and then bounce it to audio again. You can also absolutely do this with effects included in the audio file because that will save you even more processing power, not sure what killerteacup is on about because you don't need to delete any of your original bits.
A lot of DAWs have a button you click that does all this and unloads the plugins for you and then just reloads them when you click it again to edit the track. This is called freeze/unfreeze in most DAWs, but FL studio has no built in button for it for some reason.[/QUOTE]
A friend of mine uses Ableton and I rember him showing me how to do that freeze stuff in Ableton. By my knowledge there is indeed no build in way to do that in FLS. I think I'll try to make .wav's from my synths. Even when I havent made something with a synth in my piano roll it still kills my CPU just by sitting in my pattern unit.
[QUOTE=Nubcake.;43550262]Even when I havent made something with a synth in my piano roll it still kills my CPU just by sitting in my pattern unit.[/QUOTE]
Are you saying that just by opening a software instrument, you already see a decrease in system performance?
[QUOTE=KSCK26;43551810]Are you saying that just by opening a software instrument, you already see a decrease in system performance?[/QUOTE]
If I go to channels > add one > "random synth" then it uses CPU. For example, if I am allready working on some project, and decide to add another synth, then I see my CPU drop only by adding it to the window where I can control my patterns. ( When I hover my mouse above the interface on top I see it's called Step Sequencer )
Your best bet is still to write the part you want in your pattern editor and then bounce it down to audio. After you have the audio tracks, disable the synths unless you need to edit the notes. Just keep replacing MIDI tracks as much as possible and make sure your software instruments are turned off; hope it helps, man.
[QUOTE=KmartSqrl;43548178]No, because when you need to make changes you just delete the audio and edit the original midi clip and then bounce it to audio again. You can also absolutely do this with effects included in the audio file because that will save you even more processing power, not sure what killerteacup is on about because you don't need to delete any of your original bits.
A lot of DAWs have a button you click that does all this and unloads the plugins for you and then just reloads them when you click it again to edit the track. This is called freeze/unfreeze in most DAWs, but FL studio has no built in button for it for some reason.[/QUOTE]
yeah you're right, I thought he was being told to process with effects then remove the original track, not sure why
keep the stems and just mute them, export out as a .wav and import back in, simple
Tools > Macros > Switch smart disable for all plugins.
This works great for me when it starts crackling because of too much CPU usage, not sure if it works in the long run. Depends on the project setup, I guess.
make sure that if you can, you're using the asio4all drivers. it's in the audio tab in settings in input/output.
Sorry, you need to Log In to post a reply to this thread.
