![]() On the server side a small python app could take the files in, analyze and store them. launch a small and simple webserver, as interface to the userĪll of this should be working probably at least for OSX and Windows.Instead my idea would be to build a small go application that only does ![]() I guess most user (of the op-1) won't find it very easy to install python and use a command line tool. See Īlso ID3 Tags would be possible, but sadly also had no luck in getting them working with mutagen. Regarding adding own metadata: There are several other chunk types defined in the aiff spec that could probably be used. So i can't say if the op-1 would be reading that files. The json format is subtle different from what you would expect, but could be easily generated with something like data = "op-1%s" % json.dumps(self.op1data, sort_keys=True, separators=(',', ':'))Īltough I had no luck in getting the actual write done with mutagen. Just did several tries with the mutagen library, to first simply read the existing metadata, and then writing it back unchanged to aiff. I will do some testing in the next few days.Īnother thought is that Teenage Engineering may be open to including these proposed author and license fields into the official metadata spec, since it seems they would have general appeal. Of course this hinges on whether or not we can get away with adding our own JSON metadata to the AIF files. Other users can grab specific patches from that pack to use in their own packs, and we can make sure that author and license info follows each patch around in the UI. They can then group them into a "pack" on the site and share that as they like. Instead of asking users to do the step of making a pack locally before uploading it to the site, we can just let them upload a pile of AIFs and write some metadata to each one automatically. For completeness it could also generate a txt file with author / license info for the patches within, but as described above that same data should already live inside the AIFs themselves. When downloading packs from the site it can make a zip file with subfolders for the three types on the fly. They can then download the AIFs and do as they please – using tools like opie, etc as usual. What if the website allowed users to browse around and create their own collections (packs) of patches by organizing them (somewhat like soundcloud allows you to make playlists)? If the author/license data were attached to each patch then it would make sense to let people compile their own novel groups of these. If it were possible to add our own metadata to the AIF then I think attaching author and license fields might be all that's needed for a good experience. I'm starting to wonder if this "pack" format needs to live outside of this website idea at all.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |