![]() enabling automations only for some MIDI harware inputs and for some MIDI msg types => It's smarter/more efficient than using fake midi ports like MIDI Yoke (better timing, no extra MIDI hardware inputs/outputs needed). => Adding MIDItoReaControlPath VST on a track allows you processing incoming/recorded/routed/generated MIDI events and automation as one and the same. ![]() ![]() If you want CC data on a track, you have to record MIDI CC. If you want automation, you have to record automation. You can't yet record CC as MIDI data on a track, then assign that recorded data as if it were an automation envelope, and you can't convert recorded CC to automation or vice versa. Reaper currently has independent signal paths for control-CC-that-becomes-automation, and CC-that-gets-recorded-as-track-input. I think you are suffering from a common confusion of people coming to Reaper from other DAWs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |