Troubleshoot the OBS plugin बीटा

अंतिम अपडेट 14 अक्तूबर 2026 किसके लिए: Tech volunteers and directors troubleshooting SermonWave in OBS

यह लेख अभी आपकी भाषा में उपलब्ध नहीं है, इसलिए इसे अंग्रेज़ी में दिखाया गया है।

इस पेज पर

Most problems show up right in the SermonWave dock: the connection line at the top, red warnings below it, and messages in each category. This article explains them and lists common messages with their fix.

Who it's for#

Anyone running the SermonWave OBS plugin when something isn't working.

Before you start#

  • Open the dock: Docks → SermonWave.
  • Note your plugin version: open Diagnostics & advanced in the dock; the info line shows the hub, the device number and the plugin version. (The first release is labelled 1.2.7r; the "r" is only on that release.)

Read the status line#

The top of the dock always shows your organization and device name and one connection line, for example "● Connected · 42 ms".

ConnectionMeaning
ConnectedAll good.
Connected (reconnecting event stream…)Briefly lost the live channel; it reconnects by itself.
Connecting…Starting up.
Server unreachable — retryingNo internet, or a firewall blocks SermonWave. Audio is buffered meanwhile.
In use by another client (e.g. a browser tab)The device is open as a Web device somewhere. Click Take over this device.
Taken over by another clientSomeone took the device from another place. Take it back with Take over this device if that was a mistake.
Unpaired — pair again / Not authorisedThe pairing was removed. Pair again.

The session state is in the control bar: ● Idle, ● Armed — waiting for speech or ● Translating.

Health warnings#

The plugin watches its connection and your computer and shows a red warning at the top of the dock when something is wrong for more than a few seconds:

  • Audio link down — buffering (N s) — audio isn't reaching SermonWave. Nothing is lost: the plugin keeps up to 5 minutes of audio and sends it when the link is back, and translations catch up. Check the internet connection.
  • Network congested — translation delayed N s — the audio link to SermonWave is behind. It buffers up to 5 minutes of audio and catches up, so translations arrive late but nothing is lost. Reduce other uploads (translated streams, cloud backups) or the stream bitrate.
  • Network congested — the stream is dropping frames — this is about OBS's own stream: your main stream is struggling. Lower the video bitrate, pick a lighter Video quality for translated streams, or remove one.
  • Computer overloaded — OBS is skipping frames — the computer can't keep up with encoding or rendering. Use a hardware encoder, lower the resolution or frame rate, or close other programs.
  • Pick the OBS source that carries the pastor's microphone. / The selected source is not in this scene collection — nothing is being sent. — no pastor microphone is selected, or it isn't in this scene collection. Choose one under Audio input.
  • No translated recording — add a language under Translated streams / … recording is off — tick "Record a … copy" under Recording — shown while you record without a translated recording copy. Add a language under Translated streams, or turn its copy on with its REC button. See Record a translated copy in OBS.

When the network is poor, the plugin backs off and retries without flooding your connection. After a connection drop, it reconnects on a fresh connection within seconds.

Under Diagnostics & advanced, a line like "Audio link: Opus · 26 kbps · last send 0.4 s ago · 0 reconnects" shows the audio connection in detail.

SermonWave dock top area with the connection line and a red "Network congested" warning

Network stability#

  • Use wired Ethernet rather than Wi-Fi for the streaming computer.
  • Check your upload speed. Run a speed test such as speedtest.net or fast.com (click Show more info to see the upload) on the streaming computer while nothing else is uploading. If you like, enter the result under Translated streams → Your upload speed: the upload estimate in the control bar then shows how much of it you use. It is only shown, never a limit.
  • Recommended main stream settings for YouTube (Settings → Output): 1080p30 at 4.5–6 Mbps or 720p30 at 2.5–4 Mbps, Rate Control CBR, Keyframe Interval 2 s.
  • Translated streams add upload. Each one is a second video upload; a lighter Video quality saves upload. See Stream a translated version from OBS.

Logs and diagnostics#

OBS log file. Everything the plugin does is written to the normal OBS log, on lines starting with [sermonwave-obs].

  1. In OBS, open Help → Log Files.
  2. Choose Upload Current Log File and copy the link, or Show Log Files to find the file.
  3. Send it to support with the time the problem happened.

