32bit

Using two platforms; Mac OSx 10.6.8 and Windows 7 I am noticing some strange (I think) .maxproj issues with Max 6.1 64 bit

1) In Windows Max will crash when files are dragged into the project window (seem to be .maxpat files with a data dependency that really trigger this)

2) .maxzip files compiled in Windows 7 show no patchers when unzipped in OSx

3) .maxproj files that have been archived in OSx, when unarchived, cause Max to crash (nothing ever happens after click on .maxproj or subsidiary patcher)

I have been using the option to "always localize project items" assuming that this is the easiest way to keep revisions separate.

I can see how this would lead to some pretty thorny filepath issues, as one .maxproj patcher folder will have many of the same patcher names as another .maxproj folder

Maybe I have misunderstood the .maxproj protocol. In general I have been consolidating and saving a snapshot of the .maxproj into an "archive"

folder within the documents>max>projects path. Sometimes I rename the .maxzip something more descriptive than the automatic date string.

Using two platforms; Mac OSx 10.6.8 and Windows 7 I am noticing some strange (I think) .maxproj issues with Max 6.1 64 bit
1) In Windows Max will crash when files are dragged into the project window (seem to be .maxpat files with a data dependency that really trigger this)
2) .maxzip files compiled in Windows 7 show no patchers when unzipped in OSx
3) .maxproj files that have been archived in OSx, when unarchived, cause Max to crash (nothing ever happens after click on .maxproj or subsidiary patcher)

I have been using the option to "always localize project items" assuming that this is the easiest way to keep revisions separate.
I can see how this would lead to some pretty thorny filepath issues, as one .maxproj patcher folder will have many of the same patcher names as another .maxproj folder

Maybe I have misunderstood the .maxproj protocol. In general I have been consolidating and saving a snapshot of the .maxproj into an "archive"
folder within the documents>max>projects path. Sometimes I rename the .maxzip something more descriptive than the automatic date string.
Any advice would be helpful.


bug-issues-with-projects-in-max-6-1-and-6-1-1

We've solved all of these growing pains for Max 6.1.2. Thanks for the succinct report.

As for localization, that's fine: projects have search paths which are isolated from every other project -- they can't see file in other projects at all, even if they have the same name.

Bug: Issues with Projects in Max 6.1 (and 6.1.1)?