Search
  • Taylor Glad

Mic Status for Bitfocus Companion & TouchOSC

Updated: Jul 26

This project includes a Bitfocus Companion configuration file and Hexler TouchOSC file that can work separately or together for a quick and push-button style communication system for wireless microphones.


Mic Status 32 v1.1


https://drive.google.com/drive/folders/1v9-3qaZx8_p3f7W5oPzX9oakQ7Q7E-ZS?usp=sharing






In the cheapest setup, this could be used with Companion’s emulators on computers without needing to spend money on any apps or Stream Deck controllers. But you can easily use Stream Deck XLs, or TouchOSC on a computer, tablet, or phone. (This Companion config file will not work with 15 key Stream Decks.)


Tested on Companion 2.2.3 and TouchOSC 1.1.4.143


Because TouchOSC only supports 5 OSC connections, the system is built to support up to 6 devices, each sending OSC commands directly to all other devices. This eliminates the need for a central hub/device. It also means that opening a device late will not be able to “catch up” on messages previously sent. For that reason, static IP addresses or reserved DHCP are also recommended.



Customizing

It’s recommended to make customized changes to one configuration file, and then to share that with other devices to make sure customized text fields all match. (And making sure Companion and TouchOSC have identical or similar text fields)

Because this sort of project is tedious in Companion, there are also pages of empty buttons where actions can be added for any time certain mics have any error or fix report, or any mic has any certain error or fix report. See pages 95-97 in the Companion GUI.

There is also a “Settings” page where currently the only setting is to automatically return to the Mic Status page or not after selecting a mic report.

Unused channels can be turned black with the “Mic Not Used” option on that mic’s page.


Companion

There are variables for each of the mic/actor names, and error/fix variables for customizing the red and orange button labels for reporting errors/fixes. These are set per device.


TouchOSC

Feel free to change names on any of the labels not locked in the default template.

Unused mic channels can be hidden from view in the document tree.



Connections

Companion

The configuration has 4 existing connections for other Companion devices and 4 existing connections for TouchOSC. IP addresses are set to 1.1.1.1 by default, and most of the connections are disabled. Edit the connections to have the correct IP addresses, and enable the connections. (The devices won’t get the necessary OSC messages if a Companion device’s IP is set in a Connection labeled for TouchOSC, etc.)

A logging device can be any device (including a device also running TouchOSC or Companion on different ports) with an app like OSCulator or Protokol from Hexler.net. Set the IP and port for this device in the “Log” connection in Companion.

A user text variable can also be customized, which is included on logs sent to the logging device.

Logs include a timestamp, user, mic, and status report.


TouchOSC

Set the IP address of any device in any of the 5 OSC slots. For communicating with Companion (using the matching configuration file), the send port should be set to 12321.

A logging device can be any device (including a device also running TouchOSC or Companion on different ports) with an app like OSCulator or Protokol from Hexler.net. To make sure the log doesn’t get cluttered with extra OSC messages from TouchOSC, select which OSC connection slot is patched to the logging device under “Log Connection” under the “Log” tab.

The “Log User” setting on the “Log” tab will include that tag on log entries on logging device, as well as the local log.These fields are also customizable.

The local log page is only able to keep the 15 most recent logs sent or received. All outside messages will be simply logged as an “OSC” user.

Logs include a timestamp, user, mic, and status report.


0 views0 comments