> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/common-errors-and-known-issues/audio-is-delayed-in-obs.md). # Audio is delayed in OBS Troubleshooting guide for Audio is delayed in OBS in VDO.Ninja and OBS with likely causes and practical fixes. ### OBS specific issues Might be caused by a Browser-source related bug in OBS; this is normally the cause Fully restart OBS and see if that clears the issue.\ \ Start OBS in administrator mode, if on Windows, to ensure it's not being throttled.\ \ Some users have had better luck fully uninstalling OBS and then re-installing it.\ \ If that fails, you can try to bring in audio via instead. [`&novideo`](/advanced-settings/video-parameters/and-novideo.md) can be used to ingest just the audio. Route the audio to a virtual audio device and then bring that into OBS as an audio device. Should be in sync this way. ### Other possible options VDO.Ninja uses 48000-hz sample rate for audio; using this sample rate whenever possible can help keep things in sync. Try to avoid overloading your CPU or using too many browser source elements in OBS; OBS Browser Source can get overwhelmed. VMix could be an alternative to OBS if problems persist; Vmix supports VDO.Ninja also. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.vdo.ninja/common-errors-and-known-issues/audio-is-delayed-in-obs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.