DADman Monitor not restoring

[B-Grade]

Yes LDS, that feels like the same behavior I'm experiencing. Can we revert to an earlier DADman where this works better? I'm going to try android as well.

[B-Grade]

Well, android has crashed Eucon a few times, and it is also not populating the sources to the Avid Control the same way that it does on the iPad. Also, I'm getting a dialog when I launch DADman "Assertion failed: m_Context /Builds...OGL/OGLContextMac.mm : 319"

[LDS]

Originally Posted by B-Grade

Yes LDS, that feels like the same behavior I'm experiencing. Can we revert to an earlier DADman where this works better? I'm going to try android as well.

I haven't tried reverting to an earlier version of DADman, but generally things are working a lot better here than they initially were. I can't really explain why that is... but I am glad it is! I did go through at some point and assign static IP addresses to everything that allowed it. That might have made things a little more stable.

The issue I am currently having with the monitor section in Avid Control populating seems directly related to EuControl and the way it does or doesn't lock to applications. I don't know if it is by design or not, but when I start up my system EuControl seems to revert to everything being locked to Pro Tools, rather than its previous configuration with monitoring locked to DADman.