I am trying to get automation of the main faders A & B to work in Reason. I attached a screenshot of the GUI and marked the faders with a red circle.
In Reason 10 I cannot get a working automation lane for these two faders. If I click on the "Autom."-button and then on one of these faders no automation lane pops up in the sequencer. I can assign a remote-fader on my Midi-Keyboard to the A&B-fadersand they are moving in the plugin when I move the knob on my keyboard. But when I try to record faders on my midi keyboard again there is no automation lane coming up. Finally I tried adding an automation lane manually, but it seems to be not possible.
Do any of you have the Movement plugin by Output and could try? I would really appreciate it, because I like the plugin a lot but without automation it lacks some magic .
Btw in the demo of Reason 11 the behavior changes. Reason seems to hang up when I click on the Remote or the Autom. button of the plugin. It's running in the background but it is impossible to interact with Reason anymore. Maybe it is simply not meant to be ...
Cheers Flo
Reason and Output Movement
-
- Posts: 193
- Joined: 31 Jul 2019
Deleted
Last edited by DougalDarkly on 09 Jan 2020, edited 1 time in total.
- adfielding
- Posts: 959
- Joined: 19 May 2015
- Contact:
Yep, this works and is exactly what I've done. Here's the patch I use, maybe it'll be of some useDougalDarkly wrote: ↑28 Sep 2019Sorry, I don't have the Movement plugin, but this has come up with a couple of other VSTs - what I did then was to stick the VST in a Combinator, map a rotary to the parameter I need (if it comes up in the Combi's programmer) and then automate the rotary in the combi's sequencer lane.
Apologies in advance if this is of no help to you!
- Attachments
-
- Movement.zip
- (6.08 KiB) Downloaded 51 times
-
- Information
-
Who is online
Users browsing this forum: No registered users and 15 guests