odd. yes, looking more closely through the edit table, I believe I was mistaken when I stated that no changes were saved.
Looking closer, it appears that:-
-
Save Changes has worked on MP3s (<5% of total) where album art was added to tags by recent Musicbrainz Autocorrect process
-
Save Changes also worked on FLACS where album art was not successfully added to tags by recent Musicbrainz Autocorrect process, but where edits were made to other fields, either by hand or Autocorrect.
-
Save Changes has not worked on FLACS where album art was successfully added to tags by recent Musicbrainz Autocorrect process.
As a further experiment, I deleted the recently added album art data from artwork field in a single FLAC file where I know that other fields in this track were also modified in recent edits, then highlighted the single file and tried Save Changes from context menu.
This Save worked, suggesting that something is choking specifically when trying to Save Changes on those FLAC files where album art has been added to artwork field.
Two more small possible clues: when doing the single file Save Changes where no data in artwork field, it was very, very slow. Spinning blue wait icon sat there for maybe sixty seconds, and only disappeared when I clicked away to a different application then click back to Jaikoz.
Also, instead of main menu Save Changes on entire table, I tried as a final experiment a single file, context menu Save Changes on another FLAC track, this time with new artwork data still there. The file did not save, and the error message came up and whole program froze for a considerable time, resumed response only after several clicks into and back from other apps. Don’t know whether this is significant.
Seems Jaikoz is possibly having a hard time saving any changes in my FLACs, and having fatal trouble saving when the modified data includes artwork.
Again, Jaikoz is running on a mac, OSX 10.8.3, and the music is on a LAN based Linux Samba SMB/CIFS share, which is mounted on the mac filesystem. I tend to doubt its a file permission issue, since other apps on mac have no problem writing to this share.
Its a puzzler. Any more ideas?