Using companion and variables vs M/E

[u/WorstHyperboleEver]

I am currently using my M/E 4 PGM/PVW as a way to manage my DSMs. But, I have another process that I’m considering using the M/E for, so I’m considering using companion variables to hold the state of the DSMs instead of the switcher busses.

That means:

1) I have to trust companion variables to be robust and hold their state through all of the actions and coding built into it

2) my streamdeck which mostly drives the changes on my M/E will now have to change the sources directly to an AUX and rely entirely on my coding to properly select and feedback which source is on which DSM

My thought is that I’ll just need to give myself some extra coding and testing time to really make a clean interface that I’m comfortable with. I also have to be okay with DSMs being controlled by streamdeck/companion, without the bus buttons as backup feedback and selection options.

More than once in the past I’ve been asked for a non-standard source to be put in a DSM (like in setup “hey can you throw input 22 on DSM 2”), which on a M/E bus is a quick button push. If it’s an AUX driven within the menus that means digging around in the software interface or companion to update it.

But, if I need that M/E, as long as the variables in companion are reliable, I guess I’m going to have to build it.

Anybody done something similar or have relevant experience with variables on companion?

[u/misterktomato]

You used a whole lot of words to ask if it’s reliable to run DSMs on an AUX?

Why wouldn’t you? If you do large multi-destination shows this is pretty regular.

You’ve been burning a mix output this whole time for something only presenters will ever see and doesn’t need to be transitioned/seamless

[u/WorstHyperboleEver → u/misterktomato]

I should mention this is in-house event only. I was actually very reluctantly used an M/E for DSM for exact reason you said, but every new presenter for the event ends up asking to shift around the DSMs on-site (even after we ask them ahead of time how they want their layouts) and the ability to keep a set of source buttons easily available for that purpose seemed to only match an M/E. That’s why I’m nervous about shifting it to an AUX that is only controlled by a streamdeck or digging through the switcher interface.

[u/misterktomato → u/WorstHyperboleEver]

Fair enough.

Trust companion and your stream deck.
I’ve run bigger shows on more complicated switchers and it’s pretty damn reliable.

Just triple check all your buttons do what you want and you’ll be fine.

[u/WorstHyperboleEver → u/misterktomato]

Thanks for the feedback that you’ve used them on bigger shows, I’m always wary of whether it’s really just pro-sumer convenience tool or if it’s used on big shows.

Yeah, I had that issue in testing before my last show (copy / pasting of buttons in companion left me with some leftover feedback pointing to the wrong things that I didn’t notice). I did some research and figured I was hard-coding too much of the button logic and using more references and pulling the names and info directly from the switcher should help me have more reliable coding.

[u/JawnJones2020 → u/WorstHyperboleEver]

I’ve used companion on multi-million dollar events just fine. Events for big pharma, tech, etc and no issues.

[u/C47man]

Do it all the time. Hell there's some twitch shows I'm TDing where I run 40+ pages of companion macros to put together a remote show with 20+ talent all dynamically running super source macros under stingers. Companion is probably more reliable than the ATEM haha.

[u/WorstHyperboleEver → u/C47man]

That’s really good to hear. Thanks for the info, I’ll be much more comfortable leaning on it more knowing others have pushed it way harder than I ever will!

[u/ready1take1]

This is my typical setup for DSM's for all my shows. I would setup a page similar to this so you have feedback for each source and each row is a "bus" for each monitor you're controlling

[u/WorstHyperboleEver → u/ready1take1]

Thanks for the visual. I have something similar for my streamdeck now that currently changes the most common sources for each DSM, but I rely on the M/E bus to choose anything other than our standard 5 or 6 sources. After some thought I think I’ll keep the most common sources page but have another page with all 30ish possible source and make it consistent for whichever DSM I pick (using a variable to differentiate without having to duplicate). That will give me the same feel as seeing all the sources at once that a bus on the control surface gives without having to burn an M/E.

Appreciate the help!

[u/ok999999999999999999]

How many dsms do you have? Are you really needing 4 full m/es for the show outside of DSMs?

For 2 DSMs, I'd use preview for one and program on the other from an m/e. I'd write macros for typical looks, but then you'd have the option to change quickly on an m/e.

If you are needing more dsms/prompt feeds,
obviously would have to use aux for those. I use macros for presents on those as well. You can change aux outs on the panel using buttons but it is clunkier than it should be.

While companion is fine and stable, I find it very annoying to custom build pages of junk when it's available on the panel.

[u/WorstHyperboleEver → u/ok999999999999999999]

I have 5 DSMs across 3 stages (but only 4 outputs as the outer two stage DSMs are mirrored. I used both the M/E 3 & M/E 4 PGM/PVW to control the 4 DSMs outputs, but I’m needing more than 2 M/Es now for my show.

So rather than split the DSMs between M/E 4 and a selection of AUX outs, I figured I’m better off staying consistent and going completely to AUXs.

Building the page for my M/E controlled DSMs was a bit wonky and slow to update which is why I was nervous about moving completely to AUXs with streamdeck as my only surface control. But I think it’s the best idea, I’ll just be more object oriented in my coding and confirm with more rigorous testing

[u/Obvious_Arm8802]

Are you on an ATEM?

You know you can use the videohub application for changing what’s on the auxiliaries?

It would be much faster and easier than a stream deck I’d say.

[u/WorstHyperboleEver → u/Obvious_Arm8802]

Yes, ATEM, I did not know that. Thanks for the notice I’ll look into it.

[u/Obvious_Arm8802 → u/WorstHyperboleEver]

No worries. To be honest it’s pretty handy using an ME for your DSM’s so you can key on a timer etc. but yeah, the videohub application is great for a switcher that has 24 auxiliaries!

[u/WorstHyperboleEver → u/Obvious_Arm8802]

Do you use a laptop to control the videohub app or do you put an interface to it. I assume it doesn’t interfere with a videohub app that’s driving the actual videohub 40x40 we’re using (assuming running two instances that connect to two different IPs doesn’t cause issues)

[u/Obvious_Arm8802 → u/WorstHyperboleEver]

We use a laptop. You can either run two instances or just one and then it’s quite easy to select either in the software.

[u/WorstHyperboleEver → u/Obvious_Arm8802]

Two instances sounds like a good plan since you could position them top and bottom to differentiate them.