How to document plugins/programs/presets for yourself?

Practical tips for recording, editing, and mastering.

Moderators: MattKingUSA, khz

Post Reply
Established Member
Posts: 1060
Joined: Tue Feb 16, 2016 6:56 am
Location: Kangasala, Finland

How to document plugins/programs/presets for yourself?

Post by tavasti »

At least I have problems remember all the software and presets that I have found useful. Reading music related stuff from this forum, irc or some other place, seeing link for interesting plugin. Download it, 'I will test when have time'. Or even test it quickly. So question is, how to document these things for myself? One possibility is to have it shared with others, but then data usability may be lost. Plugin that works great for metal maniac won't be that great for hip hop producer, and needs of Lo-Fi producer and progressive fusion are different. Another thing is that marking 'downloaded, not tested' is not meaningful for others :-)

So what tools to use, what fields to have in data? My idea is to use google sheets, but any better ideas? Some local app or web-based solution (can install stuff onto own server) are also possible.
Linux veteran & Novice musician

Latest track:
More my music

Established Member
Posts: 322
Joined: Sun Jan 27, 2019 2:25 pm
Location: Italy

Re: How to document plugins/programs/presets for yourself?

Post by Basslint »

I suggest a personal wiki such as Zim :D
The community of believers was of one heart and mind, and no one claimed that any of his possessions was his own, but they had everything in common. [Acts 4:32]

Wanna make music on openSUSE? Check out Geekos DAW!

Post Reply