home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Products
MPTagThat
[Suggestion] Find missing tag info
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="hwahrmann" data-source="post: 477803" data-attributes="member: 10391"><p>yes, looks like the other tag editors skip those comments.</p><p>I can read one of them, but on the second on i'm failing.</p><p></p><p>both comments are UTF-16 encoded and contain Asian characters (Chinese, Japanse, or whatever).</p><p>This isn't the problem, but the second comments contains 1 byte too less and this is causing the troubles.</p><p></p><p>the only way to look at them is using a hex editor. they're somewhere around 340 bytes into the file starting with COMM.</p><p>if you remove everything starting (and including) the first COMM until APIC starts, then you wil be able to read the file.</p><p>i was also successfull by just adding 1 byte to the second COMM frame.</p><p></p><p>another quick solution, until i could fix the issue, would be to use another tag editor, which doesn't fail and remove the ID3 V2 tag and retag it.</p></blockquote><p></p>
[QUOTE="hwahrmann, post: 477803, member: 10391"] yes, looks like the other tag editors skip those comments. I can read one of them, but on the second on i'm failing. both comments are UTF-16 encoded and contain Asian characters (Chinese, Japanse, or whatever). This isn't the problem, but the second comments contains 1 byte too less and this is causing the troubles. the only way to look at them is using a hex editor. they're somewhere around 340 bytes into the file starting with COMM. if you remove everything starting (and including) the first COMM until APIC starts, then you wil be able to read the file. i was also successfull by just adding 1 byte to the second COMM frame. another quick solution, until i could fix the issue, would be to use another tag editor, which doesn't fail and remove the ID3 V2 tag and retag it. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Products
MPTagThat
[Suggestion] Find missing tag info
Contact us
RSS
Top
Bottom
