[ APE Tag Writer ] (zip) [version 1.01 released 2005-05-26]
[ Sourcecode ] (zip) [version 1.01 released 2005-05-26]
Release History
Description
APE Tag Writer is a small (12kb) command-line utility used for writing audio tags to Monkey's Audio compressed files using tag data from a textfile.
APE Tag Writer is implemented in C# and has been tested to run under .NET Framework. There should not be anything in the implementation that prevents it from running on Mono as it only uses the System, System.IO and System.Text namespaces.
APE Tag Writer is completely free to use. You can use the sourcecode as long as you give credit. See License.txt included with the sourcecode archive for details.
Operation
Nota Bene: APE Tag Writer requires an installation of .NET Framework or Mono!
APE Tag Writer reads text files in Vorbis Comment format. Audio Tag Extractor can be used to create such files from MP3 and Monkey's Audio files.
APE Tag Writer is very useful if you want to automate the writing of tag data, for example, when transcoding to APE from FLAC. I've used it to write tag data from FLAC-backups of my CD-library. With some additional script-commands I was able to loop through, transcode and move all of my CD-backups from FLAC to APE with very little effort (Contact me if you want my batch files) and all tag data preserved in the APE-files.
Command Format
Program usage: APETagWriter [infile] (options)
Options:
-?, -h (--help)
Display this help information.
-e (--echo)
(Default) Output information to console during run.
-o (--outfile) [outfile])
File to write tag to. Default writes tag data to infile. This is used if you want to preserve the original APE-file.
-q (--quiet)
Do not write information to console.
-r (--replace)
Replace the existing outfile.
-t (--tagfile) [tagfile]
File to read that holds tag data! Must be VorbisComment format (for now at least)!
-x (--exclude) [list]
Exclude tags from output. List separated by commas.
Example use: -x GENRE,COMMENT,TRACK
Comments and Feature Requests - chreo@chreo.net
Comments (feedback, bugs etc) and feature requests for future versions are most welcome. I will answer all e-mail (unless it is flame and spam or becomes to overwhelming).