Hello everyone. I'm rewriting an external for the RTcmix audio language. I have built RTcmix as a static lib and compiled it into my external, accessing the functions from RTcmix through its API in the code for my external.
I have it up and running, but if I create multiple instances of the external in the same patch, they interfere with one another, garbling the audio and corrupting the memory.
Any ideas on fixing this? I had assumed that linking against a static library meant that there would be no shared namespace.
Thanks! Joel
Joel --
I have the answer for you (and it's not pretty). Will send in separate e-mail.
Unless anyone knows how to load a dylib and keep the name/data-space 'private' under Windows.
brad
On Mon, Jun 12, 2017 at 1:59 AM, Joel Matthys jwmatthys@gmail.com wrote:
Hello everyone. I'm rewriting an external for the RTcmix audio language. I have built RTcmix as a static lib and compiled it into my external, accessing the functions from RTcmix through its API in the code for my external.
I have it up and running, but if I create multiple instances of the external in the same patch, they interfere with one another, garbling the audio and corrupting the memory.
Any ideas on fixing this? I had assumed that linking against a static library meant that there would be no shared namespace.
Thanks! Joel
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list