Can't figure out what's wrong 512 buffer (12ms) is usually OK, with occasional crackling still, but when I decrease to 256 samples or lower, I'm getting problems. I don't think there should be any underruns when the CPU load is around 20%.
FL STUDIO ASIO CRACKLING DRIVER
By switching to the FL Studio ASIO driver and increasing the buffer length to 2048, I was able to dramatically decrease the CPU usageįL Studio always shows at least some underruns in the Audio settings, no matter what buffer, including 512 samples.
Recently, FL Studio has created their own driver called FL Studio ASIO, which I found performs on par, if not better than the ASIO4ALL driver. So you'll have to bump it up to let's say. But once your track count starts to grow, it's hard for your CPU to keep up with this 512 buffer size. When you're first starting your project, you'll find you can use a really low buffer size, like 512, for example. FL Studio tells us that the single core speed is most important in selecting a CPU. While you're in there, make sure 'Multi-threaded mixer processing. This may seem like a no-brainer for some people reading this, but I have to include it in the list for one main reason: FL Studio recently added a function to triple the buffer size, regardless of what the driver is set to, and there are some people who haven't touched this option yet. This will allow you to hear the audio from FL Studio and other applications (such as YouTube, SoundCloud etc) at the same time Increase your ASIO buffer size. FL Studio ASIO has the advantage of being fully multi-client on most machines. This doubles the latency, but that ensures that there will be enough time to process each buffer unit. The triple buffer option works one buffer unit behind, and prepares audio for the next buffer period at each cycle.
0 kommentar(er)
