Skip to content

Troubleshooting

No audio, lost input, listeners who can’t hear and other fixes.

13 articles

Check the cable, the mixer send and that the right input is chosen on Live, then run Test audio.

  1. On Live, make sure Live input shows your audio interface, not the Mac’s built-in microphone.
  2. Don’t see it? Reconnect the interface and use Refresh audio inputs.
  3. Press Test audio and have someone speak at the pulpit. If it says No sound, check the fader and the send on the board.
  4. Still nothing? Check that Dubr is allowed in System Settings → Privacy & Security → Microphone.

The service keeps running and Dubr tries to reopen the input by itself. If the red banner asks, choose the input again.

  1. Plug the audio interface back in. Dubr usually reopens it by itself.
  2. If the banner says to choose the input, pick it in the banner and choose Continue with this input.
  • If no input returns for 10 minutes, interpretation stops. The last 2 minutes count down on the banner.

First check that Dubr is live and the status shows attendee delivery active. Then check the attendee’s phone.

  1. On the Mac, check the status reads Interpretation live and the badge Attendee delivery active.
  2. Check the language tab: is anyone listening, and is the service in Sermon? Worship is captions only, with no voice.
  3. On the attendee’s phone: tap Tap to Enable Audio or Resume audio if it shows, make sure the translation isn’t muted, and turn up the phone’s volume.
  4. Ask them to choose their language again, or reload the page. They stay in the same service and language.
  • If the banner says Audio interpretation paused — captions continue, the voice is retrying; captions keep going.
  • A private test link works only for that test. Attendees should use your church QR.
For attendees

The page shows when the next service starts and connects by itself once the service goes live.

  • Not live yet: the service hasn’t started. Keep the page open, or come back a few minutes before the service.
  • No service right now: interpretation runs during services.
  • If the connection fails, Dubr keeps trying by itself while the page is open. Check the phone’s internet connection.
  • Opened an old test link? Scan your church’s QR instead.

Check the service’s spoken language and listener language, and the church language in Settings → Languages & accents.

  • The Service check’s Speech recognition step warns when it hears a different language than the service is set to.
  • A service’s languages are set when you create it. If they are wrong, create a new service with the right Spoken language and Listener language.
  • Attendees choose their own language on their phone. Make sure the language they need is turned on under Listener languages.

When the voice falls behind the speaker, it speaks a little faster until it catches up.

  • The delivery chip on Live shows the pace. Keeping up is normal; a catching-up chip means the voice is speeding up a little.
  • A clear, steady input helps the most: a “Dubr” mix with no instruments and no room noise.
  • After the service, the report shows Typical delay and how often the voice sped up.

Add them to the service’s Names and special words, and give Dubr the sermon notes and lyrics before the service.

  1. Open the service → Prepare → Names and special words and add the name, place or church word. Use Say it as (optional) for how it is pronounced.
  2. Add the sermon notes and Scripture under Sermon, and today’s lyrics under Worship songs.
  3. Choose Save preparation before the service starts.
  • Words like your church’s name are never translated.
  • Live AI interpretation can still miss a word now and then. Tell us about a pattern from Settings → Support.

Start needs a set-up Mac, a ready service, an approved voice and a connected input, with the right languages.

  • Settings → This Mac must show Ready to go live. If it shows Not set up, an owner or administrator signs in on this Mac.
  • Choose a service that is ready. A service that has ended can’t start again.
  • Choose a Speaker voice that is ready, and an input that is connected.
  • The source and listener languages must be different.
  • On a free trial, only private tests can start. When trial or test time is used up, the owner chooses a plan.
  • Only owners, administrators and live operators can start services.

Your account is signed in but isn’t on a church team yet.

  1. Ask a church owner or administrator to invite this exact email address.
  2. Accept the invitation from the email.
  3. Back in Dubr, choose Check again, or Use another account if you signed in with a different email.

Your sign-in stays saved. Dubr reconnects by itself when the internet returns; you can also choose Reconnect now.

  • Ending a service and Service checks need the internet.
  • If a live connection can’t recover, Dubr asks you to check the internet connection, then press Start.

If you see “The voice was not created”, choose Try again. Check the recordings first.

  • Use clear speech from that speaker only, ideally 1½ to 2 minutes.
  • Interpretation must be paused to create a voice.
  • A new voice shows Voice being checked until it is ready.

Still stuck?

Ask AI answers from these articles in seconds. A person on the Dubr team reads every ticket and email.

Tickets open in your church’s web workspace. In the Mac app, use Settings → Support.