S6 monitor section disconnects from DADman

[andrewyarovenko]

Oh and MacOS 13.6.5

[creativecontrol]

Thanks. Please let me know if trashing the suggested monitoring XML file had an effect on the issue?

When this occurs, it seems to be a timing issue with the handshake between WSControl, DADman and Pro Tools.

Please let me know how your workstation is booted up from cold and what apps are auto-launched or manually launched and in what order?


best,


Jeff

[Rich Breen]

Originally Posted by creativecontrol

...Please let me know how your workstation is booted up from cold and what apps are auto-launched or manually launched and in what order?

Typical boot-up is S6, then computer, then WSControl, then DADman, then ProTools. I think I've tried every possible sequence though and have yet to find one that *always* works, though I couldn't swear to it.

[creativecontrol]

That should be fine. Please advise on the pref.

best,


Jeff

[andrewyarovenko]

Re: deleting monitoring prefs--
I've finally been able to replicate the issue while I was present and deleting monitoring prefs resolved it at least for now. Time will tell whether this mitigates the issue in the long term... Hard to say as we haven't found a sure way to get the issue to occur.

[lucienpalmer]

Originally Posted by 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

I just upgraded from Ventura to Sequoia and in the process all my MacPro network settings were deleted for all four network ports. I've been able to reset everything, except DADman can;t see the MTRX. A workaround is to log out of the user and log back in.

But the S6 monitor section can't control DADman. The monitor names and their levels get transferred when they first connect, but the knobs and buttons are unresponsive.

I found this thread, and it feels like a similar issue. I just tried deleted the monitor prefs on the S6, but that file doesn't exist in that folder. Photo attached.

[creativecontrol]

Greetings,

What version of S4S6 Software are you running currently? I'm also curious about that Temp Settings subfolder.



Jeff

[lucienpalmer]

Originally Posted by creativecontrol

Greetings,

What version of S4S6 Software are you running currently? I'm also curious about that Temp Settings subfolder.



Jeff

Hi Jeff,

v 2024.10.0.19

Inside the Temp Settings folder is a single file called "interfacechange" only 1Kb.

Also, I just noticed that I can still change sources with the MPM. It's only the monitor section on the MTM that can't control DADman.

[lucienpalmer]

I just restarted WS Control, and that got the S6 monitor section working again. I'll try turning off auto login for WS Control, too. Then figure out the magic startup sequence.

FYI, the only factor that changed was updating to Sequoia. I never experienced this in Ventura.

[creativecontrol]

Thanks. Yes, the startup soup needs to be examined further on our end I would say.

best,


Jeff