I not only experience the slowdown in that situation, but often even memory corruption or something: nonsense error messages such as ".x8972383 no such object" (or something like that: can't remember exactly), and sometimes some patch windows is closed that shouldn't be. Often the MAIN patch window is closed, i.e. disappears, so when I close any other open window, there's no open window left; then I quit PD and magically the main patch appears again, and it asks me whether to discard changes!!! (so I say "no" and that's the only way to have the patch appear again without quitting pd).
All this happens when saving an abstraction which is used multiple times in an open patch... and in my case it's not hundreds of times but just tens of times.
Yes, I've had that as well. The thing to do in this situation is to make sure that all the abstractions or subpatches inside the one you are saving are closed. Having to refresh these open subpatches or sub-abstractions along with the main abstraction exponentially increases the load on PD, and also leads to the "no such object" message.
Otherwise, think about converting some of the abstractions to subpatches instead...
best, d.
matteo sisti sette wrote:
Quoting matteo sisti sette matteosistisette@gmail.com:
this is definitely not a "nonsense message".
it tells us that there is a corruption in the communication between pd
and pd-gui (out of sync) and/or a buggy gui-object.
i admit that the error is a bit cryptic (similar to the famous "an
error #87 occured" within the bluescreen), but it is not "nonsense".
fgnmasd.r IOhannes
This message was sent using IMP, the Internet Messaging Program.