The title says it all.
How do I automate parameters in Massive just as I can with Reason's default plugins?
Automation with Massive?
- Raveshaper
- Posts: 1089
- Joined: 16 Jan 2015
This should be possible, sort of, by sending CV signals into the parameters you want to manipulate and draw the automation for the things sending the CV. Like using a Thor rotary to send its knob position out as a signal and drawing clips to move the knob.
Enhanced by DataBridge v5
if you are talking about clip automation, you click automate on the top of the plugin and click the knob you want to automate and it will appear in the sequencer like it would a RE
It is as easy as Aeox says.. Click Automate, click (or move) the parameter, and a lane is created.
Automating while recording, by moving a parameter while recording, also just works ( provided you didn't disable "record enable parameter automation" )
Automating while recording, by moving a parameter while recording, also just works ( provided you didn't disable "record enable parameter automation" )
V9 | i7 5930 | Motu 828 MK3 | Win 10
- AttenuationHz
- Posts: 2048
- Joined: 20 Mar 2015
- Location: Back of the Rack-1
Guessing its down to how it was recorded but how did you stop the sequencer from jumping to the front when the automation lane was created?
It is not too much of an ask for people or things to be the best version of itself!
It was at the beginning, the sequencer was neither running or recording, so there was no jumping; only creating the lane.AttenuationHz wrote: ↑10 Jul 2017Guessing its down to how it was recorded but how did you stop the sequencer from jumping to the front when the automation lane was created?
V9 | i7 5930 | Motu 828 MK3 | Win 10
- AttenuationHz
- Posts: 2048
- Joined: 20 Mar 2015
- Location: Back of the Rack-1
Ah nice that has been bugging me for so long de-arming for recording stops it. Wish there was a option in preferences for that though!Olivier wrote: ↑10 Jul 2017It was at the beginning, the sequencer was neither running or recording, so there was no jumping; only creating the lane.AttenuationHz wrote: ↑10 Jul 2017
Guessing its down to how it was recorded but how did you stop the sequencer from jumping to the front when the automation lane was created?
It is not too much of an ask for people or things to be the best version of itself!
Oh my god, how the hell did I not notice that. Thanks!
Best answer with video ever
-
- Information
-
Who is online
Users browsing this forum: False Mirror, Sogou [Spider] and 9 guests