[Abcde-users] FW: Abcde and aiff

[Dry Martini Holding Company]

That would be because I forgot to attach them. Here they are.


Robert

On 4/27/25 15:59, Dan Hargens wrote:
> I see no screenshots here...
>
> On Sun, Apr 27, 2025 at 2:52 PM Dry Martini Holding Company via 
> Abcde-users <abcde-users at lists.einval.com> wrote:
>
>     Here are two screenshots of two files viewed through the kid3
>     program.
>     The one titled Blue works properly. The other titled concrete does
>     not
>     work (does not show up in the album or artist listing). I see that
>     the
>     one that is working is ID3v2.3.0. The other is, ID3v2.4.0. There
>     is lots
>     of album information missing on the file that does not work properly.
>
>
>     Robert
>
>
>     On 4/25/25 21:54, Gabriel Rosenkoetter via Abcde-users wrote:
>     > On 2025-04-25 21:47, josh via Abcde-users wrote:
>     >> On 26/4/25 11:38, Dry Martini Holding Company via Abcde-users
>     wrote:
>     >>> I have no doubt that MPD plays the aiff files and displays the
>     >>> metadata properly. The part of the music server that is not
>     working
>     >>> properly is the the display by "album", album artist, and artist.
>     >>> All of this info is stored in a DB. The DB is updated after any
>     >>> additions or deletions are made. In my case, the only part that
>     >>> diplays a newly added album, is the "alpha" order listing.
>     >> It would really help to see the metadata from a track that MPD
>     >> displays correctly and the metadata from an abcde ripped track
>     that
>     >> MPD does not display. Please show the out of the following:
>     >>
>     >> For a track that MPD displays metadata correctly: ffmpeg -i
>     song.aiff
>     >>
>     >> For an abcde-ripped track that MPD does not display metadata:
>     ffmpeg
>     >> -i abcde-song.aiff
>     >
>     > Huh. I agree that that output would be useful to help understand
>     this
>     > problem, but I read Robert's statement there slightly differently.
>     >
>     > I think that we (josh, Jason, and I) have been assuming that MPD
>     was
>     > never parsing any of the metadata in the id3v(whatever) tag (or
>     that
>     > abcde was not applying those tags to AIFF files for Robert), but if
>     > MPD is able to display that information, but unable to index
>     based on
>     > it, that's a different problem.
>     >
>     > I'm back to thinking that this might be a problem for whoever's
>     > responsible for maintaining MPD.
>     >
>     >
>     > _______________________________________________
>     > Abcde-users mailing list
>     > Abcde-users at lists.einval.com
>     > https://lists.einval.com/cgi-bin/mailman/listinfo/abcde-users
>
>     _______________________________________________
>     Abcde-users mailing list
>     Abcde-users at lists.einval.com
>     https://lists.einval.com/cgi-bin/mailman/listinfo/abcde-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.einval.com/pipermail/abcde-users/attachments/20250427/b8ab1a80/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: blue.png
Type: image/png
Size: 83830 bytes
Desc: not available
URL: <http://lists.einval.com/pipermail/abcde-users/attachments/20250427/b8ab1a80/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: concrete.png
Type: image/png
Size: 113893 bytes
Desc: not available
URL: <http://lists.einval.com/pipermail/abcde-users/attachments/20250427/b8ab1a80/attachment-0003.png>