This topic has been viewed in excess of 75 times however there has been no response from JRiver reps.
And
here, no response to these users either.
I
posted on this a while back. Granted, the responses in this thread provided a workaround to play M4A files on my device but I never received any answer regarding MC's support of enchanced M4A files (i.e. files with bookmarking).
To summarize my post, M4A files were being transferred to my iPod as video files which is incorrect since
M4A denotes "audio" if I'm not mistaken. The files in this state on the iPod do not play. I was then told to update MC preferences to 'treat" M4A files as "audio" and not "video". I don't exactly recall where this was done but I did that and was able to play the audio on the iPod however, the bookmarks are not supported.
On the same system, I tested transferring the same files to the iPod through iTunes (my favorite application...not). But in this case, iTunes delivered. Delivered meaning that the M4A file was transferred to the iPod, as an audio file with bookmark functionality (and bookmark imaging) intact.
On the same system, iTunes is able to play the file with the bookmarking images. MC is able to play the file but does not display any of the bookmarking images.
MC as of the latest version, does not appear to support this. Now, I'm not all that concerned with MC 11 actually playing these files with the bookmark support, but I would prefer it if MC's transfer process didn't corrupt the M4A files and simply transferred them to my iPod fully intact.
My question is, will development acknowledge/investigate this particular issue and whether or not ultimately it will be supported? At the very least, investigate/resolve the issue where the files are being transferred to the device in a state such that the bookmarks are disabled/corrupted? I don't believe it's a stretch for people to view MC as a "replacement" for iTunes (a $40 replacement). This is evidenced by the number of people at the iLounge forums that recommend MC 11 highly for that very purpose. As such, I don't think it's an unreasonable expectation that enhanced m4A files would be handled without the awkward results users are experiencing now. But I'm getting the sense, not noticing any effective response to this issue, that MC dev / product management is not terribly concerned with this.
Some feedback on this would be appreciated.