Open TorNis7 opened 2 years ago
What one hears in monitoring is not what is recorded. It's a different circuit. So for step 4, do check whether your recordings have issues. The monitoring is known to be buggy. Can be lagging or else. Doesn't necessarily mean the recording is off.
Edit: are the vids linked direct obs recordings or streams ?
Monitoring doesn't use any kind of encoder, so it's unlikely to be encoding related. Also, it's unclear from your examples if you are recording the monitored output to show the issue, or recording the device directly. The sample log file presented shows a recording with only the monitor, no direct capture. Does this also occur with direct capture and not monitor?
Monitoring shouldn't really be used as a loopback in that way in the first place.
What one hears in monitoring is not what is recorded. It's a different circuit. So for step 4, do check whether your recordings have issues. The monitoring is known to be buggy. Can be lagging or else. Doesn't necessarily mean the recording is off.
It is in recordings as well. Just like in all the published content examples I did above (YouTube/VODs). Intensity of pops is basically how "lucky"/"loud" your voice gets at moment of crack. Obviously if you are not talking at that moment, noise gate will save you from that.
Those are OBS ones. Little Dragon Meiling's example is also via OBS.
Monitoring doesn't use any kind of encoder, so it's unlikely to be encoding related. Also, it's unclear from your examples if you The sample log file presented shows a recording with only the monitor
Here is my main profile log with direct captures. I did various states/troubleshooting in Discord, so have plenty of different logs, I just used this one as a blank example.
Edit: are the vids linked direct obs recordings or streams ?
Everything on my side are both streams and recordings. I locally record my streams and they have same audio result as live stream feed.
Edit: Here is another quick example from raw recording via OBS. Issue happens at 2nd second.
Operating System Info
Windows 10
Other OS
No response
OBS Studio Version
27.2.4
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/53eatQ4A4fbucurJ
OBS Studio Crash Log URL
No response
Expected Behavior
Microphone Deity VO-7U works without issues in OBS
Current Behavior
I bought expensive new on market USB mic called Deity VO-7U and believe there is some OBS hardware incompatibility after excessive troubleshooting with multiple people who have this mic. Mic works fine outside of OBS (more on that below).
When you listen to the mic via OBS launched (mic monitoring), Deity VO-7U mic starts doing cracks/pops/audio skips randomly once ~2-3 minutes or so. Meaning that during streams/recordings in OBS, that's going to happen, my speech is going to be cut in annoying way. For examples, check out this video at 2:08 or 8:13 (headphones recommended), or any other my recent VOD/YouTube video. This issue has been found by few other smaller YouTubers, example at 14:21. Meanwhile big mic review youtube channels didn't experience this in their videos due to high chance of them using different recording software or just got lucky/edited it out.
Steps to Reproduce
Anything else we should know?
I troubleshooted my mic issue like crazy and I tried everything I can in OBS and windows and on hardware level.
First of all I want to mention definitive proof that it's OBS issue. I tried raw recording mic in Reaper/Audacity, no issues there while self-monitor and recording. Same thing with just Windows self-mic monitoring. But once I open OBS and listen/record via OBS, the issue appears.
Stuff I tried: Changed USB cables, changed USB ports, used USB C instead of A port, decreased overall voltage in my outlet, physical gain knob doesn't effect this, RGB on/off doesn't affect this. Inside windows, nothing really I can do, but I still deleted drivers for device just in case. I deleted Apple AAC encoder, doesn't help. I deleted all VST plugins, nope. I tried virtually anything audio related in settings in OBS, no shot. Changing 44.1khz / 48 khz or bitrate doesn't matter.
Logically, the encoder in OBS is one at fault (that gives this corrupted Output) but this is very rare issue and I am not sure if this is even going to be solved (granted, this is new mic on the market, so maybe this issue becomes more common in the future?).
I tried talking with other Deity VO-7U mic owners who I confirmed have same issue, they obviously have no idea what to do. OBS Discord support is clueless too.