Popping in the audio. ( Surprise it's not the mic)

[Sawyer Anderson]

So after two days of getting pissed off and about to file a ticket to get my mic checked out and repaired i decided to one more test.

This test had me go back to the video the same time the poping shows up in my audacity line up.

Help please.PNG (51.72 KiB) Viewed 735 times

To my surprise the poping is not in the original .mp4 file recorded by OBS. After doing some more digging my only conclusion is it is audacity. This is futher proven that i made a OBS recorded muted the mic ( Blue yeti) And the spikes where still in the audio even when there is no audio.

I have lost many videos to this noise that ive been able to slightly fix through leveling it all out but i would like to know what is causeing this problem to avoid it in the future.

[Sawyer Anderson]

Also since i can't find the edit

Mic is a Blue Yeti

OS is Windows 10

2.1.2 is my audacity

And i want to say it was the .exe installer

[steve]

Does the problem still happen if you record with the project rate (lower left corner of the main Audacity window) set to 44100?

[Sawyer Anderson]

Does the problem still happen if you record with the project rate (lower left corner of the main Audacity window) set to 44100?

It does not as far as i can tell however i would prefer not to have to use audacity dureing my recordings since OBS recording are done with the streams done over OBS.

I'm also posting another picture. The Tracks in order are 1.mixed 2.Mic 3. game audio

What strikes me as odd is in the mix of both the game and mic audi there is only 1 spike where the mic audio has 9 ( not counting the far right one that matchs as that was a sneeze)

Odd very odd.PNG (72.57 KiB) Viewed 717 times

[Sawyer Anderson]

Here's another of a different video no spikes in 1.track one ( Game and mic ) But plenty of spikes in Track 2. ( Mic ) And no Spikes in Track 3. (Game)

Another.PNG (64.87 KiB) Viewed 650 times

[steve]

Are you trying to record with OBS and Audacity at the same time?
What exactly are you trying to do? What's your set-up? How do I replicate your set-up so that I can replicate the problem?

[Sawyer Anderson]

Are you trying to record with OBS and Audacity at the same time?
What exactly are you trying to do? What's your set-up? How do I replicate your set-up so that I can replicate the problem?

No Both my Audio and Video is recorded in OBS through a 1-3 track system 1. mixed 2. mic 3. Game. I then Import the audio int audacity for editing and cleanup. However in the past few weeks it's been adding those spikes in there even when their not in the .mp4 file when i go to that same timestamp.

All i'm wanting to do is to find out why audacity is adding audio spikes that don't exist into the files and how to prevent it without haveing to edit them out every single time.

[steve]

Both my Audio and Video is recorded in OBS through a 1-3 track system 1. mixed 2. mic 3. Game.

The punctuation is ambiguous, but I think you're saying that you record everything via OBS, and that produces a .mp4 file which you import into Audacity for editing. Have I understood correctly?

I then Import the audio int audacity for editing and cleanup. However in the past few weeks it's been adding those spikes in there even when their not in the .mp4 file when i go to that same timestamp.

I think I know what's happening.

Digital audio data ("PCM" audio) is just a series of number. Each number represents the amplitude of the waveform at a specific point in time on a specific audio track. Normally these numbers are in the range -1 to +1. In special cases, sample value may be greater than 1, or less than -1, but they must always be numbers.

Inside the computer, numbers are represented as a sequence of "on" and "off" states. This is the computer's binary representation, called "bits". Some sequences of "bits" represent numbers, so represent characters, some sequences don't represent anything.

When dealing with numeric values, there are three types of "special" values that can cause problems. "Infinity", "negative infinity" and "NaN". These values should never occur in valid audio because they are not "valid" numbers. I suspect that the imported .mp4 file contains occasional "corrupted" sample values that are not valid numbers, and that it is those invalid numbers that are producing the clicks.

To test this theory. Zoom in close on the start of the click and select a tiny bit of audio starting just before the click and ending just after the click. The selection should be less than 100 samples. Then use the "Sample Data Export" tool (http://manual.audacityteam.org/man/samp ... xport.html) to export the sample values to a text file. Set the "Measurement scale" to "linear". Then open the exported text file and look carefully down the list of numbers. I'm expecting that at the start of the click there is an infinite, negative infinite, or NaN value.

[Sawyer Anderson]

Both my Audio and Video is recorded in OBS through a 1-3 track system 1. mixed 2. mic 3. Game.

The punctuation is ambiguous, but I think you're saying that you record everything via OBS, and that produces a .mp4 file which you import into Audacity for editing. Have I understood correctly?

I then Import the audio int audacity for editing and cleanup. However in the past few weeks it's been adding those spikes in there even when their not in the .mp4 file when i go to that same timestamp.

I think I know what's happening.

Digital audio data ("PCM" audio) is just a series of number. Each number represents the amplitude of the waveform at a specific point in time on a specific audio track. Normally these numbers are in the range -1 to +1. In special cases, sample value may be greater than 1, or less than -1, but they must always be numbers.

Inside the computer, numbers are represented as a sequence of "on" and "off" states. This is the computer's binary representation, called "bits". Some sequences of "bits" represent numbers, so represent characters, some sequences don't represent anything.

When dealing with numeric values, there are three types of "special" values that can cause problems. "Infinity", "negative infinity" and "NaN". These values should never occur in valid audio because they are not "valid" numbers. I suspect that the imported .mp4 file contains occasional "corrupted" sample values that are not valid numbers, and that it is those invalid numbers that are producing the clicks.

To test this theory. Zoom in close on the start of the click and select a tiny bit of audio starting just before the click and ending just after the click. The selection should be less than 100 samples. Then use the "Sample Data Export" tool (http://manual.audacityteam.org/man/samp ... xport.html) to export the sample values to a text file. Set the "Measurement scale" to "linear". Then open the exported text file and look carefully down the list of numbers. I'm expecting that at the start of the click there is an infinite, negative infinite, or NaN value.

It does not seem to be what you suggested i did a few more then 100 samples due to the spike not being 1 big spike ( picture below ) along with the .txt.

All 4 High areas seem to be the spike i hear on the audio.

Sigh.PNG (61.49 KiB) Viewed 581 times

[Sawyer Anderson]

I can confirm that this is an audacity issue. In the attached file i have Audacity and then another audio program. Only Audacity is showing the spike. As mentioned before you can't hear the spike on the mp4 before i import it into audacity so it's not something that is there by default.

Oh boy.PNG (193.65 KiB) Viewed 563 times