Alexis Baskind

I am sharing a max project between max and windows and facing an annoying issue: after saving the project and patches in windows, the patches contain a reference to several mxe64 externals in the "dependency_cache" section. Those are called by the project when it's opened again.

Now when I open the same project in Mac, it still refers to the mxe64 externals (in section "other"), which has the effect to hide the reference to the correct Mac externals (mxo) when I open the patches.

Until know, the only solution I found is to open every patch as a text file and clear the reference "dependency_cache". As I have more than 30 patches in my project, and as I have to switch constantly between windows and mac, this is somehow a pain.

Is there a more elegant solution, like automatically clearing all the dependency caches of all patches of a project, or not taking the dependency cache in account when opening a project?

Dear all,
I am sharing a max project between max and windows and facing an annoying issue: after saving the project and patches in windows, 

clear-dependency-cache-for-max-projects

I can't seem to repro. Could you send an email to support at cycling 74 dot com with an example Project so that we can try and reproduce here?

You can also try and 'consolidate' the Project by going to the Project window's lower toolbar, and click on Manage Project->Consolidate.

This is an issue, especially when developing max objects. A external is copied into the cache and referenced from there. If you create a new frozen amxd, it can happen that it still uses the old version of your external. So far the only solutions are afaik:

- use the developer path only and don't freeze

This is an issue, especially when developing max objects. A external is copied into the cache and referenced  from there. If you create a new frozen amxd, it can happen that it still uses the old version of your external. So far the only solutions are afaik:

Sounds like something that is both undesirable and potentially solvable, so if we can get some more information on this in Support, that would be incredibly helpful. Thanks!

I tried to reproduce the problem yesterday but of course it did not happen again: I reopened the project in windows, worked on it, and then opened it in Mac: the mxe64 externals are still mentionned in the cache (as "other"), but did not create conflicts with the mxo as it did before. I tried the same on a brand new project and it was the same, no conflict. As soon as I can reproduce it I'll let you know.

However, I was wondering why the 3rd party externals have to appear in the dependency cache, actually. If they are in one of the paths (project directory or extra user paths), they will be found anyway.

@Kleine: by "clear the cache manually", you mean edit the max patches as text and remove the "dependency_cache" entry, or do you have a better solution?

I removed the temp items from the application support / cycling74 folder manually before opening a new version - but i don't recommend this procedure...

I removed the temp items from  the application support / cycling74 folder manually before opening a new version - but i don't recommend this procedure...

In case it's useful to anyone reading this thread (as I did), there's an option in the preference panel to save dependency path, or not (Thanks Ben B. for pointing this out to me!). The default being to save them.

And also, the issue is not specifically related to Max projects, but just any patcher (IIUC).

In case it's useful to anyone reading this thread (as I did), there's an option in the preference panel to save dependency path, or not (Thanks Ben B. for pointing this out to me!). The default being to save them.
And also, the issue is not specifically related to Max projects, but just any patcher (IIUC).


clear dependency cache for max projects?