Live Set & patch portability
Hi I am sharing a set with some friends and it uses a M4L patch that is constantly updating so I would like to store the patch within the project folder that I am sharing. Is it possible to have a relative path to the patch? Or must all people that are sharing the project, keep the project in exactly the same volume/folder?
I am interested in the exact same thing. Has this never been answered on this forum or am I just too dumb for the search function…?!
What does ‘constantly updating’ mean? What’s updating about it?
I guess the OP was still developing / improving / changing and thus constantly updating the patch.
However, more importantly I am (we are) interested in how to store relative paths in Max or M4L. In my case I want to be able to load a sample, store its path in a pattr and then copy the device to a different machine. The sample might stay in the exact same folder along with the device but if I try to load it pattr only holds the original absolute path which might defer greatly of course.
As far as just changes in the actual patch, freezing is the best option (or svn I guess if freezing isn’t possible).
For your situation, I’m not sure…I haven’t done that before. But if it doesn’t have to be platform agnostic, there are ways to do it….[shell] external might be one way, I know you can do some tricky things with it. I know there are other ways of doing it as well, I’ll be looking into it myself so I’m interested in hearing other answers ;)
Sorry "constantly updating" isn’t the best grammar admittedly. I Meant the Max device is integral to a song that is bring shared using an FTP sync app, I was editing the device as often as the song. The song in question never actually got worked on by the band but it might someday. I’ve since noticed Max devices are included in the ‘manage project files’ feature so it could be easily re linked everytime.