X2 Automation

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.

make sure on the track inspector under the track tab that automation write mode is set to touch and not latch or overwrite. the other thing you can do is to set the punch in/out options to the range you want edit. any automation will only be written to that range, leaving everything else unchanged.

doesn't a touch-sensitive controller give a "un-touch" event, a la mouseup event, that could be grabbed, or does sonar just not look for it because most controllers don't fire it?

Ok so we are just going to leave this wonderful 'touch' feature as an unfinished oversight then are we. Fabulous.

creynolds


Ok so we are just going to leave this wonderful 'touch' feature as an unfinished oversight then are we. Fabulous.

It might help if we knew what controller you are using.  In my case I use the MC and it does have touch sensitive faders.

But in the setup for it you can turn them off.

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.

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.

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

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.

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. 

You're seeing a bit faster response now? If so it could very well be due to a fix in X2a. 

Whew!! It is not just me...
So is this an issue with ALL control surfaces and Sonar?
See my post...(I can't create hyperlinks for whatever reason???) cut and paste into browser
-- forum.cakewalk.com/fader-lag-release-latency-setting-m2861029.aspx --
 
With the vs-100 you would think it would be flawless, but no... release the fader wait... then it snaps back. Average time from release to snap back is approx 1.3 secs at 44.1 or 58,800 samples.
Absolutely beyond sub-pro.
I might be heading back to the digi camp if they can't figure out how to release a silly fader.
 

Noel Borthwick [Cakewalk]
In X2A the touch timeout value was reduced quite a bit. I think this is what you are seeing.

 
Should it be a timeout at all? Why not respond to to my release? I know these faders transmit some kind of signal.
 
OK i did research and found motorized faders generally use a capacitance sensing circuit to determine if someone is touching the fader.
And you use software to determine at what capacitance the fader considers itself touched and what to do if touched.
It is written in code just like php or any other code with a true or false or 0 and 1 statement.
Like:
Fadertouch {
 if capacitance = 700 {
do this thing};
else {
do this other thing};
}
 
SOURCE - Cody Hazelwood - Look for "TOUCH SENSITIVITY" section --
Again cut and paste in browser
--- hazelwoodsound.com/motorized-faders-and-the-arduino ----



The expensive touch fader acts as if it is not touch sensitive at all and waits for a given time... like the fader is asking, "are you done yet?"
 
Try This...

• click on a fader in console view (make sure it is in touch write mode)
• Use your mouse scroll wheel
• duck a single word or note real quick by spinning your scroll wheel...
• the fader move down... holds for a set period then releases... approx release or timeout time is 1.45 secs

Touch sensitive fader should not suffer from that timeout code in the software writing. Touch faders should have their own lines of code.
 
Granted those duck outs are not something I do a lot of, normally I fine tune via mouse selection. However, it feels a bit wonky and cheap and it doesn't seem like a lot to ask for...
 
Please make my touch sensitive faders respond to my release and not have some predetermined timeout.
And if it must be predetermined allow me to make changes in the prefs. Like fader touch time out = 0ms.