Shift + fader sets level to 0db

[Picture Start]

That sums up my experience too. It's not convenient like before. In the past, you could hold shift and move the fader then release and it would consistently snap. Now you can't hold the button and make multiple snaps in one go. It's better than nothing but I'd like the original functionality back please.

[Picture Start]

For you product team people, I've made you a quick video to highlight what is wrong with the current "fix" and what needs to happen to bring this functionality back to where we were 2 years ago.

On the MC Mix, notice the following repeatable behaviors:
1. Hold the button and tap the fader and it snaps to 0dB.
2. Hold the button and move the fader, it fails to snap when I let go.
3. Now, let go of the fader and touch it again, nothing happens.
4. Even if I let go of the button, then depress the button, then re-tap the fader, nothing happens.
5. I have to let go of the button, then move the fader manually in order to make the fader "ready" to receive another shift+tap. It's several annoying behaviors in one.

VIDEO: MC Mix Fader FAIL

On my MC Control, notice that the faders behave 100% correctly:
1. So long as the button is depressed, the act of "letting go" of the fader, snaps it back to 0dB. The device doesn't care what I was doing with the fader. THIS is what needs to happen across the board!

VIDEO: MC Control WIN



Mac OS 10.10.2, Both surfaces recently firmware updated to the latest.

[Picture Start]

I just discovered, at my cutting room, that the option key does all the things desired that the shift button currently fails to do:

VIDEO: option key works

[alaiho]

Unfortunately the 3.3 version does not work as well as 3.0.1.

There is still a problem where the McMix's fader sends the "fader to zero" message to the DAW, but it does not update the fader status in the controller itself unless you change the fader's value in the DAW.

Programs affected are at least Logic X and MIOconsole, both are the newest versions.

I appreciate the effort of the Avid team for trying to solve this problem, but at the same time I'd like to see it sorted out.

At the moment I'm unable to use the unit with Logig X, because it is not compatible with EuCon ver. 3.0.1.

[ALSTUDIOS]

Originally Posted by alaiho

Programs affected are at least Logic X and MIOconsole, both are the newest versions.

Hi

I'm on Cubase Pro 8 and have mandatory to use the EuControl v3.3 due to the Cubase internal driver, which doesn't allow to use older versions anymore.

Confirm the issues with the Artist Mix as shown in the video.
The DAW Mixer set the fader always to 0dB, the fader on the Artist Mix does it just sometimes.

- work around -
If I just change the channel on the Artist Mix one time left und back, the fader on the Artist Mix set to 0dB as well.

Not that revolutionary hint, but it works.


Cheers

[Kyle Splittgerber]

Hey Guys,

We've improved this quite a bit in EuControl 3.3.1, just released today. Will you guys give that a shot? Note: If you have already reset a fader, and are still holding the SHIFT switch while moving the fader, your DAW may not recognize the fader move, and you may not be able to reset the fader. If you want to reset the fader again, move the fader slightly, touch and hold SHIFT, and then tap or move fader to reset to 0 db.

Thanks.

[alaiho]

Hi!

I just tried this today. The version 3.0.1 works better than 3.3.1 so I'll still stick to that.

Would it help if you would just tell the McMix to update it's faders (to match the client software) every time operatos finger leaves it? This seems to be the problem still.

[Picture Start]

Originally Posted by Kyle Splittgerber

Hey Guys,

We've improved this quite a bit in EuControl 3.3.1, just released today. Will you guys give that a shot? Note: If you have already reset a fader, and are still holding the SHIFT switch while moving the fader, your DAW may not recognize the fader move, and you may not be able to reset the fader. If you want to reset the fader again, move the fader slightly, touch and hold SHIFT, and then tap or move fader to reset to 0 db.

Thanks.

Hi Kyle,

I wish you guys would watch the two videos I posted about 3 messages ago, as they very clearly show what is wrong and what needs to happen.

