Shift + fader sets level to 0db

[alaiho]

Hi!

The Eucon Feature "Shift + fader sets level to 0db" hasn't been working since version 3.1 update in december 2013. The feature is essential in my workflow, both live and studio, so I have had to fall back to the version 3.01 for five times already.

Now as Apple updated Logic X to version 10.1 the EuCon v.3.01 is not supported by it any more.

Has Avid any plans to fix this issue?

[thewiz]

The shift+fader works on my system using the last software, and the latest Logic X update fixed the EuCon support.

[alaiho]

Interesting, I thought I had already tried it out. I'll doublecheck the issue.

[alaiho]

I tried the Latest EuCon today, but it doesn't work on my system.

By any chance, could you please send me detailed specs of your setup so I could compare it to my own for troubleshooting the issue? I could start by taking everything you are not using off from my system.

I tried all the usual fixes, like removing all preferences and using a dedicated Network for EuCon. But it didn't help.

[jigdagod]

I'm having the same issue. My artist control works just fine. Once I try it on my (2) artist mix it'll do it once and stop working after that. It'll do it on the screen, but the fader won't move with it. I tried on the latest software and 3.2. I'm a Windows 7 64-bit user. Pro Tools 11.

[alaiho]

Yes, the message goes from the Controller to the DAW, but motorized faders don't behave as they should.

The EuCon version 3.01 works fine.

[jigdagod]

Originally Posted by alaiho

Yes, the message goes from the Controller to the DAW, but motorized faders don't behave as they should.

The EuCon version 3.01 works fine.

I will try it when I get home today.

[O-WYO]

According to Avid Tech Support, the shift+fader=0dB feature was disabled, beginning with v3.1.

My experience bears this out. After numerous back-grades from v3.2.1, the latest version that provides S+F=0dB functionality is v3.0.1 (at least on my system - Mac Pro, OS 10.9.5, Cubase 7.5.40).

[C52382P]

Are you kidding me? They are claiming they disabled it on purpose!?!?!?! Yeah because disabling it would NATURALLY mean that you leave it partially functional. What the actual F*CK?!?! Between this never-ending BS and deciding they want to charge us for incremental updates to ProTools I might be about to jump ship after ten years. It is clear that something is very, very wrong at AVID.

[O-WYO]

Originally Posted by C52382P

Are you kidding me? They are claiming they disabled it on purpose!?!?!?! Yeah because disabling it would NATURALLY mean that you leave it partially functional. What the actual F*CK?!?! Between this never-ending BS and deciding they want to charge us for incremental updates to ProTools I might be about to jump ship after ten years. It is clear that something is very, very wrong at AVID.

Yup. They disabled it on purpose. I don't recall the specific reason; but, if you search the forum, you'll likely find it (if it hasn't been removed).

Not long after disabling S+F=0dB, Avid disabled connections through WiFi, LAGG, VLAN, and who knows what other limitations were imposed. Their explanation is they don't want to provide the tech support.