S6 monitor section disconnects from DADman

[Rich Breen]

Hi all - I have an intermittent problem that's driving me slightly batty. Upon booting the system (S6, DADman, WSControl, Pro Tools), the S6's monitor section sometimes doesn't connect to DADman; everything else in the master section works (softkeys, all displays) but the monitor control pots don't show any levels and talkback button doesn't work. Sometimes, the monitor pot will function if I focus DADman, but the monitor displays still don't show level and talkback doesn't work. This system has been this way for as long as I can remember, and most of the time works fine, but sometimes not.

I can get things back to normal through some 10-15 minute dance of rebooting everything, quitting and restarting WSControl, etc, but none of that *always* works, and I haven't found a reliable way to always get control back. Again, *everything* else works fine - fader controls, rest of master module, all switches and pots - just the monitor section fails.

Aside from being nerve-racking, this is problematic as we do a lot of remote work with this system with the client in the control room reviewing edits/mixes and engineers running the system remotely (via Anydesk) - if the monitor section isn't operating correctly the client's talkback doesn't work and the client is not tech savvy so can't fix it.

Can anyone offer some suggestions for troubleshooting this? Just need to find a way to get to the bottom of it. I suppose the last-ditch solution would be to just install a DADMom but it's overkill for this room.


TIA!
rich

[creativecontrol]

Yes, there have been some binding issues with DADman and S6 historically, however much of this has been addressed. Please post all of the relevant versions of PT, DADman, S6 software (and macOS version) and we can dig in deeper.

best,


Jeff

[Rich Breen]

I'll have our stage tech Andrew forward the various bits of info - thanks!

[BScout]

We've had similar issues and focusing away from DADman and then focusing back has usually gotten it back. But then it doesn't always stay unless you hit the lock button in the monitor section on the S6. We do run the monitoring DADman on a second system (our Print system) and most of the work happens on the Mix system. So sometimes I go to the workstation tab and explicitly select the Print system so the S6 grabs DADman before switching back to the Mix system.

[Rich Breen]

Originally Posted by BScout

...focusing away from DADman and then focusing back has usually gotten it back. But then it doesn't always stay unless you hit the lock button in the monitor section on the S6.....

Thanks, this used to be the more common problem here, but now it just doesn't connect to DADman at all or only partially. Just very unreliable.

[creativecontrol]

A very simple one to try would be to log in as Admin and trash the MonitoringSettings file:

https://www.dropbox.com/scl/fi/8ryj2...=4q1agi0k&dl=0


best,


Jeff

[BScout]

Jeff, after having a working system, if I make that file uneditable by the system, will the S6 always lock to the same monitoring (vs attempting to guess which system, monitoring software, etc when it starts up)?

For instance, we have the two previous mentioned Pro Tools systems (MIX and PRINT) and DADman is always launched on PRINT and is the one the S6 should control. Can locking that file prevent the S6 from looking at anything launched on the MIX system (like DADman on that system)? That would be very handy if we could making Monitoring a static setup like that.

[creativecontrol]

Interesting. That I'm not sure of. Perhaps Eddie can illuminate.



Jeff

[EddieJones]

Originally Posted by BScout

Jeff, after having a working system, if I make that file uneditable by the system, will the S6 always lock to the same monitoring (vs attempting to guess which system, monitoring software, etc when it starts up)?

For instance, we have the two previous mentioned Pro Tools systems (MIX and PRINT) and DADman is always launched on PRINT and is the one the S6 should control. Can locking that file prevent the S6 from looking at anything launched on the MIX system (like DADman on that system)? That would be very handy if we could making Monitoring a static setup like that.

I'm 95% sure this can't be done as S6 will try to open that file and then fail, possibly deleting it and recreating it.

[andrewyarovenko]

Hi Jeff! Re-Rich's inital post,

Currently we are on the following:
ProTools 2024.3.0
S6 / Eucon 2023.11
DADman 5.7.0.1
MTRX Firmware 2.4.2.2