mesayre
Max Output Level: -87 dBFS
- Total Posts : 195
- Joined: 2012/07/07 09:29:57
- Location: New York, NY
- Status: offline
ACT "Enable Automation" function question and/or problem
Hello all,
I've been using an a-800 keyboard through ACT, and generally am pretty happy with the mix functionality. However, I have one thing bugging me:
When I want to overwrite automation, if I use the mouse to click the write-enable button on in the track view or inspector, I get a partial write mode that just lets me write the currently-selected parameter (which is what I want, and is what the manual says will happen). However, if I use a button on my ACT surface programmed to "Automation Write Selected Track", it enables overwrite for ALL parameters.
Latch seems to work as expected. Is there some reason the UI button and ACT function work differently? Or is this a bug?
Cheers,
Mike
|
azslow3
Max Output Level: -42.5 dBFS
- Total Posts : 3297
- Joined: 2012/06/22 19:27:51
- Location: Germany
- Status: offline
Re: ACT "Enable Automation" function question and/or problem
2015/07/10 14:49:20
(permalink)
As far as I observe, in case you press "Wt" button, it enable all parameters for automation writing ("Wt" is full red then). You can also enable individual parameters, you get "Wt" button diagonally red.
It is easy to select individual parameters with mouse, but it is more tricky with surfaces. So, normal solution is just enable all. Till you really touch some control/parameter no automation is created. So there is no problem with such solution.
Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc. www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
|
mesayre
Max Output Level: -87 dBFS
- Total Posts : 195
- Joined: 2012/07/07 09:29:57
- Location: New York, NY
- Status: offline
Re: ACT "Enable Automation" function question and/or problem
2015/07/14 00:28:32
(permalink)
THanks for the response.
I agree that it should be OK to enable overwrite on all params, as the manual states that this should only write data on parameters you automate. However, if you enable write using an ACT surface while in overwrite, it immediately begins writing data on all parameters, whether you touch them or not. Then I get a warning message ("Do you really want to write data to 67 parameters?"), and sometimes even get a crash. This behavior is contrary to what the documentation suggests should happen.
|
azslow3
Max Output Level: -42.5 dBFS
- Total Posts : 3297
- Joined: 2012/06/22 19:27:51
- Location: Germany
- Status: offline
Re: ACT "Enable Automation" function question and/or problem
2015/07/14 04:53:48
(permalink)
That is either A-800 or Sonar versions specific. Which Sonar version are you using?
What I want to say is that I have just tried my Control Surface with X2, Latch Mode, All track/synth parameters automation write armed, but only those which I touch during the transport moving are changed.
Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc. www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
|
mesayre
Max Output Level: -87 dBFS
- Total Posts : 195
- Joined: 2012/07/07 09:29:57
- Location: New York, NY
- Status: offline
Re: ACT "Enable Automation" function question and/or problem
2015/07/14 22:10:18
(permalink)
I'm on Foxbro Platinum. The issue occurs when the track is in Overwrite mode, but only if write-enabled via ACT command.
|
azslow3
Max Output Level: -42.5 dBFS
- Total Posts : 3297
- Joined: 2012/06/22 19:27:51
- Location: Germany
- Status: offline
Re: ACT "Enable Automation" function question and/or problem
2015/07/15 04:39:20
(permalink)
From documentation...
Overwrite mode overwrites any existing automation data for the currently armed parameter while the transport is rolling, even if you don’t touch the parameter.
Yes, they also write
Only the parameter currently shown in the track’s Edit Filter.
And I confirm that this part is not true in case Global Automation Write is enables throw Control Surface. All automation armed parameters are recorded. On X2 as well. With any Control Surface. You can try to submit a bug report, but that is a bug in documentation only. Logically, in case you want write automation for one parameter only, you should somehow select this one parameter. A-800 simply has no such function (as well as all other known surfaces). That is possible to do (for example, turning related knob while "Enable automation" button is pressed) but they are not doing that. Till you use my plug-in are configure it such way (yes, it is possible with my plug-in), I do not think it will be changed. But is there any reason to not simply use Latch mode?
Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc. www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
|
mesayre
Max Output Level: -87 dBFS
- Total Posts : 195
- Joined: 2012/07/07 09:29:57
- Location: New York, NY
- Status: offline
Re: ACT "Enable Automation" function question and/or problem
2015/07/26 16:14:34
(permalink)
Hey again,
Thanks for testing it out. Yes, I suppose I can just use latch. I just wanted to see if there was something I was missing. As suggested in the documentation, it can sometimes be helpful to tweak a parameter until I find the right spot, then just write one data point there - which is easiest with overwrite.
Thanks again,
Mike
|