jeffburger

I have a LOT of instances of a given bpatcher in use throughout a patch and various subpatchers. It seems that each instance must pull from disk all over again instead of loading once and then knowing to instantiate from the copy already in memory. In this large patch, that translates to an unacceptably long load time. I know I can embed the bpatcher, but that leaves me with a whole lot of instances to go hunting for and updating if I even need to make changes to the bpatcher.

Am I missing something (short of using a solid state drive or making a RAM disk)? Is there a way to tell a bpatcher to continue instantiating from an already-loaded instance instead of disk for the sake of efficiency?

Haven't tried it yet, but I'm thinking the same concern also applies to poly~?

I have a LOT of instances of a given bpatcher in use throughout a patch and various subpatchers. It seems that each instance must pull from disk all over again instead of loading once and then knowing to instantiate from the copy already in memory. In this large patch, that translates to an unacceptably long load time. I know I can embed the bpatcher, but that leaves me with a whole lot of instances to go hunting for and updating if I even need to make changes to the bpatcher. 

Instantiate iterations of bpatcher and poly~ from RAM?