Some embedded artwork images not displayed under MacOS Finder and iTunes on both Windows/MacOS.
Tests:
If artwork not displayed in iTunes it will not displayed in any standart MacOS applications
Worked only on some MP3 files. Changing of file format ( JPEG, PNG ), image source (local disk, copy/paste) or taking over image not helped
Artwork added from over software ( e.g. iTunes ) correctly visible and displayed in Jaikoz.
Hi, try changing the Version in Jaikoz from to V23 if using v24.
Also check that Preferences:Save:Compatability:Do not Unsynchorinize tags is unchecked.
Then try Force Save to resave the files.
If you still cannot get it working please email support and example of a file that doesn’t work.
Noted you raised http://jthink.net:8081/browse/JAIKOZ-689#comment-11609
First of all I opened the file in Jaikoz, and just did File:Force Save - this fixed the problem the metadata including artwork could now be seen in Finder and iTunes.
So my first question is did you actually try this, if you did and it didn’t work it must because your preferences are set differently to the defaults. I had a closer look at the files and noticed that all the text fields were stored using UTF-16 rather than ISO-8859-1 (which is the default for ID3v23). If I go into Jaikoz and set Preferences:Save:ID3 v2 Tag:Default Text Encoding to use UTF-16, and Force Save again then the file metadata is no longer visible in Finder and iTunes.
So I assume you changed this option and that is what breaking things for you.
Problem found, yet another bug in iTunes !
If you set default text encoding to UTF-16 within Jaikoz that is used for all frames that allow you to specify a text encoding, this includes the coverart frame (APIC) which uses it for the description field.
iTunes will not display the artwork if you have the textencoding field set to UTF16 unless you actually encode the text as ISO8859-1, which is what iTunes does.
The workaround Ive made for Jaikoz 5.5.0 is for Jaikoz to always use ISO-8859-1 for this frame, if this means the description cannot be encoded then we set the description to blank, this is not a major issue as by default the description is blank anyway.