Trouble Shooting

If the QR Code, Language, Audio Select, or Transcription mode options are not present, then an issue has occurred in loading. If this is the case, please try one of the following options:

• Log out and log back in

• Try clearing the cookies and the cache of the website

• Try loading the login page on a different device

If none of those options work, please make a report by following these instructions.

If the stream stops during a service, please follow the following set of trouble shooting steps.

• Click the 'start streaming' button again

• Refresh the page and click 'start streaming'

• Log out and log back in

• Try clearing the cookies and the cache of the website

• Try loading the login page on a different device

Breeze Translate and the underlying services we use are sometimes not available through school WiFi networks.

To fix this issue, you can ask your network administrator to allow access (whitelist) the following domains:

• breeze-translate.com

• deepgram.com

Alternatively, you can use a mobile device as a hotspot. Breeze requires about 100MB per hour for the transcription (receiving of translations is much much lower).

The audio output — speaking the translation — is only in the beta stage of development. We have made the feature available for the cases where it works, but we cannot guarantee that it will work consistently across all devices and languages. Our approach is as always to use economical technologies to make a useful and affordable service, and as such we are not at this stage implementing the state of the art speech output, in favour of a service that more churches will be able to afford to use.

Further Details

Spoken output uses on-device speech-to-text software that is supplied with the device. As such, spoken output will only work where the relevant software is on the device.

Unfortunately, it is a known issue that languages such as Farsi are not well supported by on-device text to speech.

If you have any problems at all using Breeze Translate, please contact us on info@breezetranslate.com and we'd be really happy to help. Below is some useful information on how to make the most helpful bug report:

Making a Helpful Bug Report

Please include as much of the following information as possible when reporting an issue:

• Your church name

• The date and time of the issue occurring

• The Browser and operating system (eg. Windows, Mac etc) you are using

• Any steps to replicate the problem

• If possible, please include a copy of the console log (see instructions below)

Getting the Console Log

It's helpful to us to see the logs from the web browser's console on your device to diagnose the issues you're facing. Please copy and paste the logs that you'll find after following the instructions below.

• Chrome:

  • Press F12 or Ctrl+Shift+J (or Cmd+Opt+J on macOS) to open the Developer Tools.

  • Click on the "Console" tab within the Developer Tools panel.

• Firefox:

  • Press Ctrl+Shift+J (or Cmd+Opt+J on macOS) to open the Web Developer Tools.

  • Click on the "Console" tab within the Web Developer Tools panel.

• Safari:

  • Enable the "Develop" menu in Safari by going to Safari > Preferences > Advanced and checking "Show Develop menu in menu bar".

  • Then, go to Develop > Show Web Console.