|
|
Post by MIchael Rubin on Aug 7, 2015 8:05:03 GMT -8
It seems that even though I keep my finger on a fader when writing automation in "touch" mode, if I don't move that finger for a short period of time, the fader gets released. Is there a setting somewhere that addresses this? Obviously not desirable behavior or the way physical touch automation faders work IRL. Thanks.
|
|
|
|
Post by Slate Media Technology on Aug 12, 2015 11:09:21 GMT -8
Hi Michael,
Thank you for bringing this to our attention. I am looking into it now.
Kind Regards,
—
Trevor Fedele
Product Specialist
Slate Media Technology // Slate Digital LLC
trevor@stevenslate.com
|
|
|
|
Post by jameyz on Aug 12, 2015 20:05:40 GMT -8
This is a logic bug due to a couple Logic/HUI issues with all controllers.
Hopefully Apple will add a fix in the next LPX update
|
|
|
|
Post by budbrown on Aug 29, 2015 6:37:05 GMT -8
Unfortunately, it seems the Logic 10.2 update has not addressed this terrible situation with touch automation. The behavior noted by the OP is still present, as well as an approximately 1-2 second delay for the fader to return to the original value after lifting your finger off the fader following an automation pass. Thus, one of the most attractive and useful aspects of the Raven, that of being able to use the MTi's long throw faders ( with or without fine resolution) to write touch automation in Logic is still unavailable to us. Note that these problems are not found when using touch on the Logic faders themselves, only with the MTi overlay mixer, so it doesn't seem to be an issue with touch screen integration per se. I, along with all the other Raven Logic users I'm sure, would love love love Slate to be more proactive in addressing this issue. I don't think hoping that Apple might provide a fix in a future update is going to work. This needs to be pushed at every level, otherwise the Raven Logic user base will continue to languish with a crippled system.
|
|
|
|
Post by Slate Media Technology on Aug 31, 2015 7:57:28 GMT -8
Hi Budbrown,
We are aware that the issue has not been address in the most recent update. We have been and are working with our developers and Apple to resolve this issue in a timely manner.
Thank you for your patience.
Kind Regards,
—
Trevor Fedele
Product Specialist
Slate Media Technology // Slate Digital LLC
trevor@stevenslate.com
|
|
|
|
Post by pirateman on Aug 31, 2015 8:14:48 GMT -8
I was just about to post the same thing! Glad you are aware... Danny  NB Just replied to your other question... |
|
|
|
Post by gphawk on Oct 5, 2015 19:06:33 GMT -8
With 3.0 has this issue been resolved?
|
|
|
|
Post by Slate Media Technology on Oct 8, 2015 9:47:14 GMT -8
This has not yet been resolved. We currently have ongoing development to resolve it.
Kind Regards,
—
Trevor Fedele
Product Specialist
Slate Media Technology // Slate Digital LLC
|
|
|
|
Post by thesoundpost on Jan 23, 2016 4:15:35 GMT -8
I stumbled upon this thread, trying to find out what kind of problems users of other DAWs are dealing with. Being a Nuendo user myself, I soon came across a nasty automation bug that I assumed must be a Cubase/Nuendo thing. I see now that I was wrong. It has been around for quite some time and it is obviously not a 'Logic only problem'. I have the exact same problem in Nuendo using touch automation. Is this problem still present in Logic today? If you're interested, here's my post: slate.boards.net/thread/826/raven-mixer-automation-problemsBest regards, Marty. |
|
|
|
Post by jameyz on Jan 23, 2016 8:20:09 GMT -8
Actually this doesn't happen in Logic anymore.
|
|
|
|
Post by thesoundpost on Jan 23, 2016 10:42:32 GMT -8
Actually this doesn't happen in Logic anymore. Good to know. Couldn't find in this thread if it did. Thanks. |
|
