[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "2045" by Man With a Mission breaks EMMS

From: Yoni Rabkin
Subject: Re: "2045" by Man With a Mission breaks EMMS
Date: Fri, 01 Jul 2022 17:53:07 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1.90 (gnu/linux)

snickerbockers <snickerbockers@washemu.org> writes:

> I just tested it out.  The new commit you made solves the problem, and
> i'm able to successfully import 2045 into my emms library.

Excellent, thank you for the bug report.

> thanks,
> snickerbockers
> "Yoni Rabkin" <yoni@rabkins.net> writes:
>> snickerbockers <snickerbockers@washemu.org> writes:
>>> "Yoni Rabkin" <yoni@rabkins.net> writes:
>>>> Which info backend are you running (the value of `emms-info-functions'
>>>> variable)? My first guess is that `emms-info-native', which is written
>>>> in elisp, is barfing on some encoding.
>>> I'm actually using the exiftool backend.  When I switch to native it
>>> works without any problems.
>>> I did some digging and saw that running exiftool -json on the
>>> problematic file returns the title without quotes:
>>> "Title": 2045,
>>> but when I run it on any file that does not have a numeric name, it puts
>>> quotes around the title.  that might be where the problem is coming
>>> from.
>> Perhaps, but when I changed the title of a track here to a purely
>> numeric value and read it with the exiftool backend, I didn't get any
>> error.
>> However, just to be on the safe side, I've modified
>> emms-info-exiftool.el to ensure that a title will always be read as a
>> string. I pushed that to the main git repo (commit 9120240). Can you
>> please try it out and see if it happens to fix the problem?

   "Cut your own wood and it will warm you twice"

reply via email to

[Prev in Thread] Current Thread [Next in Thread]