Copy parameter automation data from Reason into Logic?

[bhuether]

Hi, in Reason I have CC data for a plugin that Reason saves as MIDI data when exporting a MIDI file. In Logic, when I use the Reason plugin directly in Logic, I see the plugin's automatable params under Track automation.  But if in arrange view I copy the imported MIDI CC data I can't paste it into the corresponding Track plugin automation lane. For instance, in the imported MIDI data I have MIDI General CC# 3 that contains data to be used to control cents of the Reason Neptune pitch shift plugin.  So I copy that MIDI data then when I go paste it after I select under track automation data Reason->Neptune cents, it doesn't paste.

Any idea how to do this?

 

thanks,

Brian

[polanoid]

Logic will only paste the copied data unmodified, i.e. if you copied data for CC #n, it will be pasted as exactly that and will not be converted into Logic’s proprietary Fader automation data, regardless of what your automation lane shows.

[David Nahmani]

You can always first copy it then convert it to another parameter? 

[polanoid]

So here's what you do:

1) Find out the Fader number the plug-in parameter you want to automate has (I usually do this by connecting a Monitor object to the Channel Strip in the MIDI Environment and tweak the parameter I want to automate, )

2) Do a MIDI transform on your imported MIDI Region with these parameters (in this example the destination Fader # is 12)

Be aware though that the parameter value range probably doesn't match, so I doubt you will get something useful out of this. Logic can not know how to meaningfully translate a [0...127] CC value range to a plug-in parameter value. You may experiment with scaling Data Byte 2, but you're on your own with that I'm afraid (that said, you can use the above mentioned MIDI monitor to find out the parameter's value range, so transforming the value might not be that difficult)

Edited June 29, 2022 by polanoid

[polanoid]

So here's an example how you would convert CC#3 (full range 0...127) to Logic's Sampler Coarse Tune parameter which ranges from 0...48 (BTW for Fader Events, channel 2 means the destination is the plug-in on the first slot, which is the Instrument slot for software instrument channels. Channel 1 is the channel strips "base plate" with Volume, Pan, Sends etc.):

Edited June 29, 2022 by polanoid

[polanoid]

28 minutes ago, David Nahmani said:

You can always first copy it then convert it to another parameter? 

Be aware though that this will not work for Track Automation as Track Automation will only handle Fader automation data

[polanoid]

BTW if you insist on having the converted automation data as track automation data, you will have to convert it from region automation by either:

1) switching to region automation, selecting the converted parameter, and the option clicking the blue button now showing "Region". This will convert all visible region automation to track automation 

or

2) switching to region automation, selecting the converted parameter, and choose "Mix -> Convert Automation -> Convert Visible Region Automation to Track Automation" 

[bhuether]

Ok, so I got things straightened out.  I used a MIDI Modifier plugin so that the CC data is mapped to the plugin params.  All works fine. Just that the Cents CC data from Reason had all negative cents values set in Logic to 1.  Or maybe the data itself preserved the plus/minus relationship but Logic in importing the MIDI did some sort of truncation. No idea. I ended up manually recreating the negative parts of the curves...

thanks

[polanoid]

15 minutes ago, bhuether said:

Ok, so I got things straightened out.  I used a MIDI Modifier plugin so that the CC data is mapped to the plugin params.  All works fine. Just that the Cents CC data from Reason had all negative cents values set in Logic to 1.  Or maybe the data itself preserved the plus/minus relationship but Logic in importing the MIDI did some sort of truncation. No idea. I ended up manually recreating the negative parts of the curves...

thanks

If the destination parameter has negative values, there must be some offset ("Add" parameter) you need to take care of in the MIDI Modifier. MIDI CCs can not have negative values, they always range from 0 - 127. Logic does not "truncate" anything.

Edited June 29, 2022 by polanoid

[bhuether]

Thanks for the insights - this is definitely an area of Logic that I am not too familiar with!