Hello.
I think i have discovered a very serious problem with Amarok.When i change the tags of a FLAC file using amarok,the file becomes corrupted!There is no audible change,or quality loss,but when i decompress the flac file:

flac -t bad2.flac

Ι get something like this:

bad2.flac: testing, 96% complete

bad2.flac: ERROR while decoding data
           state = FLAC__STREAM_DECODER_END_OF_STREAM

So,be very carefull with tagging and flac files.You may permanently damage you collection!
Should i fill a bug report?

I am using amarok 1.4.3 (amarok-1.4.3-14.guru.suse101 for 686) ,KDE 3.5.4 "Level A",taglib-1.4-20, and linux 2.6.13

If true, it would be a TagLib problem (as TagLib handles all metadata for Amarok). Please submit a bug report for TagLib at http://bugs.kde.org.

Konqueror also uses taglib(if I am not mistaken) but it wokrs fine.The bug is fully reproducible on my PC:

I have a flac file named "original.flac" (I am using flac 1.1.2)

>flac -t original.flac
original.flac: ok

>metaflac original.flac --list
METADATA block #0
  type: 0 (STREAMINFO)
  is last: true
  length: 34
  minumum blocksize: 4608 samples
  maximum blocksize: 4608 samples
  minimum framesize: 4408 bytes
  maximum framesize: 10063 bytes
  sample_rate: 44100 Hz
  channels: 2
  bits-per-sample: 16
  total samples: 5234688
  MD5 signature: 5a46aa3ef2a129c9f3f436ef73d97ac6



Then I use konqueror to insert the string "123456789" to the "TITLE" tag.The resulting file is fine:

>flac -t original_tags_with_konqueror.flac
original_tags_with_konqueror.flac: ok

>metaflac original_tags_with_konqueror.flac --list
METADATA block #0
  type: 0 (STREAMINFO)
  is last: false
  length: 34
  minumum blocksize: 4608 samples
  maximum blocksize: 4608 samples
  minimum framesize: 4408 bytes
  maximum framesize: 10063 bytes
  sample_rate: 44100 Hz
  channels: 2
  bits-per-sample: 16
  total samples: 5234688
  MD5 signature: 5a46aa3ef2a129c9f3f436ef73d97ac6
METADATA block #1
  type: 4 (VORBIS_COMMENT)
  is last: true
  length: 74
  vendor string:
  comments: 5
    comment[0]: ALBUM=
    comment[1]: ARTIST=
    comment[2]: DESCRIPTION=
    comment[3]: GENRE=
    comment[4]: TITLE=123456789




But if i use amarok to do exactly the same thing,the file gets corrupted! :

>flac -t original_tags_with_amarok.flac
original_tags_with_amarok.flac: testing, 96% complete

original_tags_with_amarok.flac: ERROR while decoding data
                                state = FLAC__STREAM_DECODER_END_OF_STREAM

>metaflac original_tags_with_amarok.flac --list
METADATA block #0
  type: 0 (STREAMINFO)
  is last: false
  length: 34
  minumum blocksize: 4608 samples
  maximum blocksize: 4608 samples
  minimum framesize: 4408 bytes
  maximum framesize: 10063 bytes
  sample_rate: 44100 Hz
  channels: 2
  bits-per-sample: 16
  total samples: 5234688
  MD5 signature: 5a46aa3ef2a129c9f3f436ef73d97ac6
METADATA block #1
  type: 4 (VORBIS_COMMENT)
  is last: true
  length: 74
  vendor string:
  comments: 5
    comment[0]: ALBUM=
    comment[1]: ARTIST=
    comment[2]: DESCRIPTION=
    comment[3]: GENRE=
    comment[4]: TITLE=123456789

Are you sure it is a taglib bug?

I couldn't reproduce this in my PC, I use Amarok to tag all my FLAC, so it would have been a huge problem, but fortunatelly my files tst OK.
Amarok 1.4.2
TagLib 1.4
Flac 1.1.1

What versions of these packages are you using?

I have tagged many files with amarok with no problems too.Only a very small proportion gets corrupted.
I will give you the links to the files I mentioned in my previous post:

http://users.auth.gr/~cfarinis/original.flac
http://users.auth.gr/~cfarinis/original ... marok.flac
http://users.auth.gr/~cfarinis/original ... ueror.flac

The versions of the packages are:
amarok 1.4.3-14.guru.suse101
taglib 1.4-20
flac 1.1.2
kde 3.5.4

Ok, I can confirm that the problem is amarok 1.4.3!!
Using amarok 1.4.2 I tagged your file and it was binary identical to the ones tagged by you with konqueror and it didn't have errors.
I upgraded to 1.4.3 to test and I got the same problem as you when I tagged the file. (Amarok is the only program I updated)
I'm not sure what's the problem but for now I think it would be good to stay away from this version. Did you submit a bug report about this?

Another interesting point is that tagging the file back in amarok 1.4.2 fixes the file.

p.s.: I've lost my collection DB in this upgrade -> downgrade, oh well... 

Also note that the file processed with amarok has exactly the same size as the original file(and there is no padding block).This not right.

I submited a bug report for Amarok.

Hi!

I would like to know how I can repair my corrupted flacs? I try retagging the files after upgrading to amarok 1.4.4 (the problem is solved with this version) and it still remains... I also used "Ex falso" or "Easytag" but it doesn't change anything!

Thank you for your help! I have many albums corrupted...

Should I conclude there isn't a solution to "repair" my flacs?

http://phoenix.inf.upol.cz/~lichvarm/affd/

Look for flacdec, binary worked for me.

I ran "flacdec -r filename" on the corrupted file posted on this thread and it decoded it to a playable wave.
The did a "flac -e filename" on the wave and became a playable flac again. 

But as always, use at your own risk (don't know if music is totally recovered without glitches)!

Bye, tira.

Thank you!