Baptiste Coudurier <[email protected]> added the comment:

Hi,

On 04/28/2010 07:26 PM, skottish wrote:
>
> skottish<[email protected]>  added the comment:
>
> When you posted before that the issue that I originally brought here should 
> be fixed in
> r20453, it was. This is to say that the patch that you had provided then 
> corrected the
> malformed metadata produced by Apple.

No, the commit just changed the name of the metadata key. Nothing was 
malformated by Apple.

 > this brought the files back into spec.
>
> At some point a few months later, I started to notice that the metadata of 
> any new m4a
> file that I brought onto my system encoded to Apple's specs were no longer 
> working
> properly with MPD. Since FFmpeg is the only playback engine that I use for 
> MPD, we came
> full circle to where we were before.
>
> The patch that I posted about in msg9753 re-corrects the issue, but the patch 
> is falling far
> behind FFmpeg's development.

This patch modifies several unrelated things. You reported one issue, I 
believe the issue you specifically reported is fixed.

If you have another issue, report it in a detailed manner.
If one developer of MPD could help that would be nice.

> With that being said, this is how to reproduce the results:
>
> I just rebuilt FFmpeg without applying the latter patch. I removed my mpd.db 
> file, restarted
> MPD, and allowed it to rebuilt the database. The only files that show up in 
> my collection
> now are mp3 or vorbis. This is far less than 1% of my collection.
>
> If I apply the patch, remove the mpd.db file, restart MPD, it will rebuild 
> the library and all of
> my files will be there. This problem exists, it seems to me, because MPD 
> expects
> metadata to be part of the standard and not some crap that Apple puts out.
>

Well, I'm sorry but is not a correct and detailed bugreport. I don't use 
"MPD" and I don't know what you mean.

________________________________________________
FFmpeg issue tracker <[email protected]>
<https://roundup.ffmpeg.org/issue1501>
________________________________________________

Reply via email to