For this you can use the VBcable application. Set your OBS monitor to that "virtual output" and use that "virtual input" in zoom. Works perfect. https://vb-audio.com/Cable/Question: I'm actually using this to grab the NDI output from my Avid Media Composer software, and it's working perfectly! The only issue I'm having is that while I can use the OBS VirtualCam to output the video to Zoom, I get no audio. I'm seeing that I could also run an NDI Output from OBS. Would this carry the audio then as well? I'm been having a real problem getting audio out of OBS and into Zoom. (Most likely a Zoom problem, but curious if anyone knows.)
For this you can use the VBcable application. Set your OBS monitor to that "virtual output" and use that "virtual input" in zoom. Works perfect. https://vb-audio.com/Cable/
01:02:58 PM.509: [obs-ndi] hello ! (version 4.7.1)
01:02:58 PM.509: [obs-ndi] Trying ''
01:02:58 PM.509: [obs-ndi] Trying '/usr/lib'
01:02:58 PM.509: [obs-ndi] Found NDI library at '/usr/lib/libndi.so.4'
01:02:58 PM.510: [obs-ndi] NDI runtime loaded successfully
01:02:58 PM.511: [obs-ndi] NDI library initialized successfully (NDI SDK LINUX 11:53:05 Sep 11 2019 4.0.0)
01:31:18 PM.888: Source ID 'ndi_source' not found
01:31:18 PM.888: Failed to create source 'TAS-Travis-OBS'!
Perhaps related to my a/v sync issue (previous post), my OBS logfile shows these "audio buffering" entries upon startup. My OBS audio sync offset is 0, so I'm wondering what's going on here. Thoughts?
09:18:04.414: ==== Startup complete ===============================================
09:18:04.416: All scene data cleared
09:18:04.416: ------------------------------------------------
09:18:04.465: [obs-ndi] started A/V threads for source 'PTZOptics 30x NDI (Channel 1)'
09:18:04.466: [obs-ndi] A/V thread for 'NDI™ Source' started
09:18:04.466: Switched to scene 'Scene'
09:18:04.467: ------------------------------------------------
09:18:04.467: Loaded scenes:
09:18:04.467: - scene 'Scene':
09:18:04.467: - source: 'NDI™ Source' (ndi_source)
09:18:04.467: - source: 'Text (GDI+)' (text_gdiplus_v2)
09:18:04.467: ------------------------------------------------
09:28:50.064: adding 213 milliseconds of audio buffering, total audio buffering is now 213 milliseconds (source: NDI™ Source)
09:28:50.085: adding 149 milliseconds of audio buffering, total audio buffering is now 362 milliseconds (source: NDI™ Source)
09:28:50.106: adding 128 milliseconds of audio buffering, total audio buffering is now 490 milliseconds (source: NDI™ Source)
09:28:50.126: adding 128 milliseconds of audio buffering, total audio buffering is now 618 milliseconds (source: NDI™ Source)
09:28:50.168: adding 64 milliseconds of audio buffering, total audio buffering is now 682 milliseconds (source: NDI™ Source)
09:28:50.210: adding 42 milliseconds of audio buffering, total audio buffering is now 725 milliseconds (source: NDI™ Source)
Yesterday's test: start system, no other apps running, no streaming or recording, just a camera and audio source. CPU and GPU idling at under 25%. I walk away and just leave it going. Two hours later (by the log file) OBS starts adding a bunch of these audio buffering delays. Why? Could a Windows process have engaged at that point to peg the CPU? Possible, I guess. But I've dug around and it's not related to a virus/malware scan or Windows Update.Currently chasing down an issue with buffering and latency on my system -from what I can tell it's often much more related to your PC then specifically about the particular source it references. Dodgy Sound Blaster X3 drivers have turned out to be the source of these kind of buffering increases for me. I thought it was a bug with OBS.Ninja but it was just being attributed to that source.
Also check if your CPU usage is topping out and the system isn't coping.
Update: Changing Sync setting to Source Timing did not resolve this.I'm having a/v desync issues with a PTZOptics camera that's supplying both audio and video over NDI. The desync drifts around from 0 to 800ms. I just noticed the latest OBS-NDI changelog (4.8.0 -> 4.9.0) says "The "Sync" setting now defaults to "Source Timing" - This is the best option to keep audio and video synced together." So...I've been using the Network sync setting, so will switch things to Source & hope this corrects things.
Question: What actually does the Sync setting do, and exactly what is different about 'Source Timing' vs. 'Network'? I'd like to understand what's going on and not just blindly be clicking options! Thanks.
CMake Error at CMakeLists.txt:20 (find_package): By not providing "FindLibObs.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "LibObs", but CMake did not find one. |
Before I downgrade NDI back to 4.8, did anyone ever find a solution to the Audio/Video Desync issue for the latest version?
Maybe the latest OBS RC version fixes this, or maybe changing the audio channels, anything at all honestly?
The current version is unbearable, since sometimes the Audio won't be the one Desyncing, but the Video instead and it does that over time, so you can't even put a filter delay correctly.
Hell, just changing scenes sometimes automatically starts the Desync issues. I can't even use the StreamFX shaders, because if I do, NDI has a heart-attack and can sometimes stop sending frames (imagine an overloaded encoder on the second PC).
I ended up spending hours turning everything into a Media Source to help NDI, but even sometimes a Media Source is too much and will end up Desyncing it.
The only solution I found was sending the Mic, Audio and Video each as a separate NDI filter (and the Audio set at 48 khz, I don't know why, but this delays the desync issue by quite a while) but as soon as I do that the second PC ends up using 2x the processing power (instead of 20% for a small scene, it boosts to 40% and overloads the encoder), and it makes using scenes pointless since NDI filters don't pick up on the changes of scenes automatically.
I'm vexed, and really hoping someones had solution to this. Cheers in advance.