-Brading Software Message Board
+--Forum: Mp3/Tag Studio Suggestions
+---Topic: Another request started by calberga
Posted by: calberga on Sep. 29 2007,16:18
Would it be possible to allow the following sort of patterns in Direct Tag Manipulation?
Source: <Title>
Destination: <TRASH> (<Comment>)
or
Source: <Title>
Destination: <Title> (<TRASH>)
or even
Source: <Title>
Destination: <Title> (<Comment>)
I know I can do this is a couple of steps, using Create Custom List and Tag from List, but it would be much simpler as a single operation, without having to navigate the directory structure in Tag from List.
Posted by: Magnus Brading on Oct. 01 2007,09:54
The problem with this is that it would require an arbitrary number of source/destination field pairs. Your suggested semantics would be in contradiction to the current source/destination semantics (you have a parse template in the destination field), and also only solve "half the problem", since it would not be able to easily build field contents from several parts (including static added strings).
In the advanced mode of this tool I already have such a "solve half the problem" solution, which can instead build complex contents from multiple full fields + static strings, but instead not perform any parsing of existing field contents.
To be able to add up these two "half the problem" solution into a full solution, there is the problem that an arbitrary number of source/destination fields would be needed, and since this is a relatively messy GUI problem, I settled for the possibility of the extra step through the create list/tag from list combination in these more complex situations.
But I miss this possibility as much as you, it's the part missing from making the tools "complete".
I might give it another shot in the future.
Posted by: calberga on Oct. 01 2007,16:17
Well, another possibility which does not involve climbing the directory trees would be to provide a "dummy" V2 tag, say V2_TEMP, which would only could be deleted simply. Then, one could use it to save the current filename, rename the file from the tag which is to be parsed, tag-from-filename, and restore the correct filename.
The most frustrating part of the create-list, tag-from-list sequence, for me, is the fact that while create-list defaults to putting the new list in the current directory, tag-from-list always starts in the last directory where it was used. This can be anywhere, and always takes some navigation to get to the newly-created list. In addition, if one is trying to keep things clean one must then remember to delete the list when done. I have an embarrassingly large number of ###.txt files scattered through my directories of .mp3 files!
Posted by: Magnus Brading on Oct. 05 2007,20:33
Isn't that what macros are for?
Anyway, thanks for the input and ideas, as always.
One day I will make this final addition to complete a perfectly symmetric circle of mp3 processing.
Posted by: calberga on Oct. 05 2007,23:55
I guess I'm going to have to actually try a macro -- so far I haven't touched the things.
Thanks
Posted by: Magnus Brading on Oct. 06 2007,11:13
Well it's about time then I'd say.
end