It not only is more slow but causes audio glitches.Įverytime Sigmund is reset, on playback, on transport and when stopping all sounds an audio glitch occurs. Repositioning the cursor even once causes the same issue, and dragging the cursor into position is a normal use case for me.

A lower buffer length increases the amount of underruns, but using 512 or 1024 samples will still cause the same issue. Understanding the ASIO driver configuration. The buffer stores audio data from FL Studio before its sent to your audio interface. Virtual DJ, Traktor, FL Studio or Ableton Live to name a few). The example was a worst case scenario to highlight the problem, but not exclusively the situation when it happens. Buffer length You don’t need to worry about most of the settings here yet, but you definitely should know what the Buffer Length does. Can you tell me whether the buffer underruns appear when Sigmund is used in normal conditions when you replay a song, or a loop in the project? In the situation you visualize there's lot going on internally (especially when delay lines or modulators are synced with host's tempo) when the plug-ins tries (few times per second) to catch-up the exact PPQ (cursor position) of the project and reinitialize buffers accordingly (especially when we speak of 2ms long ASIO buffer, which is quite achievement alone for USB audio interface) - these kind of procedures are launched only for such occurrences and aren't triggered very often when you just hit play. I'm speaking of grabbing cursor and fiddling back and forth. I don't suppose this is very real-life situation here.

Buffer length fl studio