Importing filepath-propertyvalue pairs

Support
#1

I would like the best way to tag a library from a large (e.g. 1Mb) textfile consisting of a list of filepath-propertyvalue pairs e.g.

S:\TLIB\07798105810046\1\1.WMA Concierto en la luna
S:\TLIB\07798105810046\1\3.WMA Loca bohemia
...

where the filepath is the path of the file that is to have the propertyvalue written to a certain fixed field e.g. Title.

For smaller lists I have imported the entire textfile into the propertyfield and then used string functions to remove all but the matching propertyvalue, but that would be very slow for a 1Mb list.

Thanks.

#2
QUOTE (chrisjj @ Aug 28 2010, 13:55) <{POST_SNAPBACK}>
I would like the best way to tag a library from a large (e.g. 1Mb) textfile consisting of a list of filepath-propertyvalue pairs e.g. 
S:\TLIB\07798105810046\1\1.WMA Concierto en la luna
S:\TLIB\07798105810046\1\3.WMA Loca bohemia
...

where the filepath is the path of the file that is to have the propertyvalue written to a certain fixed field e.g. Title.

For smaller lists I have imported the entire textfile into the propertyfield and then used string functions to remove all but the matching propertyvalue, but that would be very slow for a 1Mb list.

Thanks.


Do it as Mp3tag provides it.
On each line of the source file enclose each item into double apostrohes and delimit each item by an unique character to build a CSV like data record line.
For example:
"S:\TLIB\07798105810046\1\1.WMA"|"Concierto en la luna"

Import the file, which contains all the prepared lines, into Mp3tag using "Convert/Textfile - Tag" together with a Formatstring like this:
"%_PATH%"|"%TITLE%"

This should fill the TITLE string into the relating file.

DD.20100828.1920.CEST
Edit. Misspelling on Formatstring corrected.
DD.20100829.0215.CEST

#3

Wow. No mention in the docs that Textfile-Tag actually searches for a match on _path!

Thanks D, but it doesn't work for me e.g.

#4

.....

#5

But it does work if I remove the format string's single quotes:

Thanks!

I guess this failure of single quotes to act special is a bug?

#6

chrisjj, I beg your pardon for the inconvenience.
I've edit the misspelling in my post from above and removed the single quotes.
The single quotes have crept in by my efforts to consistency in Mp3tag scripting too.
As you discovered, the format string rules are partly different from the scripting rules.
(It seems so, that ) ... all characters within a Formatstring, beside the placeholders, are taken "as is", so that an inserted special single character or character string must not be enclosed by single quotes.
Example:
Formatstring: "%_PATH%"|"%TITLE"
... is correct and will fit to ...
Fileline: "S:\TLIB\07798105810046\1\3.WMA"|"Loca bohemia"

DD.20100829.0238.CEST

#7

What we have is some format strings using different rules from others.

e.g. in Convert Text file - Tag and Convert Filename - Tag single quote means single quote, whereas in Convert Tag - Filename and e.g. Action Format value single quote means "Output raw text".

This fits with the fact that the first type doesn't allow scripting and the second does. So I guess this is not a bug after all. But both are lablled the same on the UI - you have to look in the Help to discover there are two different types.

This is confusing and error-prone. I think the UI labels should distinguish the two types e.g. "Format string (not scriptable):" and "Format string (scriptable):".

Suggestion - make UI labelling distinguish the two kinds of Format String
#8

Good point!
My vote +1 for adding this to the UI and into the manual.

DD.20100829.1912.CEST

#9

Why are you using quotes?

%_path% | %title%
also does it.