Can you list what these new values are, and what value you use for the mean atom (Apple use com.apple.iTunes). I ask because I think if you you a generic name then this may become the defacto standard for these fields - which will be good for Media Monkey - but if you call it something like com.mediamonkey then that would probably put of other applications from using it which would be a bad thing.

Hi thanks for taking this onboard, when will the release with these changes be availble ?

You are right, this wasn't well chosen. I reviewed the implementation and modified it so that '----' atoms are used not only for this purpose, but also for other data that don't have any standard atoms (like ISRC, etc.).

Thanks,
Jiri

When you add an image to a mp4 file, or even edit a text field in a file that already contains an image field MM3 will create an atom called AApr when it adds an image containing the additional child atoms:AlfN,AMIM,Adcp and Apty.

I have two issues with this, firstly is it really neccessary to add these additional fields - the image itself is already held in the covr tag, these fields just seem to contain additional attributes suchas mimetype and description - Im not sure these are really that useful as they will only be recognised in Media Monkey.

Secondly, all standard meta atoms within mp4 contain either
:parent atom, data atom
:---- atom,mean,name,data

see http://atomicparsley.sourceforge.net/mpeg-4files.html

these new Media Monkey fields do not fit into this scheme, and I can see them causing problems for a number of audio players, why dont you just add the fields as '----' fields if you need them ?