Obs studio recording come out bad Pc#

I do not click anything because in the video everyone can see that I am not in front of my PC.ĭue to the fact that the Audacity recording is fine on the same PC I think this issue is caused by OBS. These drop-outs or 'breaks' happen randomly. The bottom waveform (=OBS) is earlier in time.Īfter seeing that I was thinking that the drop-out is more like a 'break' in the signal because when you delete it and move the bottom waveform to the right, both are aligned all the time. You can see that the waveforms are not aligned. The second picture is before the audio-drop out. To get the first picture I aligned the waveforms after the drop-out. Audacity looks fine but OBS is struggling.Īfter scrolling through the waveforms I found this:

Obs studio recording come out bad mp4#

Recording is set to 'stream encoder' (nvenc), mkv and remux to mp4 afterwards.īoth audio-tracks are recorded using the same interface on the same computer. On the top there is the recording done with Audacity and on the bottom there is the audio-track from the recorded video. The soundcard gets the S/PDIF clock from the mixer and is locked to it.Įvery soft- and hardware is set to 48kHz. My signal chain: Pioneer DJ Mixer puts out 48kHz signal via S/PDIF into the Focusrite Clarett. I found a simillar or maybe the same issue in my latest stream recordings. What I have tried to solve this issue is basically waiting for the buffer to be filled, like this in audio_callback.

Obs studio recording come out bad code#

I’m not familiar with the OBS code base and the audio processing happening, but to me it seems like the problem is the fact that in audio_callback(), it always takes a fixed amount of data from the audio buffer ( audio_size = AUDIO_OUTPUT_FRAMES * sizeof(float)) even if the buffer is not sufficiently filled due to potential delays in the capture thread.

The attached log file includes a debug message (Capture size: 480) I added, it outputs the captureSize variable in ProcessCaptureData() to check for any changes in amount of data being returned there. When an audio dropout occurs, the message “can't discard, data still pending” is seen in the debug output (if compiled with DEBUG_AUDIO). The issue is not limited to recording but also applies to streaming. The issue is not limited to recording from desktop audio but also applies when recording from external USB audio interfaces. There are systems where I was not able to reproduce the issue, though I did not make excessively long recordings (> 4 h) to eliminate the possibility of the issue occurring on these systems. The frequency of the issue seems to depend on the hardware. I have not yet found any setting in the OS (like energy settings) that fix or reduce the issue. The issue seems to be independent of OBS settings (like audio sample rate or output format).

Obs studio recording come out bad windows 10#

I have been testing on Windows 10 20H2 with OBS 26.1.2-276 and 27.0.rc2, 64 bit, without any video source configured (issue also happens with video configured though). The issue can also be reproduced without using a test tone of course, but a continuous tone makes it easier to check the resulting file for dropouts. After stopping the recording, audio dropouts can be found in the resulting file.Īs indicated above, the frequency of this issue seems to depend on hardware and may either not occur at all or very rarely on some systems, I'm not sure what it depends on.Record desktop audio using OBS (all default settings) and wait.The length of the dropouts are not necessarily all the same length. test recording on my computer, dropouts have occurred at these time stamps: every 5 minutes, I have seen it on another computer where it happens roughly twice per hour.įor a 40 min.

When recording or streaming, audio data contains multiple random short audio dropouts.ĭistribution of the dropouts seems to be random but happen at a certain rate depending on which computer it is being run on.