Joe Kaplan

I recently wrote a standalone C++ app using some other SDKs and I would like bring some of that functionality into Max using Min.

I got my environment set up. I double, triple, quadruple checked properties to make sure all the appropriate includes and linker settings are there. I write my first function, copied verbatim from the other app. I would like that function to run when the object receives a bang. The code compiles with no errors. Good.

But when I launch max, and send the object a bang, the function fails and returns a memory allocation error.

I'm wondering how to handle this. I'm taking a function that works just fine on it's own, and embedding it into a Min project that also works fine on it's own. But for some reason the external function does not want to run from inside Min. This issue is not linker/include errors since the project builds just fine and I can browse to the definitions of all of my components from within the project.

One of the advantages of Min, I understand, is that it

 So I'm not sure why I'm running into issues here. I was hoping that anything I could run in C++ I could run inside a Min-devkit package.

Is it possible that code that runs just fine on it's own would be incompatible with Min?

If so, would I have better luck with Max SDK?

Max SDK looks like it has a significant learnign curve, and I'm reluctant to make that investment if what I'm trying to do 

Any input would be much appreciated. Thanks!

I got my environment set up.  I double, triple, quadruple checked properties to make sure all the appropriate includes and linker settings are there.  I write my first function, copied verbatim from the other app.   I would like that function to run when the object receives a bang.  The code compiles with no errors.  Good.

But when I launch max, and send the object a bang, the function fails and returns a memory allocation error.  

I'm wondering how to handle this.  I'm taking a function that works just fine on it's own, and embedding it into a Min project that also works fine on it's own.  But for some reason the external function does not want to run from inside Min.  This issue is not linker/include errors since the project builds just fine and I can browse to the definitions of all of my components from within the project.

One of the advantages of Min, I understand,  is that it "fully embraces modern C++."  So I'm not sure why I'm running into issues here.  I was hoping that anything I could run in C++ I could run inside a Min-devkit package.

Is it possible that code that runs just fine on it's own would be incompatible with Min?
If so, would I have better luck with Max SDK?  

Max SDK looks like it has a significant learnign curve, and I'm reluctant to make that investment if what I'm trying to do should work in Min.

Any input would be much appreciated.  Thanks!

I recently wrote a standalone C++ app using some other SDKs and I would like bring some of that functionality into Max using Min.
I got my e

min-gives-memory-allocation-error-on-a-function-that-runs-fine-elsewhere-combability-issues

There are two directions to go in to start getting to the bottom of this.

1. start with a dummy project, just something that says hello on a bang. Gradually start to bring in the SDKs that you are using. Don't add functionality, just start linking to other libraries / frameworks. After that, start adding in the actual functionality of your code base. Do this gradually and wait until you hit against a problem.

2. Use your IDEs debug tools to latch on to Max and start sprinkling a couple of breakpoints in areas you think there is a failure. You can then start to narrow down where the fault actually takes place. Keep an eye on variables to see if anything is null when it shouldn't be or for any bad memory access.

There are two directions to go in to start getting to the bottom of this.

1. start with a dummy project, just something that says hello on a bang. Gradually start to bring in the SDKs that you are using. Don't add functionality, just start linking to other libraries / frameworks. After that, start adding in the actual functionality of your code base. Do this gradually and wait until you hit against a problem.

On a side note, you can use 'modern C++' with the MaxSDK, you just need to have a bridging step to interface with your C++ in C.

I made a Max SDK project template a little while ago to help take the sting out the learning curve and also show how to do the C / C++ bridging.

https://github.com/Edinburgh-College-of-Art/maxmsp-external-template

The template contains a Visual Studio solution and Xcode project so you can just clone directly should that be helpful.

On a side note, you can use 'modern C++' with the MaxSDK, you just need to have a bridging step to interface with your C++ in C.

I made a Max SDK project template a little while ago to help take the sting out the learning curve and also show how to do the C / C++ bridging.

https://github.com/Edinburgh-College-of-Art/maxmsp-external-template 

While there is nothing preventing you from using this, I would recommend for new projects to use the latest updated max-sdk and cmake scripts from 

. This will ensure your projects can support Apple silicon and have up to date library files. You can find details about this update here: 

https://github.com/Cycling74/max-sdk/blob/main/README-8.2-update.md

We will be providing release versions of this update once Max 8.2 is out of beta, but for now you should simply grab the tip of master. Same for min-devkit / min-api.

While there is nothing preventing you from using this, I would recommend for new projects to use the latest updated max-sdk and cmake scripts from our github. This will ensure your projects can support Apple silicon and have up to date library files. You can find details about this update here: https://github.com/Cycling74/max-sdk/blob/main/README-8.2-update.md 

This shows how little attention I'm paying

@Joe Kaplan, ignore what I said, look at the README above.

https://github.com/Cycling74/max-sdk-base/

I was hoping there would be a lightweight version of the SDK to sub-module, so good to know I can use this in the future.

This shows how little attention I'm paying

@Joe Kaplan, ignore what I said, look at the README above.

@Rob Ramirez: This is new 

https://github.com/Cycling74/max-sdk-base/ 

@MHAMILT: I have been working along those lines. I've identified just one function that is breaking. And I see that the break is happening deep in some VS file. It looks like the issue is neither within Min, nor within my other SDK, but arising from the combination of the two. I'm hoping to find a way to use Min for this project, as I'm am definitely attracted to its simplicity. But I will take a look at Max SDK if I have to.

@Rob Ramirez: I'm a little confused. Are you replying just to MHAMILT or also to me? Should I take your post as a clear suggestion to abandon Min and just start working with Max SDK?

@MHAMILT:  I have been working along those lines.  I've identified just one function that is breaking.  And I see that the break is happening deep in some VS file.  It looks like the issue is neither within Min, nor within my other SDK, but arising from the combination of the two.  I'm hoping to find a way to use Min for this project, as I'm am definitely attracted to its simplicity.  But I will take a  look at Max SDK if I have to.

@Rob Ramirez:  I'm a little confused.  Are you replying just to MHAMILT or also to me?  Should I take your post as a clear suggestion to abandon Min and just start working with Max SDK?

i was responding to the project template link. but whether you are using max-sdk or min you should be able to achieve what you want, and MHAMILT's first post is sound advice. in either case I would recommend starting from the latest source from our github for development, especially for new projects (maybe you already are in the case of min)

Thanks for clarifying. I will keep at this. Hopefully I'll find a way though.

Thanks for clarifying.  I will keep at this.  Hopefully I'll find a way though.

Min gives memory allocation error on a function that runs fine elsewhere ... combability issues?