Workflow and files - how do you keep your max and non-max files together?

    Oct 02 2013 | 10:02 pm
    Hi all, I recently installed Github which I like for my Arduino file control, but I wonder if any of you have advice around keeping together your max patches, abstractions, and arduino sketches (and in the future, processing, and any other related files).
    I have built quite a library of abstractions which I call upon from different patches - Do I put the entire library on git?
    Or, do I occacionally do a 'save as project' and store everything together? I think the back up process is a bit dramatic - you have to decide _now_ is the time to take a backup (save as project) and have that snapshot in time: I wish I could have something that is a bit more seamless, where I can just continuously work, edit, improve but still go back to the last working version.
    What works for you?

    • Oct 02 2013 | 11:07 pm
      We were considering getting up on github with our entire band system, across like 7 peoples patches, abstractions etc.
      We decided to go with google drive, and man that really has been awesome to work with. Automatic syncing across many machines, everything updates as it should, and the next time you load patch x, it'll auto-load with my revised abstraction y.