I’m not particularly convinced by the audio analysis part, it’s not as good as Sononym for tagging the samples by “sonic nature” of course - but hey it’s free ! - and the pitch analysis is really fine and the whole thing will be really enough for me, not too complex. It’s super easy to include your own search paths too and the software will analyze them relatively quickly, starting by tagging from the filenames and then analyzing the files in more depth. Of course it has a direct access to the ADSR web-store and you can optionally download or buy some pre-purchased samples packs from this interface directly. Yes I’m testing the software too! I quickly loaded a large amount of samples (49k+). If this actually ends up being something useful, my hope is to publish the wiki parts of the database to my website, as well as make the metadata repo public. I am actually using this right now to build what I hope to be a an end-game centralized sample library for myself. Instead of cherry picking samples from various parts of my filesystem, all I have to do is load one SQLite database, and know their UUIDs (which I can figure out using utilities and SQL querying). This streamlines sample usage quite a bit for me. Currently, I have implemented the ability to load a WAV file into a buffer if provided with a partial UUID, which can then be used in various samplers and table-lookup oscillators included in my ecosystem. Fortunately for me, I mostly use a home-brew computer music system, so I can do this with minimal friction. My efforts here have been quite minimal so far, as I’m mainly focused on just dumping information into the system.įinally, integration. My wiki can be scripted using an embedded version of the Janet scripting language, so conceivably one could potentially use it to generate interesting presentations of the Zet. The Zet is included in my static wiki engine. That way, I can configure things in such a way to only partially compile the database if things get too large. Also, I’ve set things up so that TSV files can be broken up into groups. The samples would be contained inside of SQLar archives as small self-contained collections (presumably on some external drive), and then copied into the compiled SQLite database when they are needed to be used. The repo would only manage the metadata, not the samples themselves. The Zet could then be cloned onto a new computer, and then “compiled” into a SQLite database. This allows the Zet to be managed using source control. The Zet can be imported/exported using a tab-separated-value plaintext file. Crate makes it easy to automatically import files stored in a SQLar archive into a Zet database. I’ve build a bridge between my Zet and SQLar which is called Crate (inb4 Rust did it first). SQLite also has a strange experimental archive format called SQLar, which I’ve been very intrigued by. In addition to having an expressive querying language, SQLite also has goodies like full text search which make it a really powerful file format. My Zet and Wiki are both stored as SQLite tables. This provides the baseline for an annotation system and a tagging system. Things can also be things like messages, groups, and references to other things (via the UUID address). One of “things” a thing can be is a file path, presumably pointing to a particular sample. Keys don’t have to be unique, which allows a single item to have multiple attributes. Every “thing” has a UUID4 tag as the key (I use the uuid4 library by rxi to generate these). Using this structure, I can make things and link things to things. The Zet structure is essentially a key/value database with timestamps. I’m hoping if I keep at this long enough, these sort of relationships and structures between samples and sounds will naturally form.Ī few weeks ago I started building a Generic Zettelkasten (the “zet”) for myself, which is part of the static wiki generator I built for myself about year or so ago. Over time, this network of connections allows for interesting relationships to emerge. Zettelkastens usually have some sort of cross-referencing capabilities. Well, sample libraries are like that as well. My approach is to try manually catalogue, tag, document, annotate, etc content in a centralized place, and then build out solutions that can integrate with this database format.Ī Zettelkasten is a means for storing and retrieving information in a very granular fashion. The TL DR is that I’m attempting to turn my sample collections into something resembling a centralized Zettelkasten, and storing it in SQLite. It’s still a growing and evolving, but I think I have a pretty solid foundation. This is finally a relevant thread for me.Īfter years and years of thinking about it, I recently decided to take a stab at building a system for organizing and curating my various sample libraries and collections.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |