I FIXED IT! Unfortunately I had to go through all of the steps including uninstall and reinstall and still initializing the Eucon failed. And then I got adventurous and decided to enable the Eucon controller when there was no session open. And voila!!!!! It went through.
So the bug is: Do not try to enable the Eucon peripheral while a session is open. It comes up with an error that makes you think this function is broken....
Quote:
Originally Posted by Bob Katz
Thanks, Eddie. OK, I'll go through that.
|
Well, we're still dead in the water. Here are the EXACT steps I went through:
Pro Tools uninstall:
1 backed up all preferences etc. using Trasher
2 trashed preferences etc. using trasher
3 uninstalled pro tools and HD driver etc. using Programs and Features in 8.1
4 Eucon uninstall:
Ran the installer and checked uninstall, did not remove user preferences
5 Reinstalled Pro Tools HD including the HD driver, Avid effects, etc.
6 Restarted
7 Launched Pro Tools with these virgin preferences to ensure it is stable before reinstalling Eucon
8 Launched the newly installed PT, to see it's stable with default preferences. Set the hardware to my RME MADI, tested a session, which plays stably, and quit.
9 Reinstalled the Eucon workstation
10 Restarted
11 Inspected Eucon workstation control panel. Surfaces come up exactly as before.
12 Launched Pro Tools, still with semi-virgin preferences.
13 Tried to initialize Eucon. "Error occured while trying to load controller personality Eucon." If you don't think I'm pissed, then you're wrong. Please escalate this to the next level... that was a ****load of work to come up with the same result.
14 Using Trasher, I restored my preferences
15 Now I tested the S1 control and the tablet by releasing them from Eucon Control in Studio A and reconnecting them to the Eucon control in Studio B. I launched Pro Tools on the Mac in Studio B and I am able to control Pro Tools remotely from a different studio
16 Conclusions: Something’s wrong with the Pro Tools installation in Studio A but I think it’s something missing in the installer or wrongly configured. Probably a missing or defective DLL.