I just got performer and I want to refactor my songs to use racks so they are not unloaded between each song. Is it possible to have different midi filter settings per song to the same rack?
I’d like to have the same rack with my Amp sim in it, but be able to adjust the program change filters per song.
i.e. Song 1 filters PC 1 to PC 2, and Song 2 filters PC 4 to PC 1. This way I can control the preset selection in my VST differently per song but keep the benefit of not unloading between songs.
If I understand the query than yes you can do it at the song level input routing. Just select your input slot you wish to adjust and right click for midi filters on each song and make your adjustments.
Yes, each song could have different set of MIDI Filters on the routes feeding the racks, however more typically you’d configure each song (or song part) to explicitly configure the racks as you need them so that you don’t need the mappings to change programs manually.
I don’t plan to use song parts, not sure I need that level of granularity.
I generally configure my preset in Amplitube to have my tone dialed in, and maybe one or two additional optional effects that can be individually turned on or off, like wah-wah or chorus
Maybe I’m missing something, but this lets me use just one instance of the plug. The switching is a little slow, but in context of the full band its not noticeable much.
Are you suggesting that I have multiple instances of my plug with each configured exactly as that section of the song requires? Wouldn’t this still use all the additional memory and overhead of multiple plug-in instances?
If you’re using the one instance across songs, I’m not sure what would be slow here. One way to tell would be to turn on the console logger and watch what it’s doing during the switch.
No, but you should be able to either:
Create multiple states in the rack and have each song select the appropriate state for that song.
Use exported properties from the rack to explicitly control certain settings on the plugin from the parent song.
If you’re not familiar with states and exported properties check out the states video which covers this.
Interesting find. I noticed in amplitube that switching presets cuts the tails off of delays or reverb etc. Quite undesirable.
Last night I tried song states and racks for the first time. I created a rack for each preset in amplitube
and controlled which receive the audio and midi input via states.
I have between 3-6 active amplitube instances per song and the memory usage stays under 1.5gb for the most part.
Switching states allows my reverb and delay tails to continue this way and switching is instantaneous! Turns out this might be the way to go for me after all.
First show tonight using cantabile live, and I’m excited to try it out.
