We do not currently support iXML read/write in our products. Library Monkey – Monkey Tools – US$129 – OSX
Library Monkey Pro – Monkey Tools – US$399 – OSX Not directly in BaseHead, but we use a SQLite database now and there are plenty of tools to read our non-encrypted database and export that to a Spreadsheet.īaseHead can read: BEXT, iXML (limited), aXML, SNDM v3, NMIX, ID3, OGG Or use some SQLite tools to migrate data, but I suggest the first way since then the files have descriptions in them permanently. Not directly, most users migrating metadata end up formating Excel sheets in a way that Injector Pro likes and then just burn the descriptions into the files permanently. We support only open standards and always will! Not directly, but we invite any other sound library programs to read it since it’s only basic XML. It’s basic XML based so an other program can read it if they sat down for 10 minutes and coded it in. BaseHead also writes all changed descriptions to aXML and BEXT simultaneously since BEXT has a character limit of 256 – aXML is helpful for long descriptions and files with tons of indexes in one file. Injector Pro writes this with indexes that we read in BaseHead. Yes, we have a chunk called aXML that is the same as iXML but labeled differently so we can find it quick.
We write aXML now and full support for iXML in Version 3.x We do but only from recorder files in which the BEXT is standardised. Please see the app for the complete listing.Ĭan I import metadata from a spreadsheet? what formats are supported? Yes, if they want to read the database, the format is open and not encrypted.Ĭan your custom metadata be exported for use in other programs?Ī user can use an SQLite utility and export the database, into many formats.įields that are musically useful i.e. It doesn’t read some of the custom sections.Ĭan your custom metadata be read by other programs? Anyone is invited to work with the AudioFinder metadata database. There are plenty of little database utilities out there that can work on it. SQLite is open source and an industry standard. The special part about the AF metadata implementation is that it’s open. When the user enters metadata about a file, a new database entry for the file is created, and the file is finger printed, so if they move the file, the fingerprint will allow it to be reconnected to the metadata database. Therefore, AudioFinder keeps all the metadata users enter in an SQLite database. Most of the open standards like BEXT and IXML are focused on post-production and broadcast and don’t really offer anything useful to someone looking for sounds in a music project.ĪudioFinder does not modify files – when people do processing actions in AF it always creates a new file. The second potentially larger niche, but completely ignored is musicians managing sample libraries, this is AudioFinder’s focus.ĪudioFinder’s Metadata is aimed at adding properties that are musically useful to people composing music. This is not where AudioFinder is focused. This is primarily where all the apps are focused.
Market one, the main one is sound designers for post production managing sound effects. “There are two market niches for metadata, one is overflowing with support and the other has been almost entirely ignored.
If in future you wish to update any of your comments as new features are implemented, please also get in touch!ĪudioFinder – Iced Audio – US$69.95 – OSX The implementation of metadata is an evolving area, and this post is a snapshot as per these apps now. Developers, if I have misquoted you at all please get in touch asap (using the email link over on the right) & I will update this post – I totally appreciate how much hard work is involved in developing and evolving these apps and it is very important to me that your work is represented fairly & as you wish.
If any readers know of Sound Library software that I have missed which should be included, please let me know in the comments – I did contact NetMix but have never had a response. – can I import metadata from a spreadsheet? what formats are supported?ġ. – what fields of metadata do you support? – can your custom metadata be exported for use in other programs? – can your custom metadata be read by other programs? Following on from previous posts about metadata, I have emailed the developer of each library app and asked the same questions of them, specifically:Ĭould you provide basic info for me as to how your application handles metadata?