Bitfocus Companion Module

dLive dLive Feature Suggestions
1

Companion is such a great tool to control many systems from one place. I would love to see a full featured companion module for DLIVE.
There is one but it’s missing quite a bit of functionality.

Things that would be especially useful for me:

  • Channel to mix assignments
  • Feedback of states and information
2

I have not used companion, but I just became aware of its existence in the past little while. Since it is open source, you could even work on it yourself if you have the skills.

3

I use the dLive companion module on a daily basis. In its current state it is not “compatible” with companion version 3 (it seems to be working no problem, though) and it is missing all features implemented into Midi of dLive fw2. (all UltraFX dependent things, Scene Go \ Next \ Previous). And Midi is the only way for companion to connect to dLive. If A&H should open Midi (and in addition OSC) to way more functions is discussed in many feature request posts and high on my list for usability improvements for sure!

As development for the current dLive companion module was stopped a while ago, I found the developer who originally started that module and passed it on later. I had dealt with him, that I am going to pay him for bringing the module to the features currently possible and being compatible with companion 3. As this project is not on top of his list, it’s unclear to me, when this is going to happen, though.

4

I would love to see some more development on the DLive Companion module as well.

I’ll just add that while Companion automatically flags the current DLive Companion module as “not compatible” with Companion V3, in reality it works just fine. The fact that the module is only “one way” and doesn’t provide any feedback actually ensures that the current module continues to work with Companion Version 3 even though it was created when Companion was on Version 2.

At my church, we have implemented a Streamdeck XL with Companion running on a Raspberry Pi. This effectively is a stand alone system that stays powered on (ie it doesn’t require another computer to be turned on for it to start functioning). Keep in mind that we run a “surfaceless” setup with three IP8s and a computer running Director at FOH. By having the Streamdeck, users can make changes to the system without having to power on the FOH computer and/or start the Director software.

For implementation with the DLive, we primarily use it to recall scenes (but we also have some channel mutes and mute group functionality set up too). I have created scenes to do a wide variety of tasks including:

  • Loading a “starter” scene so various groups using the facility can quickly get the system into a state designed for their needs. Most groups can use the DLive without having to start the Director software this way. We have another IP8 on stage that is “connected” to the Mixrack (so it doesn’t require a Surface to work) and set up to control FOH audio channels and the scene loads a custom layout on that IP8 with the source/inputs that group needs.
  • Change the layouts on the three IP8s at FOH between FOH use and mixing our Stream Broadcast. Our regular FOH channels go out post fader to various auxes (which act as groups) dedicated to our Broadcast mix, and then out a dedicated Broadcast Matrix. We do not have a dedicated engineer for our broadcast mix which is why we use “post fader” audio from our regular FOH sources. The dedicated Broadcast layout gives access to the various “aux” sends for the broadcast auxes thereby allowing the FOH engineer a way to spot check and adjust the broadcast mix easily.
  • Change the global “key” for vocal tuning and harmonizer RackUltra plugins (one button/ scene has been created for every possible key). The Streamdeck XL is a perfect size for this because I can place my key buttons just like a piano/keyboard so it is very intuitive to use. If I had a smaller Streamdeck, the layout wouldn’t look like a set of piano keys.
  • Buttons that load various “musician scenes” that are set to change the channel name, processing, Dyn8, and aux sends depending on who is playing/singing since we rotate various musicians/singers week to week.
  • Buttons that load a scene for transitions in the service (ie pre-service, announcements, 1st song, 2nd song, pulpit use, preaching, communion, etc, etc, etc)

We also use the Reaper Companion module to give us quick control of the transport controls to make starting and stopping recording easy. We use feedback options to provide a visual sign that the system is recording as well. We also have controls for VSC use too.

Obviously if we had a physical Surface most of this functionality could be assigned to user keys. But having the customization with names, colors, icons, layouts/pages, feedback options, etc makes the system much nicer to use than a Surface with board tape as button labels IMHO.

1 Like
5

Having labels on your keys is a huge advantage over native Soft Keys, in my opinion. And running it off a Pi is a great idea!

Y’all are giving me the itch to get a Streamdeck :winking_face_with_tongue:

6

The SQ companion module is pretty well implemented. Would be nice if someone developed the dLive module to at least match that one. I’m sure a lot of folks would chip in for some crowd funding of a developer.

1 Like
7

Has anyone tried the generic midi module with companion and then using the A&H Midi driver for windows? I tried but have not had success. Using the Dlive module but really miss the cue list Go control.

8

As I have written above, the original developer is willing to bring the module en par with what is possible right now. But not sure, when this will happen.
If you find someone else willing to do this in a quicker time frame, I will jump that boat with what I planned to contribute to the community anyways. I have the modules “source” passed over from the last developer. So who ever wants that as a starter, contact me…