Basically, it\u2019s useful because instead of keeping information about \nfile, next to it, you can embed data about the file into the file \nitself. This will travel with it and persist wherever it is used until \nsomeone changes the metadata for themselves.<\/p>\n\n\n\n
The de-facto way to do this is using some of Adobe tools that come \nwith their Creative Suite. The downside of these tools is that they cost\n money and it\u2019s a little harder to batch process things. Batch \nprocessing is something you definitely want to be doing where possible \nbecause it saves you time and it\u2019s much better to get a computer to do \nrepetitive tasks than doing them yourself.<\/p>\n\n\n\n
For these submissions and your work in general, you can go as far \nwith this kind of thing as you like and you\u2019ll have to be careful to \ndecide just how much work you want to put into this. Suffice to say, if \nyou follow along with what\u2019s below, you\u2019ll have all you need to very \nquickly insert metadata directly into your The Command Line is where this kind of thing comes into its own and \nit\u2019s worth your while learning to use it to make these kinds of tasks \neasier.<\/p>\n\n\n\n To proceed, you\u2019ll need BWFMETAEDIT in both its versions. You need \nboth the CLI (commandline interface) and the GUI (graphical user \ninterface). Get them both here: mediaarea.net\/BWFMetaEdit\/Download<\/a>.<\/p>\n\n\n\n What I\u2019m showing here is only tested on OSX, but it\u2019s likely (with a \nlittle command prompt nouse) to be completely doable for Windows users \ntoo.<\/p>\n\n\n\n BWFmetaedit explains itself pretty well online. The list of data that you can insert is here:<\/p>\n\n\n\n.wav<\/code> files and then be able to generate documents about these files in record-time.<\/p>\n\n\n\nNote<\/h2>\n\n\n\n
What metadata do you need?<\/h2>\n\n\n\n