Medusa - how do you write down patch notes to remember the details later?

I’ve been thinking about improving my organisation for music projects by keeping notes on patches and projects so I thought I’d ask if others had any ideas
Wanting to make a full bank of custom patches but make sure the patches are user friendly so I can go back and use them for recording samples with external processing later on.

How do you help yourself remember how your patches were set up when you go back to them?

Does anyone use a template for writing down notes on patches to assist when going back to patch’s or for live playing a patch or working out a song structure?

I’m thinking to make a template so I can print out a book of patches including drum and melodic patches

Template could include:
Notes on using the specific patch with tracker projects
Key, tempo and other general patch info
Patch description
Grid with a system to make notes for specific pads (xy settings, modulation pads without notes)

3 Likes

Hey @lachie.mcguckian - ah yes. The question as old as time! :timer_clock: :laughing:

I’ve always asked that myself and tried various things, but here’s what has worked best for me in the past.

I’m usually a stickler for detail when it comes to patches, but i had to let go of that notion as it was way too time consuming and in the end it didn’t really matter all to much.

The important bits where always:

  • Location of the Patch (where is it stored, so i can recall it)
  • Which part (knobs/slider/pad etc) is meant to be performed.
  • As short of a blurb as you can muster, to describe what a knob/function/slider does or how it affects the sound.

This way you end up with a mostly small description of a patch and it’s performance features. Which usually really all you want. If i needed to understand a patch fully again, i would just dig into it again. But thanks to that description, you usually remember or piece it together pretty quickly again - even after not having used it in a long time.

3 Likes