MOTUnation.com

greetings everyone, and a mayday from the tension headache studio.

i have been using DP8.01 in 64-bit mode and a Euphonix MC Control with no trouble - until this week.

an update for Eucon (the driver and setup configuration software for the control surface) appeared on the Euphonix / Avid website and, to my now-chagrin, i went ahead and applied it.

consequently DP in 64-bit mode no longer recognizes the MC-Control. And the Eucon driver does not appear as a choice in Control Surface Setup, so i can't re-introduce them (Eucon simply isn't on the list).

touchscreen, faders and transport controls are all knocked out entirely (soft keys are still there but i believe they must be memorized within the Eucon setup itself and therefor do not rely on the same kind of connection as the others).

Oddly enough, Eucon's setup sees DP and claims to be connected to it.

i rolled back to the last driver version that had been working for me, Eucon 2.6.1, but that did not resolve the problem (which kind of surprised me actually, but aint that just how these things go).

the control surface firmware version reports being the latest available and does not seem easily roll-backable.

If i set DP to run in 32-bit mode, everything works again. but i have 10 reasons why i would much rather run DP in 64 (one for every gig of RAM in my system over 4, to be exact). so i'm posting my troubles here to see if any among you has a recommendation or suggestion, and also to report them as a kind of warning to anyone else with a similar setup that is currently functioning but who might be about to apply this update.

i'm not terribly enthusiastic about the idea of paying Avid (Av0id?) a per-incident support fee on account of an update of theirs taking out my system. and for their part, i can also understand them being less than heroic about coming to the rescue of Digital Performer.

i'll do it if i must but first i turn to you all to see if there are any ideas out there.

respectfully yours,
O-2k

PS: i don't know whether or not the Group Mind has already discussed the topic, but if not i wonder whether you all have any personal trends you follow regarding When To Not Take The Updates.

obviously, OS security updates and OS java, you would take. but yeesh, these companies and their "improvements"! if an update claims to be recommended for users of 10.6 and up, does that actually translate as "lay the heck off" if you speak 10.6.8?

FWIW: I bought a Eucon just after DP8 came out. Hooked it up. Nothing. No Eucon<->DP love (other stuff worked with the Eucon however). Went to the Avid website, grabbed and installed the then latest driver, still nothing with DP. (Worked with other software though.) Much hair pulling, teeth gnashing, and emergency posting ensued.

Then I noticed that the latest Eucon DP bundle installed by the Avid update software at that time predated the DP Eucon bundle by a year. Reasonable to assume the updated Eucon bundle that shipped with DP was more current, so I reinstalled DP over itself.

And the Eucon worked.

Am sorry to hear there is an issue with the post DP8 Eucon driver. I'd reinstall DP. (Doing so did not appear to wipe out settings, but back up customized key commands, etc.) I am sure there is a way to deconstruct the install package to grab just the Eucon bundle, but couldn't advise you to well on that.

Was considering the update, but will obviously hold off. Thx.

i really appreciate your post very much because, in fact, i was considering trying just that. but i held off owing to uncertainty (re-installing DP seemed pretty... extreme somehow).

your suggestion gives me the sense that i can re-install DP without too much collateral damage, tho, and i think i'll give that a shot.

i just want to confirm: are you using Eucon 2.7, or earlier? and may i ask what firmware version the hardware reports?

again, many thanks for taking the time to weigh in.

O2k

Thanks for this thread! I was suspecting that Eucon was making my DP project a it buggy, and discovered the Eucon 2.7 update, which I installed. And then I also found that Eucon was not available in DP.

So I went and restored the Eucon.bundle form Time Machine, and now it seems to work again

I will see if it works better with DP, but now I have a new weird problem, in that now I have no cursor control in DP..... if it's not one thing.....

I shall reset everything and try again... but at least one mystery has been solved!

Thanks

SWT

thanks for the input. where would i find the Eucon Bundle? although i'm leaning pretty well towards simply re-installing DP entirely, that piece of info would be valuable to have.

all the best, and, like soupy says, "keep those cards and letters comin' in".

O2k

Aha, repairing permissions got my cursor control back all working now!

The Eucon.bundle lives in Library>Audio>Plugins>MOTU Control Surface

If you don't have backup of the old bundle, PM me and I'll send it to you.

Oh, and I didn't have to reinstall DP.

Cheers

Stephen

otalgia-2000 wrote:i really appreciate your post very much because, in fact, i was considering trying just that. but i held off owing to uncertainty (re-installing DP seemed pretty... extreme somehow).

your suggestion gives me the sense that i can re-install DP without too much collateral damage, tho, and i think i'll give that a shot.

i just want to confirm: are you using Eucon 2.7, or earlier? and may i ask what firmware version the hardware reports?

again, many thanks for taking the time to weigh in.

O2k

Firmware is 1.34
Eucon is 2.6.1

cheers

hey everyone

i am delighted to report that, thanks to all of your invaluable assistance, service is restored.

i can scarcely express my relief, and my gratitude for such generous assistance. i'm lucky to be a newbie in a community with so many people who are willing to give of their time to assist a stranger in need.

now writing on blackboard ten hundred times:

1. if it aint broke don't fix it.

2. apply updates only when there's nothing to lose.
2a. as well as data in projects, "nothing" extends also to: hours of your life, points on your blood pressure, wear on dental work (from grinding teeth), deterioration of current special friendships you may be involved in (on account of unassailable grumpiness), etc.

thank you all again!

O2k

Just to clarify what is working for me with my MCMix:

OSX 10.8.2
DP 8.01 64bit
EuControl 2.7
Eucon.bundle 1.1

Cheers!

Stephen

Thanks Stephen, it works

I'm using my MC MIC with the good old Eucon 2.5.6 with DP8.01 at 64bit over Mountain Lion 10.8.2

Everything is working great!

Best regards.

delcosmos.

I had this trouble... And contacted Motu support who got back to me straight away.. They advised me to simply re-instal DP8.01 again. Eucon is working perfectly again.

Hello,

We just published a Tech Note, which should help clarify what is going on with EuCon support in DP 8:

http://www.motu.com/techsupport/technotes/64biteucon

Cheers!
Lorne

MOTU_Tech wrote:Hello,

We just published a Tech Note, which should help clarify what is going on with EuCon support in DP 8:

http://www.motu.com/techsupport/technotes/64biteucon

Cheers!
Lorne

Great to hear from you Lorne, GREAT that you guys are popping into the forum.Thanks!!
Now if you guys can just get Eucon totally integrated so that it can ride EQ’s and effects properly, I’d be thrilled. As it stands now, if you use Eucon to automat an EQ for example, you have to click on the EQ in DP after any edit to wake DP up and have it take back control of the EQ. The automation moves do get written, bet there seems to be a lack of 2 way communication such that the moment Eucon take over control of an effect, DP loses track of it unless that particular parameter that was automated by Eucon gets touched again in DP.
Alos, Eucon’s faders never chase to the parameter values of any effect it is controlling.
Please work on this 2 way communication between DP and Eucon.

Thanks again for coming to the forum.

The mixer tracks don't get updated on the euphonix. MC Control will always show all my tracks regardless of what is visible in the DP mixer.