Page 1 of 1
Separate Automation Clips R12
Posted: 07 Nov 2024
by ShadowMatriks
I am pretty sure, but not certain, it was possible in past versions of Reason to record automation data separately by default. It defaults to note and automation combined, which IMO is not only a PITA but is handled unintelligently/badly.
For example if you record automation data in, the only way to do it is via a new note lane, which leaves you with a blank note clip and the automation data in that useless tiny strip at the bottom of the window. To add insult to injury if try to move the clip to it's parameter lane, Reason says it's alien and won't convert even though it's data for that exact parameter! Furthermore if you attempt to move the clip to another device it won't convert it, even though the data is the same range and type, I mean how ridiculous is that!
Is there a way to get Reason to record automation data separately by default?
Re: Separate Automation Clips R12
Posted: 07 Nov 2024
by jam-s
In the option menu there is an option to select if automation is recorded in note clips:
https://docs.reasonstudios.com/reason13 ... nce#509284
Re: Separate Automation Clips R12
Posted: 08 Nov 2024
by ShadowMatriks
No it doesn't do anything.
That reminds me it was bug report I meant to send to RS years ago but forgot all about/didn't do. Too late now!
Re: Separate Automation Clips R12
Posted: 12 Nov 2024
by agreeblanket
ShadowMatriks wrote: ↑07 Nov 2024
I am pretty sure, but not certain, it was possible in past versions of Reason to record automation data separately by default. It defaults to note and automation combined, which IMO is not only a PITA but is handled unintelligently/badly.
For example if you record automation data in, the only way to do it is via a new note lane, which leaves you with a blank note clip and the automation data in that useless tiny strip at the bottom of the window. To add insult to injury if try to move the clip to it's parameter lane, Reason says it's alien and won't convert even though it's data for that exact parameter! Furthermore if you attempt to move the clip to another device it won't convert it, even though the data is the same range and type, I mean how ridiculous is that!
Is there a way to get Reason to record automation data separately by default?
Automation data is generally recorded along with note data in the same lane, and there isn't a built-in option to change this behavior by default. However, you can manually create separate automation lanes for specific parameters before recording. Unfortunately, moving automation clips between lanes or devices can indeed be frustrating, as Reason's handling of clips can be restrictive.
Re: Separate Automation Clips R12
Posted: 18 Nov 2024
by ShadowMatriks
there isn't a built-in option to change this behavior by default
There is an option in the drop down options menu but it doesn't do what it used to do. It used to work, I just can't remember which update changed it!
Re: Separate Automation Clips R12
Posted: 19 Nov 2024
by MattiasHG
ShadowMatriks wrote: ↑08 Nov 2024
No it doesn't do anything.
That reminds me it was bug report I meant to send to RS years ago but forgot all about/didn't do. Too late now!
It does do something! With "Record Automation into Note Clip" disabled, any recorded parameter automation gets it separate lane. I just tried that locally and it worked, but if that doesn't happen to you there might be a bug so you should report that to us via support.
Note that performance controllers (mod wheel, pitch wheel, aftertouch, breath, expression, sustain) record into the MIDI clip regardless of setting as they're traditionally connected to your MIDI performance. This has been the case in Reason for as long as I can remember. Is that what you're referring to?
Re: Separate Automation Clips R12
Posted: 19 Nov 2024
by ShadowMatriks
Note that performance controllers (mod wheel, pitch wheel, aftertouch, breath, expression, sustain) record into the MIDI clip regardless of setting as they're traditionally connected to your MIDI performance. This has been the case in Reason for as long as I can remember. Is that what you're referring to?
Yes it looks like it's the problem I'm coming up against. I did wonder why I could do it with some devices and not others!
In terms of a keyboard performance I can see the logic now you have spelt it out. It is mostly Dr Octorex and the Combinator where I have assigned things to the mod wheel and I am doing pitch bends for individual drum slices/chops in conjunction with other FX automation, comb filter sweeps, slice reverse, repeats, tape stops that have to be precise to grid/sample playback and have unpredictable sweet spots due to multiple things going on at once.
Re: Separate Automation Clips R12
Posted: 20 Nov 2024
by nadj
MattiasHG wrote: ↑19 Nov 2024
Note that performance controllers (mod wheel, pitch wheel, aftertouch, breath, expression, sustain) record into the MIDI clip regardless of setting as they're traditionally connected to your MIDI performance. This has been the case in Reason for as long as I can remember. Is that what you're referring to?
I would really like the option to record performance data seperately like all other automation, especially the pitch and mod wheels as I most often use these for more than performance flourishes. Maybe a seperate preference: "Record performance data to clip? Y/N".
Re: Separate Automation Clips R12
Posted: 20 Nov 2024
by RobBarnett
+1