I just installed 3.3.1 and I'm seeing the exact same behavior from 3.3.0, namely, the fader ignores the shift button until you move it AGAIN, like in your disclaimer. This isn't a "good feature", because all you have to do is use the keyboard's option key instead and see how it is supposed to work, namely, in a fluid and intuitive manner. To return to the functionality we all want: no matter what you're doing with the fader, so long as the button is depressed, it will snap to 0 when the fader is released. There can not and must not be stipulations about when the fader decides to react to the snap command, as in your post, "Note: If you have already reset a fader, and are still holding the SHIFT switch while moving the fader, your DAW may not recognize the fader move, and you may not be able to reset the fader. If you want to reset the fader again, move the fader slightly, touch and hold SHIFT, and then tap or move fader to reset to 0 db." This constitutes a failure to understand what your customers need, in my view. Again, the option key DOES recognize the fader move... therefore, the MC Mix should too.

In addition, "double-tap to snap to zero" didn't work for me, and honestly, I don't think I want it to. Tapping a fader causes a small deflection that will show up in the automation.

[Kyle Splittgerber]

Originally Posted by Picture Start

Hi Kyle,

I wish you guys would watch the two videos I posted about 3 messages ago, as they very clearly show what is wrong and what needs to happen.

I just installed 3.3.1 and I'm seeing the exact same behavior from 3.3.0, namely, the fader ignores the shift button until you move it AGAIN, like in your disclaimer. This isn't a "good feature", because all you have to do is use the keyboard's option key instead and see how it is supposed to work, namely, in a fluid and intuitive manner. To return to the functionality we all want: no matter what you're doing with the fader, so long as the button is depressed, it will snap to 0 when the fader is released. There can not and must not be stipulations about when the fader decides to react to the snap command, as in your post, "Note: If you have already reset a fader, and are still holding the SHIFT switch while moving the fader, your DAW may not recognize the fader move, and you may not be able to reset the fader. If you want to reset the fader again, move the fader slightly, touch and hold SHIFT, and then tap or move fader to reset to 0 db." This constitutes a failure to understand what your customers need, in my view. Again, the option key DOES recognize the fader move... therefore, the MC Mix should too.

In addition, "double-tap to snap to zero" didn't work for me, and honestly, I don't think I want it to. Tapping a fader causes a small deflection that will show up in the automation.

Thanks for the feedback. We'll keep working on this. FWIW, the "VIDEO: MC Mix Fader FAIL" shows exactly what we called out in the note. You are holding SHIFT to reset a fader that has already been reset to zero. The DAW is ignoring it, hence the problem. In cases where you don't do this, the reset behavior should be much better (more consistent) than it was before. Are you seeing that?

[Picture Start]

Originally Posted by Kyle Splittgerber

Thanks for the feedback. We'll keep working on this. FWIW, the "VIDEO: MC Mix Fader FAIL" shows exactly what we called out in the note. You are holding SHIFT to reset a fader that has already been reset to zero. The DAW is ignoring it, hence the problem. In cases where you don't do this, the reset behavior should be much better (more consistent) than it was before. Are you seeing that?

Hi Kyle,

What I'm seeing is that when you press the button down in 3.3.1: There is an approx 200-500ms delay between tapping the fader and it moving, compared to holding the keyboard's option key and seeing more or less immediate action.

You're saying that "The reset behavior should be much better (more consistent) than it was before." but in fact, the very nature of how you have "fixed" this bug is such that reseting the fader is wholly inconsistent to the behavior to which we, the users, are accustomed.

I seriously appreciate the work and time being put into this fix, but I still feel like nobody there knows what we want on account of the lack of comment on the discrepancy between using the SHIFT button on the Artist and the keyboard's OPTION key. Everything about the option-key methodology is what used to happen back around version 3.0 and before to the dawn of these devices. And we like it that way.

What I personally dislike about this new behavior is that there are now 3 more steps involved in reseting the fader. Because we users are all used to holding down the button and the faders flying back to zero upon let-go, when you try to do this now, A) the faders don't move, then B) you have to manually move each fader you want to "become eligible" to move without the button down, then C) you hold the button and have to tap them all again. I don't think there should be any LOGIC to determine whether or not the faders reset—one simple rule: when the button is down, the faders reset!

I promise you, just mimicking the OPTION key will solve every problem. Here's a video showing you the delay.

VIDEO