Managing project files in m4l
Posted: Mon Apr 25, 2016 12:31 pm
say a frozen device uses a particular patch X which I have in my search path.
If I edit the patch X , the device still uses The old version , and when I unfreeze it a project folder gets put in max7/max for live devices, containing the old patch X, which it refers to over the new one.
That sort of makes sense, but if I try to add, say a bpatcher to my device, that uses the new patch X, or I try to replace the bpatcher file with the new patch X, I can't shake the association to the old patch X. The only way I know to do this is to delete the old file version in the project folder first, using the finder, which seems a bit clunky.
With regular max projects I can specify which files are global and which are local, but I can't work out how to deal with this in m4l projects (every device is a project apparently)
Any ideas how we're supposed to update files in m4l devices or manage m4l global/local files?
If I edit the patch X , the device still uses The old version , and when I unfreeze it a project folder gets put in max7/max for live devices, containing the old patch X, which it refers to over the new one.
That sort of makes sense, but if I try to add, say a bpatcher to my device, that uses the new patch X, or I try to replace the bpatcher file with the new patch X, I can't shake the association to the old patch X. The only way I know to do this is to delete the old file version in the project folder first, using the finder, which seems a bit clunky.
With regular max projects I can specify which files are global and which are local, but I can't work out how to deal with this in m4l projects (every device is a project apparently)
Any ideas how we're supposed to update files in m4l devices or manage m4l global/local files?