![]() That’s it! The value for the delay will depend on your exact setup. choose VB Cable output as the external app’s audio input source.pick the VB Cable as OBS Monitoring Device.delay the audio on the microphone (Advanced Audio Properties).microphone goes into OBS directly as input source.To keep it simple for the descriptions, I’m assuming we have a microphone as input, and headphones as output. Grab them, close OBS and install them, then restart your system before proceeding with the following steps. Audio Router – an optional utility that lets us route sources to destinationsīoth utilities are free.VB Cable – a virtual routable audio source/destination.Here’s an option that works, although I always forget how to route it properly (it’s for Windows only). What we need is a workaround until this functionality will be built-in to OBS (I’m sure it will at some point). There’s currently no built-in way to choose the OBS Audio in our external application, even though OBS itself has the ability to delay the audio and make it appear in sync. To make it look professional we need to add an audio delay Video processing takes a small amount of time, and as a result our audio arrives too early when used directly. This lets us use the OBS video output with external apps that do the streaming for us, like Zoom, Skype and Discord to name a few. Since it is recommended to use a hardware out over the Virtual Cables (which means I can't bring it into OBS without running it through an external DAC just to be brought back in), what would be the recommended way to get audio out of VoiceMeeter and into OBS (allowing me to have different channels for different things, like one for my mic, one for the system, one for external capture, and one for Discord audio for example)? I do use the built in Virtual Output ports for VoiceMeeter (which work great for recording and what not would be nice to see more of those in the Potato version) for some of the items to OBS, but it is very limiting with only having 3 VAIO.Since version 26 of OBS we have that wonderful built-in Virtual Camera option. I know OBS has a plug in to interface with VoiceMeeter directly, but the issue is when I try and capture the input side it is all pre-VoiceMeeter. I also noticed all of the outputs were choppy when I reviewed my Twitch recording (this was recorded by Twitch as I streamed). I did test with Virtual Cable C (which appears to be set at 48000 Hz, I have not tested 44100 Hz yet with it) and it is also being choppy with Audacity. The Virtual Outputs from VoiceMeeter Potato work perfectly fine. As I mentioned, this is only an issue though the Virtual Cables. Operating System: WIN 10 64Bits Build: 19043Īny thoughts on what the issue could be? My computer has been restarted and is fully up to date. Driver Checker reports no issues (see below).ĬHECKING VB-Audio Virtual Cable : Not InstalledĬHECKING VB-Audio Cable A (version 01000305)ĬHECKING VB-Audio Cable B (version 01000305)ĬHECKING VB-Audio Cable C (version 02010502)ĬHECKING VB-Audio Cable D (version 02010502)ĬHECKING VB-Audio MT128 Virtual I/O : Not InstalledĬHECKING VB-Audio Hi-Fi Cable : Not InstalledĬHECKING VB-Audio VoiceMeeter VAIO (version 02010502)ĬHECKING VB-Audio VoiceMeeter AUX VAIO (version 02010502)ĬHECKING VB-Audio VoiceMeeter VAIO3 (version 02010502) I have uninstalled, restarted, installed the Virtual Cables, and restarted. Doing audio recording on Audacity any audio that is sent out VAIO3 is good, but any audio going out through the Virtual Cables is choppy. My MIC Audio is routed through VoiceMeeter Potato and out to several outputs. ![]() I am using VoiceMeeter Potato and have Virtual Cable A, B, C, and D installed.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |