![]() 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. I have high hopes right now with XY and will maybe update my file management journey for any other musicians looking for a way to combine their software workflows.Ah. My basic testing over a couple of days has been really fruitful in finding ways to combine all these different softwares around a central file manager that has features useful to me as a musician - e.g., labels, the catalogue, colours and the superb tools and customisation. Bit of a double-bind!Īnyway - this is how I ended up here, at XY. Sample management software in the music world so often lacks the most basic of file management tools - yet can be superb for waveform work. ![]() The main music creation software (DAWS) like Cubase, Ableton Live, Studio One and others all have file management - but not REAL file management, often restricted to identifying favourites, and grouping into projects etc. This is a little restrictive from my point of view because it makes an assumption about what sound files are most appropriate - and the assumptions are sometimes wrong. Then there is Algonaut Atlas - a well-respected program that focuses on constructing drum and percussion kits based on an 8, 16 or 32 grid layout, using AI to try and identify sounds according to certain parameters. My understanding is that XY will be unlikely to have this functionality - this is ok because XY plays nicely with Sononym. But it does have a functional waveform display which allows me to "crop" files and then drag the results elsewhere. Where Sononym begins to fail is when I want to then organise the files it has found - it has few file management options. For a musician this is great - I record something in a certain key and can then find other files that have similar audio characteristics. ![]() This is great if I want to find a file that "sounds like" another. Some music software like Sononym have sophisticated sound recognition and matching capabilities. Music creation software from Cubase to Ableton Live do have some limited file management but "limited" in so many ways and missing features like file comparison, duplicate finding etc etc. Music files - loops, samples, wavs, recordings, aiff, ogg - are all just files. I have arrived at XY a couple of days ago when my frustration with existing "file management" software for musicians caused me to want to break things!
0 Comments
Leave a Reply. |