Wednesday, August 08, 2012

Applying Network Maps and Music Data to the Production and Compositon Process

For this experiment in thinking:  Recreate this chart to make more sense on my music composition and recording processes. Also create similar graphics for violin styles, music composition techniques, chord progression charts, and other types of "music data".  

Goal: Use this type of "music data" as quick-references for reproducing setups, experiments, application settings, plug-in settings, etc. for the audio-recording and composition processes. This is just like using a chord-chart reference to learn a song on a guitar, only expanded to be useful for other music production processes.

This could be a cool Prezzi graphics and/or dynamic slide show. Try it.  Or maybe HTML5 application (instead of the Flash tools). 

"How-To" (YouTube, etc.) videos are great too, and easier than ever to create, but sometimes you would like to get the reference "at a glance" instead of going through the whole "show-and-tell".

Mind-mapping is the equivalent of a website wire-frame reference document for a website: you are trying to identify how to interconnect tasks, ideas, ingredients, processes, products, etc. But I have found mind-mapping, as a part of the creative process, is a layer of abstraction away from actual creative activity, so it either gets in the way or is ignored as I work on a project (especially music). I can visualize a different way of using mind-mapping that does not focus on the map itself, but like jump-links on a web-page, they are naturally linking back to the ongoing map or wire-frame of the project. 

For example, inside a music composition program, as you create new tracks, add synthesizer patches, create dynamics, etc. there is a map created that flows automatically from the top-level hierarchy of "song" and catalogs all of the elements that have influenced and/or contributed to the song process. This is hard to imagine as an automated process, but I need something like this to continuously document my experiments so that I can "retrace my steps" to get the same results again. For example, when I make certain adjustments to classic audio-controls (delay, reverb, compression, gain), or adjustments to synthesizer settings, I would like to see a visual record of these settings for later reference, and a set of links that ties this information together like hyperlinks to be able to walk through, replicate, or further modify from this "baseline" so that this can be "repeated" in performance, recorded as part of the copyrighted music-score, etc. 

In other words, I want an expanded music-scoring system that includes the embedded application details from within the recording-tools, and especially for synthesized-derived compositions. 

I will be experimenting with this type of documentation process in future audio-recording/composition projects.

No comments: