Printable Version of Topic
-Brading Software Message Board +--Forum: Mp3/Tag Studio Support and Bug Reports +---Topic: Rename file from list started by calberga Posted by: calberga on Mar. 27 2008,21:27 Two whines, one simple, the other not. The simple whine: Would it be difficult to make "Rename Files From List" work on non-.mp3 file? The complex whine: Soppose I have files named: a.foo b.foo c.foo And I want to rename them as: alpha.foo beta.foo gamma.foo but I only have a text file contianing a - alpha b - beta c - gamma Is there any way to specify the file-extension in the old-name and new-name patterns in "rename from list"? <old-filename>.foo - <new-filename>.foo Yes, I know that won't work, but perhaps it gives the idea. How about <old-filename[|.foo]> - <new-filename[|.foo]> More generally, is there a way to construct filenames from list items concatanated with constant values? Posted by: Magnus Brading on Mar. 29 2008,15:41 I'm not completely sure what you mean, where would the file containing "a - alpha", "b - beta" etc come into the picture? Posted by: calberga on Mar. 29 2008,20:19 I'm referring to "Rename from list", and the file is the list. PS, this really should be in "suggestions", as I don't expect anything that will help me right now, just (possibly? maybe? if you/I/the lamp post can figure out a non-ambiguous syntax?) some time in the future. Don't worry about it too much -- that's why I labeled these "whines". Posted by: Magnus Brading on Mar. 31 2008,13:02 As you (almost) say, doesn't the following work? <Old name-1[|.foo]> - <New name-1[|.foo]> Posted by: calberga on Mar. 31 2008,13:49 I am in trouble - old age I guess. I was spinning cobwebs when I wrote that, I had no idea that it would work in this context. So -- the multi-part tags are valid for constructing arguments feeding into processes, not just for setting tags? I wouldn't (and didn't) guess that. I better go back and re-read the help documents. Thank you. Posted by: Magnus Brading on Mar. 31 2008,13:58 Multi-part fields work for all parsing templates, and all fields in them, yes. ![]() end |