Max objects missing?

Usage Questions
1

I tried running this patch from the thread here:

After downloading the FluCoMa objects from:

I am still missing the following:

newobj: fluid.kdtree~: No such object
newobj: fluid.dataset~: No such object
newobj: fluid.normalize~: No such object
newobj: fluid.umap~: No such object

I don’t see these in the externals folder of the download. Where do I find these externals?

2

Hi @jthompson

Those objects are all compiled into a single binary so they can talk to each other easily (it’s called. fluid.libmanipulation.mxo in Max; we do the same in SC). You possibly will need to restart Max after installing so that the init file Max relies on to map object names to this file has been consumed and run.

If you’ve already done that and / or it still doesn’t work, we can kick its tyres a bit

3

Hi,

User error. I placed the flucoma folder into the search path but not into the Packages folder … which is where it has to go.

Sorry for the noise.
John

1 Like
4

This happens a fair bit so youre not alone :stuck_out_tongue: is there anyway that we can make this clearer? It would be interesting to know where you grabbed the package from so we could plaster the advice directly there for example.

5

Well, it is right there in the “QuickStart.md”, so why did I miss it?

I guess maybe a “readMe.md” or even “readMe_FIRST.md” might have caught my attention a bit better? A readMe on the GitHub page might help.

Who knows what causes users (such as myself) to just start throwing stuff around without taking a moment to read what has been written (mea culpa).

I think eventually just getting this through the package manager is going to solve the problem.

6

You’re right, the package manager would solve all those issues. I think we could flag it on the front page of GitHub better as many people pass by there.

1 Like
7

Hi,

I’m currently trying to build a Max project as a standalone application using FluCoMa.

After consolidating the project and including the necessary externals, I noticed that fluid.mlpregressor~ behaves differently from other objects. Since it appears to be part of a compiled binary (fluid.libmanipulation.mxo), I manually added that file to my project before building the application.

However, when launching the standalone, I get the following error in the Max console:

fluid.mlpregressor~: No such object

And indeed, the object is not available in the built application.

I suspect I might be misunderstanding how FluCoMa packages should be included in a standalone build. Is there a recommended way to properly bundle FluCoMa with a Max standalone so that objects like fluid.mlpregressor~ are correctly recognized?

This object is central to my patch, so I’d really appreciate any guidance.

Thanks a lot for your help,

8

maybe this thread will be of interest: Building a Max Standalone using Flucoma externals - #4 by felipetovarhenao

9

Yes, thank you! The threads helped me resolve this.
All the best.

1 Like