just starting with external dev.
I have created a max external which loads fine. However, when I rebuild it with a slight change, it just keeps loading the older version of the external that I built previously. It’s only when I quit and restart max that it finds the new one.
This happens when destroying the object and creating a new one / retyping the object name etc. after rebuilding.
Is this normal? Is there a way around it?
I’m no expert at this but I think you can set the Runtime version of Max as the executable (extra bonus, you can now debug as well).
There is some info in this post:
I seem to remember an article a while ago on how to set it up step, by step. I’m sure if you do a search it will show up.
OK, thanks. I’ll try it and report back.
There is no way with a C-based external to reload without rebooting Max.
The scenario is different for java externals, which can be altered without the need to reboot, but you may prefer to develop in C for a variety of reasons.
I can’t believe it! It must be pretty inconvenient to develop externals in C. Is there no way to implement this – even in the future?
Really? It’s too much of a pain to have to reload max every time.
I am one of those who prefer to develop in C for a variety of reasons.
C74 RSS Feed | © Copyright Cycling '74