We're working hard to make Breeze as easy and reliable as possible. Below are some trouble shooting and bug reporting tips that you may find useful if things aren't working perfectly. Please don't hesitate to get in touch if you need anything whatsoever!
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
We have heard of other churches having an issue where a device, often being used by another piece of software on the computer like OBS, couldn't be accessed by Breeze. At times, Breeze defaults to the device microphone, rather than the selected audio device.
Here are some things to look at:
Trying to select the relevant device while not running OBS — does this work?
Try another site like this one to test if the device can be accessed by the browser
What operating system are you using? Macs are usually friendlier at sharing, but not always.
If using Windows, there are sometimes issues with sharing ASIO devices. You may need to download a 3rd party multi-tenant ASIO driver.
If the laptop has an additional microphone input, you could try to connect to that.
We would love your feedback on how you have got on in solving this in your context, so please contact us if you have managed to make progress on this so we can help other churches like yours.
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.
iOS (iPhones and iPads) support around 40 languages, but the voices accessible to web apps like Breeze are robotic.
Android (Samsung, Google Pixel, Huawei and more) support over 100 languages, and allow access to high quality voices.
Our recommendation where Audio output us helpful would be to use an Android device.
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:
We have a bug report button in the side bar. This will share some data about your system, as well as logs from the app and you have the opportunity to add your own message about what has happened.