Patches
Patches are the memory layer of Patcher.
Use them when you need more than a loose note or a photo on your phone. A good patch entry lets you reopen a session later and still understand what mattered.
What a patch can hold
A patch can bring together:
the modules involved
cable routing
notes and descriptive text
naming that makes recall easier later
sharing choices for public visibility
Create a patch
Go to User Area.
Open the Patches section.
Click Create patch.
Name it clearly.
Add the modules you need.
Start documenting routing and notes.
Why collection-first matters here
Patches work best when your collection is already accurate.
That gives you a reliable source list for module assignment and keeps your patch notes grounded in the hardware you actually use.
Read more: Collection
Add modules to a patch
Before you can document routing well, the relevant modules need to be part of the patch.
The practical flow is:
keep your collection up to date
create the patch
add the modules involved
document the signal path
Add connections
Once the patch contains the right modules, add the routing step by step.
This is where Patcher becomes especially useful for recall:
inputs and outputs can be documented intentionally
repeated modules remain distinct
the patch stays readable later instead of turning into guesswork
If a module is missing useful I/O data, improve the module data first when possible. That pays off elsewhere too.
Repeated modules and instance clarity
When the same hardware appears more than once in a patch, Patcher keeps those instances distinct.
Use that deliberately. Give repeated modules names or notes that make the role obvious later, especially when one module is doing more than one job in the same session.
Edit without fear
Patches are meant to evolve while you work.
Patcher is built around fast iteration, including auto-save for patch state and edits, so it stays useful during an active session instead of only after it is over.
Naming and notes
The more patches you save, the more naming matters.
Good patch names and notes should answer:
what the patch does
what makes it different
what you would need to remember under pressure
Public and private use
Not every patch needs to be shared.
New patches currently start public, so check the sharing toggle if you want to keep a patch private while it is still a working draft.
For public discovery, the patch itself needs to be public and your profile also needs to be public.
Best practices
save patches while the session is still fresh
keep names specific
note unusual routing or settings
treat repeated modules as distinct voices, not interchangeable placeholders
share only the patches you actually want attached to your public profile
Related pages
Last updated