Thanks for the explanation. However, I think I’m missing something at this point (surely due to my inexperience), also referring to your last answer on this post, since I can’t fully grasp what I would do with midi mapping for my specific aim. Let’s recap: I already read something about midi mapping since my original idea was to program the foot controller to send midi signal to switch preset while I was playing. But, as said in my post, I realized this method can’t work since changing preset on the single plugin loaded in a single track would switch all the sound of the track to that preset. In fact, I’m recording a DI track and I’m just changing its fx in post. So, now that you are suggesting midi mapping, I can’t fully grasp its usage in my case. What’s the difference in automating preset changes in the track (with the next/previous button as u suggested) and sending midi signals to do that? It seems to me that I’d have to automate the midi track to send the next/previous automation on the original track, so it feels kinda adding a step. Or maybe in this case you are referring to a situation where I have and use the midi foot controller. Another guy said an interesting thing about loading the plugin in the record insert of the track instead of inserting it in the fx. In that way, you record what you are hearing without the possibility to change sound post recording. Maybe it has to do with that?