Hi John, As mentioned in the first message in this thread and I quote >>I am using a Euphonix MC Mix/ Avid Artist Mix<< The faders are transmitting touch data and Sonar is receiving and writing data accordingly. The issue, as outlined, is that Sonar does no detect fader being 'untouched' or finger contact removed and therefore goes on writing null or stationary data for a predetermined time after the data stream stops (almost a second). Thus, even in the new 'Touch' mode (yes its enabled in the new tab) previously recorded automation is needlessly overwritten. I would prefer and indeed expect that Sonar would detect that the fader has been released and cease writing data instantly, so that no data is inadvertently and needlessly overwritten. I would have thought that this would be the most logical way for such an automation mode called 'Touch mode' would be expected to function. Touch sensitive controllers are now commonplace. Indeed Cakewalks own surface is touch sensitive I believe. Would it not be logical for Sonar X2 (it being oh so very advanced) be able to fully sense fader touch status.

Which control surface dll are you using? If your physical surface has touch sensitive faders, then its likely that the surface dll has not been updated to transmit touch.

Noel Borthwick [Cakewalk
]

Which control surface dll are you using? If your physical surface has touch sensitive faders, then its likely that the surface dll has not been updated to transmit touch.

Or there is no Euphonix MC Mix/ Avid Artist Mix dll and the OP is using it in Mackie mode.

The way to tell if a CS is transmitting touch is a track selection should occur when a fader is touched.

Hi Noel Thanks for once again devoting some of you time to this issue. As mentioned at the top of the thread in the OP and in my latest response to John. I am using a Euphonix MC MIX now called the Avid Artist Mix. I have downloaded and installed the Cakewalk EUCON Control Surface Support package. I am running eucontrol 2.6.2 the latest version. Touch is being transmitted by MC Mix and is being received by Sonar X2. As highlighted in your last message it is untouch or touch off that is not being recieved or understood by Sonar. To quote you Noel. >>This is because with a mouse there is a notion of a mouse button up message. Most surfaces do not have touch sensitive faders so SONAR must implement a timer to guess when the user has stopped moving a fader. This behavior is not new to X2. << I agree that this is not new to X2. I do feel however that this is not very progressive as the majority of control surfaces now being sold do have fader touch sensitivity. Would it not be wise for Sonar X2 to be able to tell when a fader is being touched OR NOT and be able to stop writing automation data to a track based on this state thereby not overwriting upcoming data after the fader has ceased being touched. Logical and expected I would think in a touch mode with touch sensitive faders.

I'm not personally very familiar with the EUCON dll but will try and find out more about this as to why touch off is not handled.

That would be absolutely fantastic Noel. Thank you very much indeed.

  No John, the OP is not using Mackie mode. I am using Eucon Controller. This option is only available after you instal the EUCON Control Surface Support developed by and downloaded from Cakewalk support. The eucontrol protocol uses ethernet rather than midi to achieve fast, network assignable control and very high resolution control data. It is used by the Artist and the Euphonix series consoles. As it is now owned by Avid it may become the standard professional studio desk control protocol for all Avid / Protools systems. Additionally eucontrol is application aware and remaps instantly as instances of one or many different applications are focused. In short, its very cool indeed. BTW Track selection IS occuring when a fader is touched. Best Chris

I redid the test again now that I have a better understanding of the problem. On the MC using the touch mode the witting does not stop instantly when you release the fader.

But touch mode and touch sensitivity may not be the same thing I would think. That is touch mode may not be using the touch of a surface but the end of movement to determine when the automation is to stop. It should what ever mode its in but I don't think CW has Sonar set up for that. It is true that there are more touch sensitive CSs around now but far more CSs without it still. None the less all of us that do have it should be supported.

Right now I'm not sure what is going on or what to expect. I do know that the Logic Control had all these modes with Logic. But I can't recall what each mode did differently and how.

You may have brought an issue to the forefront that needs further explanation.

In the case of the Mackie Control the copyright is 2002-2006. Which means to me no updates have been made for a long to it.

Also keeping on the subject touch in the dialog we have an option to touch the fader and thus select a channel. This obviously has nothing to do "touch mode".

Really the MC is being wasted under X2. It should work with the ProChannel but it doesn't.

Thanks for your update John. I think you can now see what I am getting at. I tried protools again and the touch select of channels that you mention is absolutely instant in PT 9. In Sonar it's not so snappy. In Protools there is a tiny delay after you lift your finger off a fader before it exits write and smoothly ramps to where the previously written data is. This is worth mentioning. Protools rapidly splines to the existing data rather than a linear jump. Very musical and a very good guess at what we would all prefer. 

I think that this would be a feature worth completing to the expected level. 

Actually, a very good start might be to simply quarter the time sonar waits for new data before it exits automation write. This may solve the problem entirely.