Accessing Dynamics automation recorded via ModWheel in Ableton

Follow

Comments

10 comments

  • Paul Helfrich

    This was helpful, it shows how to access the midi CC data, but still doesn't fully explain to someone new to Abelton Live 10.x trying to figure out how to record midi CC data over existing midi tracks (as shown repeatedly by folks like Paul Thompson and Christian Henson who use ProLogic in their YouTube videos explaining the BBC Orchestra library) without deleting the midi track. There's got to be a simple way to do that? Please add that info to this entry.

    My research has gotten me frustratingly close, but still no solution. It may involve "custom Control Surface scripts" (which aren't too difficult to write and place in the proper folders), along with the "Max For Live" add-on (Max Midi Effects - Expression) and Abelton automation functions. Thanks!

     

    P.S. I'm a new BBC Core user who loves working with this library!

     

    1
    Comment actions Permalink
  • Aaron Cupples

    Hey Paul, I came here with the same question, and I think I've just solved it. Go to Ableton Preferences> MIDI> and enable 'Remote' on the Input of your keyboard. Then you can map the mod wheel to the 'Dynamics' function of the BBC plug using Ableton's MIDI map feature. Then the dynamic automation will appear on the page with the rest of your automation, in addition, it will no longer appear in the Modulation parameter of the clip it's self (where it used to show up with the default functionality). Hope this helps.

    0
    Comment actions Permalink
  • Paul Helfrich

    Thanks for the input Aaron! However, I'm still not clear on how to do what you suggest step-by-step.

    For example, when I go to Preferences > Link Midi > Midi: where do I find "remote"? Under Control Surfaces? "Remote" doesn't appear as a choice under Input or Output. Under Control Surfaces there is a "RemoteSL" and "RemoteSL Classic". Is that what you're suggesting?

    Again, we want to be able to edit/record CC data in a separate track/clip without erasing any Midi notes on the clip.

    This thread would really benefit from additional explicit step-by-step directions on how to set the routing choices, as well, between the two tracks/clips to show how this works once this "remote" setting is cleared up. For example, how does one "map the mod wheel to the 'Dynmamics' funtion of the BBC plugin using Abelton's MIDI map feature"?

    Thanks!

     

    0
    Comment actions Permalink
  • Aaron Cupples

    Hi Paul, I agree it is confusing and that Spitfire could make this a lot clearer.

    To answer your question:

    This is where you select remote - on the same row that your MIDI keyboard is listed

    Then click the MIDI button in the top left to enter MIDI map mode

    You have to have the plugin expanded with the top left arrow first, then you can see all the controls you can map, click the Dynamics one and then wiggle your mod wheel, this should automatically map the mod wheel to the Dynamics function.

    Then you can click out of MIDI map mode and try recording, your automation should appear on the page like other automation

     

    Hope this helps!

    0
    Comment actions Permalink
  • Paul Helfrich

    Many thanks Aaron, very helfpul! One other little detail needs to be pointed out to Abelton beginners (I've been using midi sequencers since Jim Miller's Personal Composer for PC circa 1985!): you need to toggle the "automation" button:

    Here's a close up:

    I'm still experimenting, but you can see in the first image that I set up a second MIDI track to just record automation, don't know if it's redundant. Anyway, this should now provide enough information for someone to write up a more concise set of Abelton Live 10.x instructions for Spitfire users!

    Thanks again!

    0
    Comment actions Permalink
  • Paul Helfrich

    P.S. Here's what my Preferences > Link Midi > Midi Ports settings are now:

    0
    Comment actions Permalink
  • Aaron Cupples

    Hi Paul, on further experimentation this set-up is not a great solution as mapping the modulation to the dynamics function will only work for that specific instance of the plugin. So if you have further BBCSO instances (which is the most common setup for an orchestral plugin) then you need to keep remapping the modulation for each time you change recording channels. Not a great workflow and this kills it for me. I'll report back here if I make any breakthroughs with this!

    0
    Comment actions Permalink
  • Nicol Demaria

    Hi Paul and Aaron, thanks for your conversation. I'm trying to figure out how to use the midi control of expression and dynamic for BBC Orchestra plug-in in the best way. 

    I'm able to record and edit both the automations with my midi controller (Touch OSC on iPad), but the problem is that I need to map the midi CC everytime I change the instrument of the BBC plug-in. For instance, firstly I map the Violin expression and dynamic and I record the track with automations. Then I need to record cellos, but before I have to cancel the midi mapping on violin's track and mapping again for cellos. It is a bit frustrating. I've seen on YouTube some user controlling the automations of BBS plug-in without re-mapping every time the controls. 

    Do you know if there is a way to do it, arming automation only for track which are armed?
    Thans for helping

    0
    Comment actions Permalink
  • Paul Helfrich

    Hi Nicol,

    This likely relates to Aaron's last comment about "workflow" challenges. I'm still new to Abelton but a long time DAW/Midi Sequenccing/Recording Software user, so take my comments with a grain of salt.

    I am using the BBC Core Template for Abelton. I went into each instrument and set up the CC config to map to a Korg nanoKontrol2 for each instrument. Since each instrument is now set to a particular track, I won't use the multiple clip function per track at all, just one instrument per track to get around this. This way, the CC mapping stays fixed per track.

    Abelton is extremely versatile, something I love about it, so many ways to route signals. I would love one of the SpitFire outreach mavens to focus on a short series of Abelton tutorials to address this very issue because it unlocks the expressive power of their libraries (and helps to sell them! ;-).

    Hope this helps.

    Paul

     

     

    0
    Comment actions Permalink
  • Nicol Demaria

    Thanks Paul for your help!!

    I think I'll going to set up CC mapping for singular tracks. 

    I agree with the fact that Spitfire Audio should make some tutorial about map settings. It would help lot of users.

    Thanks again for your help..

    Nicolò 

    0
    Comment actions Permalink

Please sign in to leave a comment.