Behringer BCF2000 and AA3.0

Does anyone have the Behringer BCF2000 and has it hooked up to AA3.0?

I am having a specific problem with "touch" automation and getting the faders to correctly respond. I have it in Mackie Emulation Mode which i believe is pretty much a standard setup. However, when i want to fade in the volume at the beginning of a track, i set it to "touch" and start the song while immediately pulling the fader to the bottom, when the track is about to start, i let go of the fader, expecting it to jump back up to the static mixed volume. It seems as though the motor in the fader resists my touch when i start, but appears to sort of give up a couple of seconds in. When i do let go of the fader, it does not move at all. Then i nudge it up a little, and it snaps up to the automation. This is not the desired effect though. I end up having to go in and manipulate it with the mouse anyway, which kind of defeats the purpose.

Does this happen to anyone else that has this setup? Is it something that the default emulation mode just does? Is there a setting in audition that can specify some kind of motor timeout or something that i could set to a higher value? Am i just crazy? Lots of questions.

I called Behringer and they seem pretty intent on it being audition, as the BCF is simply sending/receiving MIDI codes, so there's nothing specific that would be changeable on the BCF side.

Please audio masters of the world! Any help would be appreciated to make my birthday gift a reality!

I've no idea how other control surfaces behave (probably the same way), but you are right about this behaviour in "touch" mode. I've never looked at this mode much as its behaviour is not much use for me. I normally just use the clip envelopes or "write" mode if I use automation which I seldom do.

It seems as though the motor in the fader resists my touch when i start, but appears to sort of give up a couple of seconds in. When i do let go of the fader, it does not move at all. Then i nudge it up a little, and it snaps up to the automation.

Apart from this, automation seems to work as described in the manual.

Sorry to have not been much help, I can only suggest changing your method and using "write" or "latch" mode. Which is not what you wanted to hear...

Well, 'write' simply records the movements you make as you make them on the fader, and latch will do the same, except it will wait for you to make the first move. But touch is exceptionally useful because it will only record your movements while you are making them, then it returns to normal. This way, you can make several passes at automation without having to re-record the whole thing to make changes to an existing automation. I use it to fade in the beginnings and fade out the ends mostly. The other options DO work, but i see no reason why the usage of touch mode should work any differently on the control surface than it does in AA3.0

Does your control surface operate in the same (IMO faulty) manner? Does anyone know a setting or something that can alter this effect?

I do appreciate the response, BTW.

Does your control surface operate in the same (IMO faulty) manner?

Yes, and I suspect the cause is coded in Audition unfortunately.

Ok so it's not that my setup is anything unstandard. Do you use other software like Cubase, Logic, etc... where the control surface behaves properly in touch mode? That would make me think that it might be possible to configure audition to work differently? Im new to this control surface, so im not sure how difficult that will be if it indeed can be altered.

The BCF2000 is not touch sensitive, so that kind of makes things difficult.  Mine's in the cupboard these days, and the touch-sensitive AlphaTrack is on the desk!  (But I admit I don't recall trying that with AA3 yet - must do....)

The BCF2000 is not touch sensitive

So the thing that is keeping me from what i need is the lack of touch sensitivity? Or is it something different?

There was a thread over on KVRAudio about this awhile back...

.. ah, found it.
http://www.kvraudio.com/forum/viewtopic.php?p=690966

Apparently, modifying the deadtime parameter in the BCF Tool may help with the whole fighting the fader problem.  Or not, as someone mentions a few posts later.

Can anyone translate these instructions for me?

- go to global edit. (press edit & store)
- Adjust the latency with the encoder 7 to your liking
- now you don't have to fight anymore with your automation.

I tried this and it doesn't do anything.... not to mention, my screen simply has 2 dots on it, isn't it suppose to be showing me which preset i am on or something? Is that a different post?