Capture Card At 44.1 kHz instead of 48 kHz

Like the title says, I randomly noticed that my capture card is at the incorrect kHz. The thing is, I have it set to 48 everywhere on my pc and I don't see a specific option for it in OBS. I tried adding it as a custom audio device at the bottom after reading that that can help but no dice.

Can anyone offer some help with this? Here's a screen of the OBS log, OBS settings, Windows sound settings and sound panel settings.

1786762148532.png
 
44100 Hz for DirectShow capture devices is hardcoded in OBS:
Corresponding pulls on GitHub:

Similar thread (other capture device):
https://obsproject.com/forum/thread...rrect-sample-rate-from-elgato-hd60-x.191254/.

Fun fact. It seems that there is no corresponding issue filled out on the Github, so the bug slips from build to build almost unnoticed.
 
44100 Hz for DirectShow capture devices is hardcoded in OBS:
Corresponding pulls on GitHub:

Similar thread (other capture device):
https://obsproject.com/forum/thread...rrect-sample-rate-from-elgato-hd60-x.191254/.

Fun fact. It seems that there is no corresponding issue filled out on the Github, so the bug slips from build to build almost unnoticed.
I saw this when I was digging around, I was just curious if anything had changed since then. Such an odd choice. I also noticed that one of my media sources SOMETIMES pops up in the log at 44.1 instead of 48 even though if I check the properties of the audio file, it's at 48. So random.

Pardon my ignorance but I don't understand what those first two links are. Are those people just discussing the issue or is that modified code to add the option?

I guess for now I'll try muting the capture card and adding it as its own audio source to see if that changes anything. I don't have problems with desyncing or anything like that, although once in a blue moon the capture card audio will hitch for a split-second. I just obviously want everything to be set up as perfectly as possible.
 
The links is about proposed changes to the OBS code that potentially could fix the problem. So, at least, some developers are aware of the problem.
 
The links is about proposed changes to the OBS code that potentially could fix the problem. So, at least, some developers are aware of the problem.
Okay, thought so. I saw that Warchamp added it to the 33.0 tracker. Hopefully that means that it has an actual chance of being implemented, even though that's probably quite far way.

I assume the solution of adding it as its own audio source is the only solution for the time being?
 
Back
Top