![]() This is the way it should be: find -name "*. I first tested like this: find -print0 -name "*.mp3"|xargs -0 tag-command -flags This meant that my impression was that none of the editors worked, when in fact all but one did work. It is not, in fact when find encounters a "-print" or "-print0" command it prints right then and there, and any flags coming thereafter are ignored (unless another -print or print0 command follows them). I had treated "-print0" as just another flag to the find command. This blog posting has been completely rewritten after "jax" commented that the find command used had been wrong. One difference between eyeD3 and the other working editors was that they stopped when being fed a faulty file path, while eyeD3 continued with the next path. and eyeD3 just chugged on like that, adding tags. (no output generated on command line) id3v2 worked like a charm.ĮyeD3 also worked like a charm: find -name "*.mp3" -print0|xargs -0 eyeD3 -G Salsa Finally I also ran it on files that had already been tagged it still reported "No ID3 tag found", and hanged. I copied the mp3 file it stopped on to another directory and ran id3tool on it as above, and it worked fine. Id3ren just hanged there for at least ten minutes, at which point it was terminated by me. find -name "*.mp3" -print0|xargs -0 id3ren -genre Salsa (no output generated on command line) id3tool worked like a charm. Here are the results: find -name "*.mp3" -print0|xargs -0 id3tool -G Salsa The "-0" flag is to unpack the NULL delimited items xargs gets from find. "xargs" then executes tag-command for each item that find finds. Do note that the -print0 command needs to come after the parameters to find! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |