Midi Filtering on a per State basis?

Cantabile
1

I have a single rack of roughly 10 vst plugins with two keybeds, a 73 key and a 61 key. I prefer to call up a song and have only one state per song where I map to sounds needed across the two keyboards via midi mapping, transposing (when needed), assigning and/or filtering cc’s for two foot switches and two foot controllers.
I understand that midi filtering is not state specific but route specific. This can get quite messy in the rack with many routes containing filters for specific states/songs to any of the plugins.

Is there a much cleaner method for midi mapping, transposing, assigning and/or filtering cc’s for two foot switches and two foot controllers on a per state basis?

2

Hi danski,

In my opinion the issue is that you placed the routings inside the rack. It may be to much work to change but it would be cleaner if the routing was at song level and the rack with the VSTis was broken into separate linked ranks so you had a more modular setup. That way the routing for each song would be all you saw. Sorry there isn’t a fix there for your current method but I thought it would be right to point it out. One other thought (if you kept the current rack) would be to create separate input ports for the rack that fed each VST directly and still have the routing at song level.

Dave

3

Thank you Dave for pointing out what I was doing wrong. I’ve been a hardcore Brainspawn Forte user for years but I need to move away from it asap. Tired of working around the bugs and need MIDI out of the host support.

I have a common rack file with each of the 10 VST’s having its own FX rack. I have not committed too far into setting up songs until I can prove the common rack concept will work for me. The common rack idea is because of my usage for so long of Brainspawn Forte common rack system.

Like what you were stating I was trying to create each song as a song part (state) for the common rack. When I changed that mindset to One State/One Song and setup a setlist of two songs (with preload) everything works the way I had envisioned.

Now, the one thing I’m hearing is a pop or click when changing songs…

4

That will occur if there are any reverb or note tails that haven’t played out before you switch songs. That is because cantabile cuts off audio when changing songs. This has been a subject of discussion for a long time here.

5

I’m not even playing anything when it pops. I’m just clicking the radio buttons. It’s very noticable but not obnoxious.

Is there a way to mute the audio output when the radio buttons are clicked prior to the actual change in the rack?

6

Apologies, I misunderstood. Which exact buttons are you referring to?

7

The radio buttons for each of the songs in the setlist.