backuping, versionning and other stuff-ing

    Jan 09 2010 | 10:34 pm
    hello, til now, I just play, test, try. now, I really begin to work with Ableton Live + max for live & max/msp/jitter.
    so I'd need a very reliable system based on backuping and probably versionning.
    I used to use SVN (w/ Tortoise)
    For backuping, how could I proceed? I mean, I have the Max5 folder. I'd like to backup all the data I'd need to restore.
    crash, I reinstall Max, I restore folder, all is ok.
    where could I put my libraries to do that? in an external folder could be the best way, couldn't it ?
    all ideas/methods would be appreciated.

    • Jan 10 2010 | 12:07 am
      this might not be much help, but my entire hard drive including applications and most serial keys is backed up via bootcamp.. are you mac or pc?
    • Jan 10 2010 | 3:39 am
      Here is something that I saw posted on CDM a while back. It's about version control with GIT but specifically in relation to max, it might be worth a look.
    • Jan 10 2010 | 9:59 pm
      hello, PC here.
      no prob for svn especially.
      my question was more about what folders I should backup.
      Do you use special folder for your external libraries? for your patches? for the main configuration of max/msp/jitter files ?
      The purpose is : restore as before a crash without having to retrieves all the config.
    • Jan 11 2010 | 1:26 am
      sorry, i think i misinterpreted the question somewhat! :)
    • Jan 11 2010 | 5:18 pm
      my question was more about how to backup all the max5 configuration and customization. I read But I didn't find if there was a folder where all the config files were etc.
      any tips? ideas?
      maybe, the solution is: backuping the whole max folder (wow!)
    • Jan 12 2010 | 3:38 pm
      I simply abuse my dropbox for versioning. Seems way easier than git. The main problem is to follow changes in the library. Usually my library changes all the time and my projects folder should not contain a complete copy of the library. While working on a project this is not a problem, but if I have to come back to a project maybe years later, the library might have changed... I always wanted a "build distribution" choice with the build collective/application functionality of Max. It should simply copy all non standard externals and all abstractions used by a project patch into a separate folder... But my begging had never been heard...:-(
    • Jan 12 2010 | 4:28 pm
      Why not use SVN on the files you want to modify only? This can be accomplished in TortoiseSVN the following way.
      * Create a empty respository * Check out into Max 5.0Cycling '74
      This will create the repository but not version or modify any of the existing files.
    • Jan 12 2010 | 5:20 pm
      It could be fine, indeed, Hans. I think I'll do that : - a specific folder for all external libraries (added in the max path) - specific folders for each project - TRY to find where the objects default custo are stored!!!!!
      thanks all !!