> 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/solo-talk-not-working.md). # Solo Talk not working Solo Talk doesn’t engage or behave as expected Solo Talk is a director control that opens a private audio path to a guest. If Solo Talk works but private speech reaches OBS or Meshcast, check the capture and monitoring routes in [Room audio, OBS, Meshcast, and private talk](/guides/room-audio-obs-meshcast-and-private-talk.md#7-keep-private-conversations-off-air). Capturing the director's listening output or a separate host microphone can bypass the intended isolation. * Main director only: Co‑directors do not have Solo Talk controls. See `director-settings/codirector.md`. * Toggle vs 2‑way: Click Solo Talk for one‑way; hold Ctrl/Cmd for two‑way (Private 2‑Way). Both map to internal actions 5/9. * Mic source: Ensure the director’s mic is enabled in VDO.Ninja. If your mic only exists in OBS, guests won’t hear Solo Talk. * Mixer app: Some director controls are not available in the Mixer UI. * Firefox: Solo Talk support is experimental in Firefox. * Not fully compatible with Meshcast or with embedded IFRAME sources Related * `viewers-settings/director.md` * `director-settings/codirector.md` --- # 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/solo-talk-not-working.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.