Noita Audio Crackling Now

Unlike simpler games, Noita simulates every pixel of falling sand, fire, and blood. This puts immense strain on your CPU. The audio crackling is typically a symptom of "buffer underruns"—essentially, your computer is working so hard to calculate the physics that the audio engine gets starved of data [citation:2].

The issue seems particularly aggressive on systems with external audio interfaces (like Focusrite Scarlett or Fireface UC) and certain sound cards, though it can happen on any setup [citation:2][citation:3].

If you have an older sound card or the above steps don't work, installing universal ASIO drivers has helped some users.

Instead of a static buffer size (which often defaults too low for procedural generation spikes), implement a dynamic buffer management system. noita audio crackling

Logic Flow:

If you use an external audio interface (Focusrite Scarlett, Fireface, etc.), buffer size is critical.

Recommendations from users[citation:3]:

"At buffer sizes 256 and lower at all sample rates, nothing crackles. Odd that longer buffer sizes cause problems when it's usually the opposite in audio editing." - Noita player with Focusrite 2i4[citation:3]

If you are skimming this article to get back to the game, follow this order of operations:

While the silence from the developers regarding this 5-year-old bug is frustrating, the community's collective troubleshooting has provided a lifeline for those who want to enjoy the game without their eardrums being assaulted by distortion. If one fix doesn't work, try combining the NVIDIA tweak with the Sample Rate change—often, it takes a hybrid approach to finally kill the crackle. Unlike simpler games, Noita simulates every pixel of

This logic would be injected into the Audio Engine wrapper (FMOD handling).

-- Configuration Constants
local SAMPLE_RATES =  44100, 48000 
local BUFFER_SIZES =  1024, 2048, 4096  -- Steps to cycle through
function AudioSystem:Update(dt)
    local current_fps = GameGetFramerate()
    local underruns = self:GetBufferUnderrunCount()
-- Smart Buffer Logic
    if current_fps < 30 and underruns > 5 then
        if self.current_buffer_index < #BUFFER_SIZES then
            self.current_buffer_index = self.current_buffer_index + 1
            self:SetBufferSize(BUFFER_SIZES[self.current_buffer_index])
            GamePrint("Audio Stability Mode: Increased buffer to prevent crackling.")
        end
    end
end
function AudioSystem:ApplyRecommendedSettings()
    -- Detect CPU Core Count
    local cores = GetSystemCoreCount()
if cores <= 2 then
        self:SetBufferSize(4096) -- High latency, zero crackle
        self:SetMixingRate(44100)
    elseif cores >= 8 then
        self:SetBufferSize(1024) -- Low latency
        self:SetMixingRate(48000)
    else
        self:SetBufferSize(2048) -- Balanced default
    end
end

Before diving into fixes, it helps to identify your specific issue. The "Noita crackle" is not a one-size-fits-all glitch. Based on hundreds of community reports, the bug tends to follow three distinct patterns:

Players universally note that Noita is the only application that behaves this way, ruling out general "broken speaker" scenarios [citation:4]. If you use an external audio interface (Focusrite

This is the burning question on the Steam forums. As of late 2025, threads spanning five years remain active without an official hotfix [citation:1].

The most likely theory is that the issue is deep within the OpenGL and FMOD integration. Because Noita uses a falling-sand physics engine that processes every pixel, the CPU is often under unique stress. The audio engine seems to lose priority or fails to flush its buffer during high-physics moments. Since the issue doesn't affect 100% of users, replicating it in a development environment is difficult.