Automatic diagnostics. When the plugin detects a problem (for example a long audio backlog, repeated reconnects, or translations arriving without a voice), it sends a diagnostics report to SermonWave once the connection allows. Support can also ask your OBS for a fresh report while it is connected, so you don't have to collect anything by hand. To send one yourself, open Diagnostics & advanced and click Send diagnostics. Reports never include stream keys, passwords or sign-in tokens.

If OBS closed unexpectedly. The next time OBS starts, the plugin notices that the last session did not end normally and sends a short report with its last log lines (on a Mac, also a summary of the crash report macOS wrote). You don't need to do anything, but telling support the time it happened helps.

Dashboard. The device's page in the Dashboard shows its status, and for OBS devices each translated output (live, bitrate, dropped frames, recording file), read-only. See Live monitoring.

Common messages#

Message (exactly as shown)CauseFix
The code expired. Get a new code.The pairing code is older than 10 minutes.Click Get a new code.
Pairing was denied in the dashboard.An admin clicked Deny.Get a new code and ask the admin to confirm.
Too many pairing attempts from this network. Retrying in a minute…Many codes requested from your network.Wait; it retries by itself.
This server does not support OBS pairing yet.The Server under Diagnostics & advanced isn't the normal SermonWave server.Choose SermonWave (default) and Apply.
Could not reach the server (…). Retrying…No connection to SermonWave.Check internet and firewall.
The selected source is not in this scene collection — nothing is being sent.The pastor mic source doesn't exist in this scene collection.Pick a source under Audio input → Pastor microphone.
The source is muted — sending silence.The mic source is muted in OBS.Unmute it in the Audio Mixer.
No languages assigned to this device — ask a SermonWave admin.No languages assigned in the Dashboard.An admin assigns languages to the device.
Could not save the languages: …Saving the device languages failed.Check the connection and try again.
The device no longer translates into this language, so no captions will arrive. Choose another language.A language OBS uses was removed from the device.Choose another, or add it back under Languages.
Error: paste your stream keyA translated stream has no key.Paste the key for that language.
Error: the server must start with rtmp:// or rtmps://Invalid custom server.Fix the Server.
Error: the server refused the stream keyWrong or expired key.Copy the key again from the platform.
Error: could not connect to the serverThe streaming server can't be reached.Check the address and your connection.
Error: this is the main stream's own server and stream key — …Same key as the main stream.Use a separate stream key per language. See translated streams.
Error: start the main stream / recording firstThe translated output needs the main output.Start your main stream or recording.
Error: the main recording has no shareable encoder (lossless or custom output) — use a normal recording formatLossless or custom recording output.Change the recording quality/format in OBS.
Error: no AAC audio encoder availableOBS has no AAC encoder.Reinstall OBS Studio from obsproject.com.
Re-sync failed (the disk is full). …No space for the synced file.Free disk space. The live-mixed file is kept.
… sentence(s) later than the delay (up to … s): raise the sync delayTranslation took longer than the sync delay.Raise Sync delay. See sync.
YouTube: live streaming is not enabled on this channel (…)Channel not enabled for live.YouTube Studio → Go live; wait up to 24 h.
YouTube: the sign-in was revoked or expired — sign in againYouTube access ended.Click Sign in with YouTube.
That YouTube stream key was deleted — pick anotherKey removed in YouTube Studio.Pick another key.

For more YouTube messages, see Stream to YouTube automatically.

A level or language changed on its own#

In the current plugin, scrolling the dock with a two-finger trackpad swipe (common on a Mac) or a mouse wheel while the pointer is over a slider (for example Original audio or Under translation), a number box (for example Sync delay) or a drop-down list can change its value without any click.

  • Scroll the dock with the pointer over a heading, a label or empty space, or drag the dock's scroll bar.
  • If a level, delay or language looks different from what you set, check it before the service and set it again. Nothing is broken.
  • Clicking, dragging and the keyboard work as normal.

FAQ#

Translations stopped during the service. Is the audio lost?#

Usually not. If the link drops, the plugin buffers up to 5 minutes of audio and sends it when the connection is back; translations catch up a little later.

Should I restart OBS?#

Only as a last step. Most problems recover by themselves once the connection is back. If you restart, note the time first so support can find it in the log.