I was wondering about a few things when patching in Axoloti, regarding best practice. I am not concluding anything here just asking a few question, cause I want to make sure I understand it correctly, so I can do the right things to optimize my patching.
Objects are classes?
Is my understanding right that when I create a new object I basically create a new class?
Reusing same object/classes reuses the code and saves memory/DSP?
How does the patcher differentiate objects?
II have to identical objects, but they are embedded. In this case does the patcher regards them as separate objects/classes, since they are embedded?
I use a NOT embedded object and loads the same exact object with same sha etc. 2 times.
Are there any difference in DSP/memory use in the 2 cases, embedded/not embedded?
I started to think about it, cause I am making an object where I need 4 of the same objects, but they all need a different offset. I could simply just make the offset as a variable, so you can set it manually. this will use the same object X times. But I thought about making the offsets inside the objects and instead save 4 different, separate objects.......
Which lead me to the question > When they are regarded as separate objects, being embedded, with their own ID, do Axoloti reuse the code cause its the same code?........ or does it reuse the code based on names or ID's?
I am wondering if there is a performance difference in those cases, embedded not embedded? Or if copying the same object with the same ID 4 times uses same memory/DSP same as creating 4 of the same object with 4 different ID's?
So I thought I'd swing it by the experts
Have a nice Sunday