Not to dismiss your hypotheses as useless, and sorry if this comes out as rude, but do you have details to back up your analysis? Android version, media player software used, specific rips you think have incorrect metadata, screenshots highlighting the mistake or unreadability, and other such bits of information?
1. Either Android or Metadata itself was corrupt, some android can't read tag
I'm not an Android expert by any stretch of the imagination, and knowing which Android version or software where the 'problem'―let's assume it exists for now―occurs wouldn't automagically give me the ability to identify the underlying causes, but this is pretty broad: if metadata pertaining to a certain file is readable on some OS but not others*, and that's already hard to fathom, then at best it may signal OS incompatibilities. But if you mean it works with certain Android version(s) and not others, then it starts to make no sense.
The closest possible conclusion I can think of is that one version has full UTF-8 character encoding support whereas the other lacks it. However, in most cases, this wouldn't break the entirety of the metadata and failing to properly decipher special characters would only replace them with weird symbols. And since ASL uses romaji, this would apply only to songs with special characters (like ☆ or ♥) in the title. If it's the metadata itself that's somehow 'corrupt', then it shouldn't be readable anywhere.
* For the record, I've tried playing ASL rips on Windows Vista, Windows 7, Debian 7 and Ubuntu 12.04, using a variety of media player programmes such as foobar2000, Winamp, Rhythmbox and others, all of which render the metadata just fine. I've also played our MP3 rips, although never FLAC, on Android 2.2.
2. the lossless (flac) compression itself was not compatible with some of metadata tag or
Not possible. If this were even close to being true then
all our other rips would have the same problem as we only release in FLAC for lossless. And we individually tag the metadata for each file as opposed to using CUE sheets.
3. software related with ripping + metadata write.
Same as the above: We use foobar2000 not just for transcoding and tagging purposes** but also as a general-purpose music player. We'd notice it before anyone else if our rips transcoded and tagged by foobar turned out to have unreadable metadata. You could suspect that files transcoded/tagged by foobar only work fine with foobar itself and not with other media player software, but as I previously noted, I've tried playing our rips with various programmes on various OS and encountered no such a problem.
** Some of us have, on occasion, used Mp3Tag in lieu of foobar2000 for tagging purposes. That still doesn't mean using Mp3Tag is bound to cause problems as we'd still be the first to notice. Oh, and by "some of us", I mean two or three people, meaning the vast majority of our rips never got touched by Mp3Tag at all. Finally, as we're harmonising our workflow, we've mostly abandoned software not widely used by others.
for conclusion i just want to ask how ASL or any forum member set their metadata for FLAC compression, since ASL release metadata was working fine with my winamp and android music player
We just use foobar2000 to edit file properties. Yes, it's that simple. For transcoding/compression, we merely use foobar2000's built-in conversion feature with binaries based on free encoders (
LAME and
FLAC). Nothing complicated.
some of example working metadata like Trust in You - sweet Arms but when i try writing my own rip, metadata was not tagged correctly (missing album art and so on) , i'm using EAC usually and with ID3v2, if that was wrong maybe someone can enlighten me with this metadata tagging
What do you mean by "writing" your own rip? By EAC, are you referring to the software or the general term to refer to uncompressed lossless? And were you tagging an MP3 file with ID3v2? How about some screenshots? More information is necessary.
