Multiple StreamDeck / MOM Deck Connection Conflicts
@Andrew_Scheps I am running into an issue with the MOM Deck package. My business partner and I have a facility with 2 studios. Each room has a StreamDeck Plus and MTRX Studio. Each room also has a Mac running DADman controlling its respective MTRX Studio. Finally, we have 2 SoundFlow Accounts - each with a MOMDeck license - with different accounts logged in on each computer.
Our facility has a pretty extensive network infrastructure with multiple VLANs and NICs on the different computers to properly manage network traffic with multiple Dante networks (primary and secondary), data, internet, EuCon, etc (thankfully I've had prior experience in corporate IT). That said, if I am understand the MOM Deck packaged correctly, it utilizes a 127.0.0.1 loopback IP to connect the StreamDeck to DADman. Due to this it seems that MOM Deck presents the StreamDeck as a DADmom in DADman using the IP of the highest prioritized NIC on the machine it is attached to. *Pleaes note that the highest prioritized NIC on our machines in both studios are in the same subnet and connected to the same VLAN.
As long as SoundFlow is only running in one room OR only one StreamDeck Plus is connected - we can connect the StreamDeck Plus to DADman with MOMDeck and it works fine. This is the case in either studio. However, if we ever try to have both in use at the same time (studio 1 StreamDeck controlling studio 1 MTRX and studio 2 StreamDeck controlling studio 2 MTRX) the units show up as not responding in DADman Device List.
I believe that this issue is because of how the MOM Deck package emulates the DADmom as a generic serial number, device name, and device ID. It seems that I am unable to update the device ID, device name or serial number in the DADman Device List to make them unique from each other. I don't believe this is an IP address issue as the local IPs of the machines are indeed unique. If this is the case, is there a way to set the ID, name, or serial that will be used by MOMDeck in SoundFlow? And if not, do you have any insight into this?
Thanks!
Andrew Scheps @Andrew_SchepsHi @Webster_Tileston ,
Thanks for the very thorough explanation. I think we need to investigate this a little more, though I think you're right about it not being an IP address issue. It very well could be the serial number/Device ID issue I know there are a few facilities using it in multiple rooms at the same time, but I'm not sure if they are all using the same Dadman to control the facility or if they are essentially on separate systems.
Let me figure out a way to make a test build and we can try it out over a zoom this week if you have time. What time zone are you in (I'm in UK time)?
Thanks,
Andrew- WWebster Tileston @Webster_Tileston8
Hi @Andrew_Scheps !
Thanks for the incredibly quick reply. I am in the US in Central Time Zone.
Just a quick clarification. We have 2 separate instances of DADman running. One on the Mac in studio 1 and one on the Mac in studio 2.
- In studio 1, DADman has 2 MTRX Studios "mounted" in the Device List via the primary Dante Network Ports.
- In studio 2, DADman has a single MTRX Studio "mounted in the Device List via Thunderbolt Option Module.
I am fairly flexible this week other than Friday afternoon 12 CST to 5 CST. Just let me know a good time for you. I appreciate the help!
Thanks!
Webster
Andrew Scheps @Andrew_SchepsAh right, but both Dadmans can see both Matrixes (matrices?) as well as both MOMs? I'm sure that's the issue. I think I can make a test scenario easily.
Email me at info@bouncefactory.net with a couple of times that work for you tomorrow and we'll sort this out!
Thanks,
Andrew- WWebster Tileston @Webster_Tileston8
No, each DADman can only see the MTRX's that it needs to - ie. Studio 1 DADman only sees the 2 MTRX Studios in that room connected via the Dante Primary Ports and Studio 2 DADman only sees the 1 MTRX Studio connected via Thunderbolt - this is true in both the Device List and the main window.
I will send an email shortly!
- Andrew Scheps @Andrew_Scheps
But each Dadman sees two MOMS? Might be something else. We'll find out
- Andrew Scheps @Andrew_Scheps
Ahh, but it would only see one because it would think they are the same unit, but from two different IPs which would be confusing for sure.
- In reply toAndrew_Scheps⬆:WWebster Tileston @Webster_Tileston8
I've never seen the device list populate with two MOMs. However, because the loopback interface on each machine is on a shared network between the 2 machines, I will see whichever one was first connected. So for example...
Studio 1 IP is 10.0.0.11 and Studio 2 IP is 10.0.0.12.
DADman and SoundFlow are running on Studio 1 with the Studio 1 StreamDeck connected properly to DADman. In the device list in DADman it shows the IP of the MOM as 10.0.0.11.
If I open DADman on Studio 2 and open the Device list it will see the MOM from Studio 1 at 10.0.0.11.
Then if I open SoundFlow on Studio 2 with the Studio 2 StreamDeck connected to the computer and MOMDeck assigned to the surface, the Studio 2 StreamDeck will not populate in the DADman Device List as a MOM - the only MOM listed will be the MOM and IP from Studio 1. The MOM connected to DADman in Studio 1 will also stop functioning and in the Device List of DADman in Studio 1, it will. show as Not Responding.
If I flip flop which room I take online first, the same happens but in the opposite room - ie. MOM from Studio 2 shows up connected in studio 2 at 10.0.0.12. MOM from studio 2 shows up in DADman in Studio 1 at 10.0.0.12. Once launching SoundFlow on Studio 1 and assigning MOMDeck to the device, the MOM in Studio 2 will stop functioning and throw a Not responding error in Studio 2 Device List.
This is what has led me to believe that DADman is getting confused by the same ID, Name, and Serial even though the IPs are in fact different.
- JJames McDonald @James_McDonald
@Andrew_Scheps We are trying to use two physically separate instances of MOMDeck to control 1 DADman Core256 in a broadcast control room suite. We have one MOMDeck instance running in the Audio control room, and another in the video control room for the purpose of using the monitoring controls for source selection and volume control in each room. As far as I can tell this is possible with the actual hardware controller, but I can't seem to make it work with MOMDeck.
I am having a similar issue to Webster, where instead of populating two MOM units in the device list (which are on the same audio network but separate assigned IPs), as I refresh the list, one of the two instances populates at random, seemingly whichever one responded first. Do you have any thoughts on this?
- Andrew Scheps @Andrew_Scheps
Hi @James_McDonald ,
The first question is are you running SoundFlow on two machines. Second question is do they need to have two different MOM profiles or is it ok if they share one?
I have a couple of ideas but definitely need to know how you're hoping it will work first.
Thanks,
Andrew- JJames McDonald @James_McDonald
Thanks @Andrew_Scheps for your quick reply! So currently I have Soundflow running on two machines, one located in the Audio control room rack, and the other in the Video Control room rack. Currently all of our DADman config is within one profile.
The goal is to just have a hardware point of control in each room, so the video director has input selection and monitor level, dim, etc for his control room, and audio engineer has the same. We have had a MOMDeck setup (SD+) in our audio control room for over a year and it has worked flawlessly, we are now trying to add control in the video room so the audio engineer doesn't have to babysit levels for video.
- Andrew Scheps @Andrew_Scheps
I think I know how we can make this work since you're on separate IP addresses. It's a little messy and we may need to beta test it. Let me put it together and I'll get in touch to test it with you over zoom if that's ok.
- JJames McDonald @James_McDonald
Awesome! Thank you a bunch! And that would be perfectly fine to test over zoom. Looking forward to it!
- Andrew Scheps @Andrew_Scheps
I'm thinking it would have to be limited instead of completely customizable like the decks you get now. Would it work if you just had a choice between 3x5 and SD+?
- JJames McDonald @James_McDonald
What we are using now is built on your standard setup of the SD+ in the Audio room, our plan is to use a second SD+ in the second room so the functionality mirrors for our ops. Here's some screenshots of how we'd like the buttons assigned. It is very simple just source active, cut, dim, and volume knob for the group master.
- In reply toWebster_Tileston8⬆:Andrew Scheps @Andrew_Scheps
I'm beta testing a version now where there are 9 additional decks possible as long as they are all on their own IP address. Should be able to publish it later today or tomorrow!
- J2James McDonald @James_McDonald3
This is great! Thank you so much for working on this!
- In reply toWebster_Tileston8⬆:Andrew Scheps @Andrew_Scheps
New version is out and should work for you! Check out the comments on the main package page and let me know if it doesn't make sense.
Let me know how it works for you!
- J2James McDonald @James_McDonald3
@Andrew_Scheps Thank you so much for working on this! It is working EXACTLY how we need it to.
- Andrew Scheps @Andrew_Scheps
Awesome!!! Now you just need 8 more computers on teh network