Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
ramptag | 2011-09-05 | 1.5 kB | |
README | 2011-02-16 | 1.7 kB | |
Totals: 2 Items | 3.3 kB | 0 |
This perl-script is a wrapper for the mixramp utility. About mixramp: Mixramp is a utility to analyse sound files and print out the volume profile of the start and end. The idea is to embed those profiles in metadata so players can do intelligent mixing between tracks. Mixramp-tags are supported by mpd. This tool is currently the only one who create these tags. Get the tool here: https://sourceforge.net/projects/mixramp/ * * * My script adds the following functionality: - Ignore files that has the mixramp tags already. - Use mid3v2 to update file tags to id3v2 (required) prior to mixramp tagging. - Run the mixramp-tag tool on the file. - Safely exit a loop anytime by pressing any key. The script will finish an eventual file write before terminating. - Optional: File filtering: Consider only to use files who has tag(s) containg <string>. Example: ramptag ftag=TCON=Bollywood /my/music/* This will run through all mp3-files in the directory /my/music/, but only files where "TCON=Bollywood" are found amongst the tags will be considered. You can easily do a wider filtering, for instance "ftag=Hitparade" will pick out all files that's got "Hitparade" mentioned *anywhere* in the tags. Could be as a comment, in the title, album, whatever. I've run this script through a major part of my collection (I'd say 60-70.000 files), and so far it seems to have gone flawless when using this script. However I have experienced using mixramp-tag directly that it (or rather, eyeD3) mess up the tags on some files quite severly, so be careful. I got 4 mirrored disks of my music collection, and I suggest you do the same before starting to mass-alter the entire base using these kind of quick'n'dirty scripts I've whip together here.