My Balila USB Conference Phone is not Recognized

My Balila USB Conference Phone is not Recognized

If you are using the Balila USB conference phone for a remote proceeding with AutoScriptOne you must have at least one of the lapel mics turned on for your mic.  Although the base unit looks like it should have a built-in microphone, it does not.  In order for the device to work properly you must use one of the supplied lapel microphones.  

Here's a tip - clip the lapel mic to a small tripod. 


    • Related Articles

    • RS Pro Crashes using the Jabra USB Conference Phone

      Using the Jabra USB Conference phone as your input and output in RS Pro can cause the recorder to crash and not connect. The solution is to separate out the mic and speaker of the Jabra by naming them differently. With the Jabra plugged into your ...
    • How to Properly Configure Power Options for USB Devices

      When setting up your computer for reporting work using USB sound devices such as a USB microphone, USB speaker, or a USB audio interface device, we strongly urge you to change the power option for "selective suspend" in your USB settings. The reason ...
    • Why Am I Getting Double Text in My Transcript

      If you see the exact text repeated in the transcript while recording a hybrid session in ASOne, please follow these troubleshooting options. Is your microphone unmuted? When using a separate USB microphone and USB speaker in a Hybrid recording ...
    • Mixer Recommendation When the Internet Connection is Limited

      We know that internet connections when reporting in-person proceedings can be challenging and unpredictable. We suggest the following setup so that you can still use your preferred microphone mixer taking full advantage of the placement of multiple ...
    • ERROR - Unable to Get New Capture Client: 88890003

      Problem: Trying to use Reporter Studio Pro you receive the error message, "ERROR - Unable to get new capture client: 88890003." Solution 1: The best resolution is to reselect the devices from the configuration window. This is a Windows issue, and ...