The attached file is the problematic file and an image of where the distort happens
I am a small youtuber making videos as a hobby but few weeks ago I have been hearing this pop in the audio
after some research, it seems like a problem with
cpu / ram overload? low pch voltage?
too small buffer size? probably not, it was 512 and even happened at 1024
audio interface faulty?
my setup is
CPU: Ryzen 5900x / cpu is not overclocked
MB: MSI MPG X570 GAMING EDGE WIFI Gaming Motherboard AMD AM4
RAM: G.SKILL Trident Z Neo Series 32GB (4 x 8GB) 288-Pin PC RAM DDR4 3600 / Ram is overclocked to 3600
PSU: Seasonic FOCUS GM-750, 750W 80+
audio interface: iD4 mk2
mic: Earthworks ETHOS
sample rate: 24bit 48000
I think it is a problem with the motherboard struggling with low voltage or something like that
but I really want to learn what is behind this phenomenon
I would love to learn and provide you more information if you need more to understand the problem
If you know why this happened or seen another post with a similar issue, I would be more than happy to learn and read the post
too small buffer size? probably not, it was 512 and even happened at 1024
audio interface faulty?
Probably #2 and multitasking.
Sometimes it’s better with a smaller buffer but I don’t know why and that goes against the theory.
You should also try to minimize any background operations. (Some people have to temporarily turn-off their anti-virus or Wi-Fi.)
If you can’t find an easy fix, there is a free online book about optimizing your computer for audio called [u]Glitch Free[/u].
\
The operating system is always multitasking (and interrupting) even when you’re running only one application. That’s why you need buffers…
When recording, the digital audio stream flows into the buffer at a smooth-constant rate. Whenever the operating system gets around to it, the data is read from the buffer in a quick burst and written to the hard drive. If something is “hogging” the system for a few milliseconds too-long you get buffer overflow and a glitch in your audio. Note that whatever is hogging the system doesn’t have to be using lots of total CPU time/power, it just has to hog it for a few milliseconds too long.
A bigger buffer helps (usually) and a faster CPU helps because it can finish-up the other stuff faster and get back to the important stuff (audio). …PCs have been fast-enough for regular-simple stereo recording for decades, so CPU speed isn’t the root problem.
There is also a playback buffer that works the opposite way. It’s filled in a quick-burst and the audio data flows-out smoothly. In this case the danger is buffer underflow.
So I recorded this with OBS with normal priority, but this even happened at high priority
I will try it with the smaller buffer size
I play games with this one PC and record it with obs at the same time, usually this never happened for 2 years
but somehow like few weeks ago, I started to notice this, maybe something broke or got faulty?
this also happened when I was playing a youtube video, the video had some distorts like what you see up there, but in playback!
I played the video in my phone and it wasnt there, the pc had a playback buffer problem. i rebooted with higher buffer size and overclocked the ram to 3600 again and it was gone.
I think its something to do with the PC itself, honestly there are so many reason so I might just replace my PC as a whole
my reasonable guess is that the mainboard is known to be kinda finicky with the usb controller, i had a problem with the camlink freezing and it was a usb controller overload problem, also the ram is overloaded to 3600 and its drawing a lot of voltage? that other system is having trouble? i dont think cpu is the problem since parts like cpu barely get faulty.
I dont think this is a problem with the mic (ETHOS) or the audio interface (iD4 mk2)
my final guess is the motherboard being weird
thanks for everyone who tried to help me, it gave me some insight
Also, I saw someone mentioning if these “ticks” always happen in the beginning of the recordings, and yes, about few seconds in, like 1 to 3 seconds, there is an audio drop-out and after that, its some random points.
Clue in the title.
I approximately reconstructed the missing piece of waveform by copying & pasting ~6ms of the preceding waveform to replace the discontinuity. Repairing the ends of the pasted-in patch.
