problem with matrix~

something must be wrong with your routing - i'm not going to go though the whole patch though - there are lots of connections! Dunno why ramping would not work, unless there is a bug with matrix~ when it is that big.

But i have some suggestions for you to make life easier:
1. use presentation mode! this will let you put you patch in logical signal flow order when patching and have it rearranged for the final UI. Patching is much easier.
2. you seem to have a bunch of nearly identical bpatchers that are actually loading different max patches that appear to be the same or very similar. I would simply load a single patch into many bpatchers and take care of any differences with arguments to the bpatcher or messages to inlets of the bpatchers. That way the if you modify what is in the bpatcher, it auto-updates for all of them, and the patch probably loads faster too.
3. unless you are making feedback loops, you can use regular s and r objects instead of send~ and receive~ for sending audio around. send~ and receive~ actually introduce a 1 signal vector (or is it one i/o vector?) delay in the audio stream so you can do feedback systems, so in normal use, you actually don't want to use them if latency is important. However, you'd have to think about that, because if your patch allows something to be routed back into itself with the matrix~, you probably want to use send~ and receive~ somewhere.