1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

How can I get smooth midi CC automation in Reaper ?

Discussion in 'Your DAW (Digital Audio Workstation)' started by Lim, Jul 15, 2016.

  1. James Marshall

    James Marshall Senior Member

    106
    114
    Apr 26, 2017
    UK
    Excellent! Can confirm that works for me too.

    Thanks so much for looking into that and for your time, it's a great little plugin :thumbsup:
     
  2. pbattersby

    pbattersby Senior Member

    66
    28
    Jul 6, 2016
    I'm curious. How is it that CCenv_(CC0-CC63).jsfx, is able to properly record CC01, but ReaControlMIDI can't? What is the magic that enables this to work when it fails for me with ReaControlMIDI? In both cases I'm using CCenv_input.jsfx as an input FX, and I have record mode set to "Latch."
     
    Last edited: Apr 13, 2018
  3. pmcrockett

    pmcrockett Senior Member

    328
    184
    Nov 3, 2014
    Saint Louis
    I've not personally used ReaControlMIDI to record CC envelopes, but my understanding is that because it can't stop the CC events from being recorded and/or passing through it, you end up with the both the MIDI data and the envelope recorded unless you use something else to filter the data as well. My impression is that it's not really designed for people who want to replace CC events with envelopes as part of a permanent workflow modification.

    CCEnv works by reading the CC values at input (in CCEnv Input), blocking the CCs you've selected so they won't record as MIDI on the track, and instead sending that CC data directly to CCEnv (CC0-CC63) and CCEnv (CC64-CC127) which convert the CCs to slider motion that can be recorded. CCEnv (CC0-CC63) and CCEnv (CC64-CC127) then pass the CC data equivalent of the slider motion on down the chain to the instrument. If there were no input component to the plugin, the MIDI track couldn't be bypassed while recording, and if there were no output component, there would be no way to read the envelopes during playback, but having both an input and an output component allows us to skip the MIDI track entirely for both recording and playback.

    I just checked, and it's actually possible to use CCEnv Input to filter out a CC by checkingboxing it and then use ReaControlMIDI's learn feature to link that CC to its automatable CC parameter which lets you record the automation with the CC input without recording the MIDI data on the track -- so you end up in pretty much the same place as if you use CCEnv (CC0-CC63) and CCEnv (CC64-CC127), just with fewer available CCs and more setup required.
     
  4. pbattersby

    pbattersby Senior Member

    66
    28
    Jul 6, 2016
    By "checkboxing it" do you mean enabling it?

    I've only just started playing with CCEnv but it seems to solve the problem (recording smooth MIDI automation) so thanks for your work on this.

    The CCEnv scripts seem to work well, so I'll probably stick with it rather than continuing to struggle with ReaControlMIDI since I'm just not making any progress with getting it to recognize (learn) the MOD wheel and behave as well as CCEnv.

    Will you eventually upload CCEnv to the Reaper Reapack repository or some external location? So far it seems it's only available to members of this forum as an attachment to this thread.
     
  5. pmcrockett

    pmcrockett Senior Member

    328
    184
    Nov 3, 2014
    Saint Louis
    Yes, by checkboxing I mean enabling.

    If ReaControlMIDI isn't seeing the mod wheel as a learn source, you may need to change your MIDI controller's mode in the MIDI devices section of the preferences. You can set input devices as enable input and/or enable input for control messages by right clicking on them. Both can be selected at the same time for any device, and enable input for control messages allows Reaper to see the device as a learn source.

    As far as distribution goes, I'll probably at least put it up in the Reaper forum thread where the script originated and maybe look into Reapack. It hadn't occurred to me that putting it as a message board attachment restricted it to forum members, so in the meantime, I'll maybe find a spot to upload it that's generally accessible.
     
  6. robgb

    robgb I Have Strong Opinions

    1,430
    1,117
    Apr 6, 2016
    Yes, that's more than possible. But I'll try the work arounds and see what happens.
     
  7. robgb

    robgb I Have Strong Opinions

    1,430
    1,117
    Apr 6, 2016
    Both workarounds seem to work. I'm wondering if there's a way to "embed" certain CC values into a track template without adding a midi item (not that this is a bad thing).
     
  8. robgb

    robgb I Have Strong Opinions

    1,430
    1,117
    Apr 6, 2016
    I've found another workaround (I think). In Kontakt I used the factory multiscript Transformer to send CC7 and CC10 to unused values (100, 101) so that they don't affect the instruments in any way. Obviously, if you do this you have to make sure your instruments don't use those new values for anything. But so far it seems to work. I tried hammering the track with CC7 and it made no difference.

    The problem I had with adding a CC7 command to the track was that it set all the instrument values to the same volume, and destroyed the volume balance I had worked out for that multi.
     
  9. EvilDragon

    EvilDragon KSP Wizard

    4,174
    2,068
    May 25, 2010
    Croatia
    Not that I know. Best have an item in the template.
     
    robgb likes this.

Share This Page