by REIKA » Wed Apr 30, 2008 5:23 pm
1) MM can read the tag of the wav file written by other applications.
2) Other applications cannot correctly read the tag of the wav file if tag is edited with MM.
3) MM cannot also read the tag of this file when the wav file edited with MM is deleted from the library once, and it registers in the library again.
I examined what had happened with BinaryEditor.
Other applications write tag with Shift_JIS code.
On the other hand, MM seems to be writing tag with UTF8 code.
In the RIFF tag of the wav file, it is sure not to be provided for character-code.
Therefore, it must be usual to use the character-code of the default of the system (As well as ID3V1).
To begin with, it is out of the question that MM cannot read the tag though it was written by MM.
1) MM can read the tag of the wav file written by other applications.
2) Other applications cannot correctly read the tag of the wav file if tag is edited with MM.
3) MM cannot also read the tag of this file when the wav file edited with MM is deleted from the library once, and it registers in the library again.
I examined what had happened with BinaryEditor.
Other applications write tag with Shift_JIS code.
On the other hand, MM seems to be writing tag with UTF8 code.
In the RIFF tag of the wav file, it is sure not to be provided for character-code.
Therefore, it must be usual to use the character-code of the default of the system (As well as ID3V1).
To begin with, it is out of the question that MM cannot read the tag though it was written by MM.