cpu problem

Try putting the sample rate from 44100 to 22050 in the audio settings (but don't forget to put in back on 44100 before rending it) that should do the trick grts 

The soundcard is just a numeric=>analo convertissor. The problem is probably your CPU. Try to close all other applications that could take some ressources from CPU.... or change it

could be driver of your soundcard, you have asio? if not there's asio4free also. My cpu went drastically down since i have an asio-driver and not just the windows thingie. but i assume you'll already have that, no?

also closing all antivirus stuff. Some system changes could do the job also: http://www.soundonsound.com/sos/sep06/articles/pcmusician_0906.htm

All of you are wrong :p

The latency of fl is not high. the problem is not your cpu, i have a dual core p4 1.70 ghz The problem is that you use to big plugins. plugins who are in beta etc... So, if you remove all those plugins, you will notice that your latency goes way down.

or another thing you can do if your pc supports it, go to options -> audio settings -> there you will see a bar with buffer length, take that bar up untill your hear clear sound. that sould fix it...

Originally posted by : Lordbone

All of you are wrong :p

The latency of fl is not high. the problem is not your cpu, i have a dual core p4 1.70 ghz The problem is that you use to big plugins. plugins who are in beta etc... So, if you remove all those plugins, you will notice that your latency goes way down.

or another thing you can do if your pc supports it, go to options -> audio settings -> there you will see a bar with buffer length, take that bar up untill your hear clear sound. that sould fix it... 

Yeah sure you're right, but the problem is that those plugins often rock big time...

My advice:

1. If available use an asio driver, put latency on max (2048 sample buffer length)
2. If not put buffer length on max, you will hear some delay
3. turn on 'switch smart disbale for all' (tools>macros)
4. Avoid beta crappy louche vst's as lordbone mentioned
5. Use high end vst's if you want but bare in mind that they consume lots of cpu
6. render if possible the lines created by those plugins (a sample consumes 0% cpu)
7. "but now I can't change my lines because they're rendered" --> save a new version for every major rendering session you do so you can go back in time to make new lines with the big plugins/alter old ones.
8. Mind the decay and feedback length of reverbs and delays, they consume huge amounts of cpu
9. Turn off unused processes or programs (allthough they often don't use more than 1-5%, a wrong plugin consumes more than all your programs together)
10. don't use 10 different reverbs when you can use one in a send channel.

thanks! raising buffer length helped. by the way where can i get asio? thanks

Originally posted by : LilDaze

thanks! raising buffer length helped. by the way where can i get asio? thanks 

You can use asio4all but I think onboard soundcards don't support asio.

Originally posted by : bandarlog

You can use asio4all but I think onboard soundcards don't support asio.

The asio4all should work on every soundcard I think (except maybe very old ones). I've used this driver myself on 2 computers with onboard soundcard and it worked splendid!

If you want to download the driver: just google "asio4all" and click some pages

Originally posted by : LilDaze

my cpu in FLstudio is sometimes way to high. So the sound is too chaotic and unclear, which makes it impossible work further.Is it due to my soundcard or is there a way to solve this? thanks  Maybe you should say on with Operating system you work before asking for help. And also wich soundcard you're using.