Verbose option

[squell]

Verbose option

[squell]

Could you copy the tag (e.g. using 'id3 -2 --duplicate test.mp3 foo' ) to an empty file and attach it here? Or if you prefer, send me a small original file by email which triggers this. Thanks!

[J-P-]

@squell
Emailed file. Thanks.

[squell]

I'm unable to reproduce it; on both Windows and Linux id3 shows the same data with or without -v.

What system are you on, exactly? If you're on Windows, what is the 'system locale for non-Unicode programs'? (You can find that under Control Panel -> Region & Languages -> Administrative).

[J-P-]

@squell
OS: Windows 7 / current
Locale for non-Unicode: EN (US)
Don't know what else to say, except that it is reproducible with that and other files.
The transfer option, -D, does work well and as expected.

[squell]

1. And if you run 'id3 -v' on the exact file you sent me, you get the same behaviour reported?

2. Also, do you really see a "blank" field at "POPM", or do you see "<binary data>"? (This is a hardcoded ASCII string in the program; I can't think of any reason it should not show up)

3. What happens if you run id3 -q "%_{TALB}" test.mp3 ?

[J-P-]

@squell

1. Yes.
2. The first report was a copy & paste from the Windows CMD Console.

3. 02—ALBUM (copy & paste)

Assuming it worked, on my end, as expected, how could one import the dump—en masse—to the mp3? Or, do I have to parse each line?

[squell]

Thanks! I don't understand this bug. When I have more time, I'll prepare a version of id3 that we can use (hopefully) to hunt this bug down. I'll also try some more Windows machines in the meantime to see if I can reproduce it myself.

[J-P-]

@squell
Thanks.
This is not that critical, as I can get the values individually.
Assuming a dump worked on my end as expected, how could one import the dump—en masse—to the mp3? Or, do I have to parse each line?