Create new automation envelope with each take?

Trying again 

Not sure I can make that work 

Confirmed, that is indeed the plugin, MIDI CC Mapper. Also, the activity meter for the track is not showing anything that I can discern when it happens. But it does immediately flip both source and target back to CC 1 when track is armed. Just to be clear, it's added as an input FX. I need it to work live, so that the wah is immediately affected. I will look into your link tomorrow if I can find the time, or if not, wednesday. Thanks. :-)

No dice? 

Greetings Mufkatar, and welcome to Reaper! You probably have "Record: MIDI overdub or Replace" selected for the track input. You won't get separate takes with that setting. To do what you want - MIDI recording multiple takes - do this: - Set the track input to: "Record: input (audio or MIDI)" Loop away! You won't see the multiple takes until you stop recording. When you do stop, it will be just like recording audio, Reaper will ask if you want to save what you have just recorded. Click yes... You might have to make the track taller to see the multiple takes. It works for MIDI notes, and for CCs. I would record the MIDI in a separate track, not in the same track with the audio. You will have to change takes in both track... a bit of a hassle, but doable. It's probably possible to have a script the selects takes in all selected tracks. Good luck!

Mufkatar - you're very close. in your screenshot, you found the right window, but it looks like you missed the part about the MIDI hardware output. open that up again for track 9 and look at the upper right hand corner of the window. that's the send you'll want to create to send MIDI from the track to the Guitarport (which, i assume, you've set up as a MIDI output option in preferences).

here's an image where MIDI hardware output is hilighted. this is where you need to find your Guitarport right now, you're sending MIDI to an audio track that isn't connected via MIDI to your guitarport at all.

Thanks again, mccrabney, but I'm still not all the way there. Yes, I had in fact noticed that setting (MIDI Hardware output), but the thing is, I suspect I really do need to send it to the track (and thus the plugin), not the hardware as such? Of course I may be wrong about that. Thing is, I could have sworn that I'd already tried your suggestion prior to my previous post, to no avail (perhaps it was a matter of not having selected the tracks), but tried again and it did work now. Sorta. Because it only affects the wah knob during recording. When playing back the take, the wah knob no longer moves at all. Checking the MIDI track, it does in fact have MIDI data with the correct CC#4 and channel 1. So why does it only work "live" and not during playback?? Any ideas? :-) My only guess right now is that MIDI data sent to the Guitarport hardware affects it in the moment, but when playing back, it is the VST plugin version of it that is processing the recording, and because the plugin isn't getting the MIDI data, it doesn't respond. Something like that.

guitarport is both a VSTi and a hardware unit? maybe post your project for us to look at

Thanks for the input, Andy, and yeah, mccrabney, my bad - I guess I should have made that clear from the get-go. I've tinkered some more, and leveled up my understanding a bit - so here's where I'm at now: My Guitarport unit is a USB audio interface with DSP processing, which can be configured via a Windows application - and also comes with a VST plugin. What I CAN do: Use the Reaper CCMapper plugin to remap my MIDI expression pedal to send the proper CC#4 messages, and route that channel's output to the Guitarport hardware, it listens on MIDI channel 1. This affects the Windows application as it should, the wah control follows the pedal movements. BUT - this does not affect the Guitarport VST plugin at all. Even if I change the routing of the channel to a send instead, pointing it to the audio track containing the Guitarport VST does nothing. Another angle of attack: I CAN use Reaper's "Learn" function on the Guitarport VST plugin (via the "Param" button in the FX window) to teach it to respond to my pedal (pedal natively sends CC#11). This makes the wah control move in the plugin as it should. BUT - for some reason, the wah control will ONLY respond to live movements of the pedal. Routing MIDI CC#11 (or for that matter, CC#4) data to the track does absolutely nothing. SO - my questions now become: * Why would Reaper's "Learn" function only ever respond to live signals, and not playback? Is there some way to disable this odd limitation? * Provided that this is impossible, I would like to understand why the Guitarport plugin does not respond to routed CC#4 data (with "Learn" disabled). The plugin clearly states that CC#4 controls wah, so I'm wondering if I've not configured the track to properly "listen" to MIDI - perhaps simply routing the data to the track is not enough? "Input" is set to "Input: stereo" (ie. audio) after all, not MIDI. Although I've tried switching it to MIDI during playback just to test, and no joy there either. Perhaps it's some automation/envelope setting I must tweak to let the MIDI data through to the VST? It kills me that "Learn" allows the knob to be controlled, but that I can't find the "natural" route to control the knob without "Learn" - it must be possible, somehow? Unless you can illuminate me on any of these two questions, I guess I'm left to conclude that this is an ancient plugin by now and may not ever work with Reaper the way I want it to. For now, the only way I can get that wah knob to move is using the Reaper "Learn", which doesn't work with playback data. And in that case, my choices are probably either to record the processed output (which should also capture the wah effect in the audio) and thus severely limit my options as regards tweaking the tone in post etc., or to buy a new guitar DSP system, either hardware or software based. I'd like to hear from you (all of you), even if just to say you're just as stumped as I am. :-) And thanks for sticking with me this far.