New Member
I’m not really sure how to explain what we are experiencing. In testing Microsoft Translator in conversation mode on a Chromebook laptop, audio goes in from the pulpit, then the app sends the translation to a browser version of Microsoft Translator. Then a mono audio cable feeds into our headset transmitter, and the translation audio is available to anyone with a headset.
When the chapel is empty it works great. We can change voices, keep the app open for well over an hour, etc. but as soon as the chapel starts to fill up the app stops working and we can’t start it again. It gives the message “Converation cannot be started, try again later”. We’ve tried using an Ethernet connection, the Lehi network, anything we can think of.
Then as soon as the chapel starts to empty out, it works again.
Any ideas? I’m stumped.
When the chapel is empty it works great. We can change voices, keep the app open for well over an hour, etc. but as soon as the chapel starts to fill up the app stops working and we can’t start it again. It gives the message “Converation cannot be started, try again later”. We’ve tried using an Ethernet connection, the Lehi network, anything we can think of.
Then as soon as the chapel starts to empty out, it works again.
Any ideas? I’m stumped.