Audio Crackling Problem on 0.27.1

Hi, I have a audio crackling problem for the last 2-3 weeks and now this problem is driving me crazy. I wonder if there is a solution?

There is the Audio Crackling sound :

 

Listen carefully 0:03-0:06-0:11-0:15-0:17

 

The audio recorded with phone mic. Thats why that crackling sound is quiet. The reason I recorded the sound with my phone's microphone is, in screen recordings, there is no crackling sound.
--- Post updated ---

The crackling sound coming out of my headphones has a very high ear scratching level.

 

The crackling sound coming out of my headphones has a very high ear scratching level.

I tried different headphones, speakers and bt audio. All same. Sooo it's not about my headphones.

 

I already tried the update audio driver way and it didn't work.

 

i have the same issue, weird thing is beamng is the only application that does this. i'll give an update if i can fix it, i'm planning on upgrading my sound card anyway from external usb to an internal pcie one (for desk space saving, but i also just want a pcie one lol), if this fixes it then maybe it'd be a compatibility issue between beam and certain sound cards (can't test motherboard audio though as headphones aren't compatible)

 

I have audio crackling as well, I thought it was my new klipsch speakers and tried troubleshooting, it turns out the new speakers just allowed me to hear the problem better. It appears to be that while the Audio crackling is happening, my T150 steering wheel inputs would also be stuck at whatever the input level was when the crackling started, until the crackling stopped. For some reason when I changed the usb slot the steering wheel was plugged in it fixed the issue for the wheel, but the audio crackling persists. I have fairly good pc specs however only 16gb of ram, I have no idea but maybe I need more ram?

 

I have a similar problem, except instead of crackling, audio breaks up. (Although not all of the audio has this problem, only water sounds, car horns, and cars driving by.)

 

Hello, first of all sorry for the spelling, I use google translate.
While I was writing a message to say that I had the same problem I managed to solve it.
I have an AMD graphics card, and opening the software for my graphics card, namely AMD Software: Adrenaline edition, immediately eliminated this bug. I have no idea where it came from, but for me the problem is solved!

UPDATE litteraly 2 min after, problem is still here, but disapear when i start recording with the amd software ? Maybe a bug with amd graphic card ?

 

I have Nvidia card with high quality stereo monitors, i looking at finding a solution

 

I have the same issue as well, is it not unlikely that this is a game issue as more than a few people have the same problem all of a sudden?

 

This can be sometimes caused by a Thrid Party audio app like for example "Voicemeeter". I suggest running BeamNG through your Headphones and not through Voicemeeter Input

Edit: I also believe that it is because Your system is Overloaded by any background running apps, sometimes they can be in your hidden Icon (next to your Language/On-screen keyboard) or in your task manager

 

I was on my AMD PC with NVIDIA RTX 3060 Ti, with powered laptop speakers hooked up to the default sound card 3.5mm output and getting lots of crackling/popping. If I used my SteelSeries headphones, I would not get crackling or popping.

Edit: I thought I had a solution, but I still have crackling/popping. It seems like less noise with "Stereo Headphones" unchecked in "Options > Audio". I got carried away and thought it was completely fixed. Sorry to revive the dead thread. I'll go trace my audio equipment in shame, unless someone else can prove I'm not crazy.

 

I have the same issue people. On ShadowPC as well as with NVidia GeForce Now. Hasnt been before a long time ago...

I tried multiple headphones and speakers. Wired and BT... Really annoying

 

I believe I kinda found out what the problem is...

I have upgraded my system to

- NVidia RTX
- 22GB RAM
- 32 Core 2,5GHz

this issue becomes less. not fully solved but less intense.

So this means it`s probably an resource issue. This is new to me. I am used to use less power and BeamNG has run like a charm. Today BeamNG needs way more computing power. But I assume not everyone can have such a big power system like I do...