How to document plugins/programs/presets for yourself?

Practical tips for recording, editing, and mastering.

Moderators: khz, MattKingUSA

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

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: https://www.youtube.com/watch?v=ycVrgGtrBmM
My music-related hobby business: https://chordpak.com/

Basslint
Established Member
Posts: 655
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 GeekosDAW!

miroona
Posts: 1
Joined: Sat Mar 14, 2020 2:06 pm

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

Post by miroona »

This boils down to file management and organization for me. My focus isn't on documentation, it's on the creation of music. I want to simplify the process for myself, rather than adding work when there isn't a need for it. For your case, I might suggest just creating a directory for untested plug-ins and taking the appropriate action once you've gotten around to fucking around with it (e.g, uninstalling the plug-in if it's not to taste). What do you think?

tavasti
Established Member
Posts: 1184
Joined: Tue Feb 16, 2016 6:56 am
Location: Kangasala, Finland
Contact:

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

Post by tavasti »

miroona wrote:
Fri Jun 05, 2020 3:03 pm
This boils down to file management and organization for me. My focus isn't on documentation, it's on the creation of music. I want to simplify the process for myself, rather than adding work when there isn't a need for it. For your case, I might suggest just creating a directory for untested plug-ins and taking the appropriate action once you've gotten around to fucking around with it (e.g, uninstalling the plug-in if it's not to taste). What do you think?
But plugins and softwares can have installer, and things aren't movable, so they can't be categorized with moving. And same thing with synth/other plugin presets, they are where they are.
Linux veteran & Novice musician

Latest track: https://www.youtube.com/watch?v=ycVrgGtrBmM
My music-related hobby business: https://chordpak.com/

jonetsu
Established Member
Posts: 1959
Joined: Sat Jun 11, 2016 12:05 am

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

Post by jonetsu »

Since a few years I'm using the file system. Plugins are either Linux native or Windows. Each category has a Test subdirectory where the installer of a plugin under test will be directed to install its things.

All plugins are on a distinct hard drive:
/dev/sdc3 /B3

All creations (Bitwig and Mixbus32C) are on another drive:
/dev/sdc5 /Compotes

For plugins the main subdirs are:

/B3/Plugins
/B3/Windows-Xubuntu

For illustration purposes, a sample of subdirs:

/B3/Plugins/

MOK/
Monoplugs/
OvertoneDSP/
pianoteq/
Redux/
Renoise/
SonicCharge/
Test/
Tracktion/
u-he/

/B3/Windows-Xubuntu/

IK Multimedia/
ImageLine/
Klanghelm/
KV331/
LaptopMusician/
LinPlug/
MeldaProduction/
MuTools/
PsychicModulation/
RobPapen/
Test/

All Windows installers are told to install in /B3/Windows-Xubuntu/Test/

Whatever they nevertheless install in ~/.wine/drive_c/ I do not care about. All I care is that the .dll are in /B3/Windows-Xubuntu/Test/


For u-he (Linux native) a symlink is used:

/home/user/

lrwxrwxrwx 1 user user 16 Feb 14 2019 .u-he -> /B3/Plugins/u-he/


Cheers.

tavasti
Established Member
Posts: 1184
Joined: Tue Feb 16, 2016 6:56 am
Location: Kangasala, Finland
Contact:

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

Post by tavasti »

jonetsu wrote:
Fri Jun 05, 2020 10:24 pm
Since a few years I'm using the file system. Plugins are either Linux native or Windows. Each category has a Test subdirectory where the installer of a plugin under test will be directed to install its things.
How do you handle bad installers which don't have proper uninstaller?
Linux veteran & Novice musician

Latest track: https://www.youtube.com/watch?v=ycVrgGtrBmM
My music-related hobby business: https://chordpak.com/

jonetsu
Established Member
Posts: 1959
Joined: Sat Jun 11, 2016 12:05 am

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

Post by jonetsu »

tavasti wrote:
Sun Jun 07, 2020 7:12 am
How do you handle bad installers which don't have proper uninstaller?
First of all, I consider that with the plugins I have I still need several years to master their use. This said, why look for new plugins ? The last I bought was the excellent Panagement whose author dropped a word about it here on LM. And at the same time got the other two plugins made by Auburn Sounds.

So that would concern mostly only Windows plugins. I install so rarely Linux plugins for the simple fact that I must have them all. With Windows plugins, since I specify a location on hard drive B3 to the installer, a lot of its stuff is there. So I do:

cd [testing dir on drive B3 for this plugin]
rm *

The files that were put in the wine user directory drive_c/ I don't care much about. drive_c is in the home directory and my home directories since maybe 20 years are volatile. I never put important files in any home directory. Thus the OS can change, have a totally new home directory, and after install I mount back the important partitions for data that I care about. This means that there's ample space in home/ for silly Windows files that were put in there even though I specified B3 to a Windows installer.

I actually never ran a Windows uninstaller. Also, I tend not to try plugins often, and rather not at all since some time because of the first statement above and also because I find I currently have a wide palette of plugins that covers a wide range of uses. The 100+ Melda plugins by themselves for instance. But when I was into the testing phase I simply used 'rm' to delete the main files of tested plugins which were installed mainly in a location I specified at install time.

User avatar
ycollette
Established Member
Posts: 50
Joined: Sun Jul 03, 2016 8:53 pm
Contact:

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

Post by ycollette »

For the Wiki solution, you can try https://tiddlywiki.com/
It's a one page wiki quite small and powerfull. No need for a server or a database.

Post Reply