• Devices

    CAB contains the protocols of many brands and types of devices. The ONE-Driver application acts as an interface with a device. Communication can be done via RS-232, TCP and UDP. Types of devices that are supported: Telehone hybrids (AVT, Comrex VH2, Telos, Studer, Yellowtec) IP codecs (Comrex, Prodys) ISDN codecs…

  • Network Timers

    The built-in timer network gives directors and presenters extensive timing options. Up to 64 independent adjustable timers are shown in each CAB-Controller and in the separate ONE-Timer application. The countdown clock is available in several types, such as: End time: clock counts down to the set time Deadline: clock counts…

  • Audio matrix & UNI model

    Audio matrix Equipment connected to a digital audio matrix, such as Axia, DHD or Lawo, gives great routing opportunities. A ONE-Driver application – operating as CAB-Router – controls the digital audio matrix and takes care of serving the correct return signal (N-1 or a selectable alternative source) from a studio…

  • Common setup\Event log\Events

    This document contains information about the event logging of every Audisi application. Events Shows the Event log window for live viewing of Events. The top of the Event log window displays: A mouse click on a red Error or orange Warning line will remove the line from this window (but…

  • Common setup\Event log\Setup

    Every Audisi application can write log files per hour. Since logfiles are a very useful tool to troubleshoot errors, it’s highly recommended to config this section properly. Event log file setup Path for log files To define the path for Event logfiles and events that should be logged. Cleanup old…

  • CAB-Controller

    Application for remote control of audio devices. User interface with a ‘rack’ of devices at the left side and the phone book at the right side. DEVICES By default, devices are shown as a dark blue line with two buttons. The numbers below are corresponding with the devices as shown…

  • ONE-Driver

    Application that knows how to control devices. The ONE-Driver connects to the ONE-Server via TCP/IP and connects with the device via the required protocol to exchange control commands and status info between devices and the CAB-Controller/GML-Browser/VID-Controller. The ONE-Driver speaks the languages of: audio devices like telephone hybrids, IP- and ISDN codecs…