When Two Become One
Category: Lab
After going to CodeMash 2.0.0.9 this year I realized how functional it is to have workflows in all of my work. The ideas of backups, version control, and continuity are important in all types of processes so I started to think of how I could move some of the best ideas across.
Arguably one of the most important parts of producing good Object Oriented code could object/class relationships and structure. Having the ability to have like items organized and defined properly can lead to good use of functions and properties of the objects. So to move this closer to my music world I have started to define the items in my MPC more accurately. This means a folder for like items: Sessions, Sequences, Programs (kits), Samples/Loops, Vinyl Samples (chopped and unchopped), and individual instrument sounds. In each folder I have started the process of sorting and managing these lists. My MPC has a much better organized folder structure and the 120 gb hard drive inside seems to spin a little happier.
Above photo is a view of the MPC sample folder
The above photo is a set of loops on my backup hard drive, the goal is to match the MPC.
Taking the concept of backups from my music backups and code backups to the production world has landed me with a backup scheme that will allow me to transfer changes from my MPC to my backup hard drive as often as I see fit. This will save me some time in searching and hunting for samples when going back and forth between the DAW and the drum machine. The MPC does allow me to connect to it via USB, but if I am looking for something quick or if the MPC isnt even booted up, the back up hard drive is available to use. The added bonus is that if something goes wrong with the MPC hard drive, or if someone offers me a ton of cash for my MPC and hard drive on the spot, I can go back from scratch to a match (of the favored setup) in no time.
Moving from templates and frameworks on my dev side I have started to focus more on my autoload setup for my MPC. Since the MPC is becoming my favorite couch/coffee shop DAW available, it should be easier to start and stop in short chunks requiring minimal time to get into the grind. The JJOS setup and the upgrades they offer remind me of the available plugins for VS 2008.
In a move from audio to development, I think I am finally getting closer to test driven development in most cases. In my audio setup, I start with a simple loop and build onto it going steps at a time and testing each step before continuing. The process has been leading to a better defined scope and tighter code/patterns. This also leads to better builds or what ProTools would call Bounce(s).
Versioning has been something that both sets of my life need. In development the requirement is obvious for tracking bugs and issues; in the audio world it may not seem as useful. When I really like the way a song is sounding, I can save as and start a new branch, as the mix changes I can merge tracks back or leave them out to be a complete release. In the early stages of a track having good templates or skeleton branches seems to be useful for getting to building tracks quicker. I have also found plenty of use in versioning while practicing my mastering craft.