AE Modular Template

I did not know this thread existed. I’m pretty fluent in python. I may be able to bring something to the table with the above project. As I have time I’ll see what I can do for us!

I've spent a lot of time trying to find an optimal patch-notetaking method. My main goal is to create a visual record of my music that is just as beautiful to see as the audio recordings are to hear. But besides this, I also want a system that is easy to record, easy to follow, and allows me to reasonably predict what the sound would be. 

The most obvious way to create patch notes (and the way that is presented in the instructional material that comes with the Starter Kits) is to literally represent each module with a photo/render, and to draw little lines to show all the connections. This sort of literal representation is timely to draw and includes way too much information. To fix this, I used the following patch note system.

System 1: Abbreviated Literal

In the Abbreviated Literal system, I draw literal representations of each module as they would look in real life, but omit any unnecessary information. Pins outs are ordered exactly as they are in real life, but not all pins are drawn. Any omitted information is represented by a dotted line. I only include potentiometers that are relevant to the patch, and draw them in the positions they are found in the patch, rather than represent their positions as a percentage.

Drawing these in a notebook lets me sit and mentally process the patches for a little bit before moving on to the next one. My music teacher in high school said I was too easily distracted. Slowing down to record my work has helped immensely. Drawing also lets me use the colors I want to use.

Take a look at the "Random with Sample and Hold" Patch from the instructional material included in the Starter Packs represented in this Abbreviated Literal.



System 2: Wolfgang Schaltung (modified) plaintext

I briefly tried representing my notes as parseable script (much like to Patchbooks script) inspired by a post on another forum. But I found plaintext notes tedious, confusing, and drab. I also found I could not predict the sound of the patch in the slightest; I needed the help of visual representations. However, in a test I did with my wife, this system did seem to be the most precise for reproducing the patch. It seems that any abstraction (and therefore visual representation) of the patch creates ambiguity and confusion.

Take a look at the same patch described in plaintext.



System 3: Graph Theory

In an effort to make the patches more beautiful, I took inspiration from Graph Theory. The idea here is very similar to the Patchbooks method, with icons representing modules. However, I wanted to use more visually pleasing icons. The connection to graph theory comes from using an online graph editor to optimally place the modules to reduce wire crossovers. I think it has some potential. However, randomly throwing modules around in space offers little insights to signal flow. It was also impractical to go to a computer after every patch to find the "optimal" design.


Here is the same patch using the "Graph Theory" design.




Design 4: Information Highways

The patch notes design I currently use takes the beauty of the "Graph Theory" design and adds signal flow information. Modules are represented with shapes (Corners for CV or audio sources, curves for signal processors) and color (CV = orange, audio = cold colors, etc). As much as is possible, I try to show signals flowing from left to right. Modules are aligned vertically on the page as well.

I found this patch notes system is compact, aesthetically pleasing, and relatively clear. It is also the quickest to draw.

Take a look at the same patch drawn in this manner.




And here is one more patch I made, with all of the notes I took to accompany the visual record.