Roth

I'm recently getting back into Max external development (haven't done much since Max 6).

I'm glad to see there is a Cycling '74 GitHub these days—and that 

I was wondering about the purpose of Max-API[1] compared to Max-SDK[2]: I do see that Max-API is used by min-DevKit and friends and tries to be nicer for C++ with adding namespaces (also has 

 ready to go). I'm assuming Max is still built against the headers in the Max-SDK vs the headers in Max-API; is this correct?

Is Max-API supposed to mirror all the same 

 functions but placing them in namespaces? Are there or are there planned API differences? Which set of headers are the future for internal builds of Max (especially as you are moving to Apple Silicon)? Since I'm writing my own C++ wrapper API, I would prefer to use whichever set of headers are the canonical edition.

[1]: https://github.com/Cycling74/max-api

[2]: https://github.com/Cycling74/max-sdk

I'm recently getting back into Max external development (haven't done much since Max 6).

I'm glad to see there is a Cycling '74 GitHub these days—and that mxj has been open-sourced!

I was wondering about the purpose of Max-API[1] compared to Max-SDK[2]: I do see that Max-API is used by min-DevKit and friends and tries to be nicer for C++ with adding namespaces (also has CMakeLists.txt ready to go). I'm assuming Max is still built against the headers in the Max-SDK vs the headers in Max-API; is this correct?

Is Max-API supposed to mirror all the same extern "C" functions but placing them in namespaces? Are there or are there planned API differences? Which set of headers are the future for internal builds of Max (especially as you are moving to Apple Silicon)? Since I'm writing my own C++ wrapper API, I would prefer to use whichever set of headers are the canonical edition.

[1]: https://github.com/Cycling74/max-api
[2]: https://github.com/Cycling74/max-sdk

I'm recently getting back into Max external development (haven't done much since Max 6).

I'm glad to see there is a Cycling '74 GitHub thes

max-sdk-vs-max-api

your assumptions are correct I think. the sdk space remains in flux, but for the most part the max-sdk remains the source of truth and the maxapi is there to support min-devkit projects. use and abuse at your own risk. we hope to clarify the use cases, and possibly simplify things in the future, but have no time frame for that work.

there are minor discrepancies but I wouldn't exactly call them planned. file issues with whatever you come across.

can't comment on future plans for the sdk. we will work to support apple silicon dev once we finalize that support internally.

in this case unless you have concrete needs of min or maxapi then I would stick with the max-sdk. that being said I strongly recommend taking a look at the various components of min before making that decision.

Is Max-API supposed to mirror all the same extern "C" functions but placing them in namespaces? 

Are there or are there planned API differences?

there are minor discrepancies but I wouldn't exactly call them planned. file issues with whatever you come across. 

 Which set of headers are the future for internal builds of Max (especially as you are moving to Apple Silicon)? 

can't comment on future plans for the sdk. we will work to support apple silicon dev once we finalize that support internally. 

Since I'm writing my own C++ wrapper API, I would prefer to use whichever set of headers are the canonical edition.

in this case unless you have concrete needs of min or maxapi then I would stick with the max-sdk. that being said I strongly recommend taking a look at the various components of min before making that decision. 

Max-SDK vs Max-API