Tag editing problem

[simoncn]

Thanks for this analysis of the reason for the problem.

The creation of a second comment block is a bug in dbPoweramp, as the FLAC specification says that only one comment block is allowed.

I would like to see the original file that you think is incorrect. I will PM you instructions for uploading it to my FTP server.

[BlueDog]

That's also a valid point.

From the dBPoweramp R16.2 changelog:

Quote:FLAC tagger would not change tag if FLAC file was missing vendor item in tag (all FLAC files should have these)

FLAC tagger would not write tags if the FLAC file contains 2 Id tag blocks

The second entry seems to break the rules ...

[BlueDog]

Ugh, it's definitely the R16.2 update to dBpoweramp causing this problem and I retract my statement about the file being at fault - other than the vendor string being empty.

I downloaded a previous purchase that I successfully tagged with R16.1 a while ago and tried it with R16.2 which resulted in two comment blocks!

I was going to post a bug report on Spoon's forum but it appears Gussy has already done so ...

Do you still want a file to look at Simon?

[simoncn]

No need for a file now as it seems Gussy and you are a step ahead of me on this.

[BlueDog]

No problem, now I suppose we just have to wait and see what happens over at SpoonHQ.

[simoncn]

I checked the Vorbis comment block specification and there is nothing there that prohibits the vendor string having zero length.

[BlueDog]

That's very true, but I think it being empty is what was preventing earlier versions of dBpoweramp from creating a second comment block. More curiously, it was quite happy to edit the comments before even though the change log suggests it didn't.

A workaround exists for the time being, so I guess we'll have to wait and see what the outcome is ..

Time for a beer or six, methinks.

[Gussy]

Sent a file to Spoon - says he's looking into it....