Re: integration with beets

[Yoni Rabkin]

"Fran Burstall (Gmail)" <fran.burstall@gmail.com> writes:

>>
>> However, it would also be good if you can list the features of beets
>> that you think are missing in Emms. Perhaps we can use that as a way to
>> help roadmap tagging and library management in Emms.
>
>
> For me, the killer feature of beets is its import command:
> * checks and optionally corrects media metadata from musicbrainz and,
> optionally, discogs
> * installs the media in the right dir in your music library

This suggests to me a few potential features (the names are just
suggestions):

emms-tag - Use the beet command line interface to beets from Emms
to correct and update track metadata. One interesting issue which would
come up here is that the underlying services, such as
acoustid/chromaprint, are licensed only for non-commercial use. So while
the software is free software, the services are not. People will have to
go through the process of having beets working with fpalc (the FFT
component of chromaprint).

emms-collate-filename - Modify a track's filename based on its metadata.

emms-collate-directory - Write all tracks with a particular metadata to
an appropriately named directory.

> * takes care of album art for various values of "takes care"

What do you mean by that?

> All of these should be possible to implement in emms...
>
> ---Fran
>
>
>
> On Tue, 14 Nov 2023 at 15:47, Yoni Rabkin <yoni@rabkins.net> wrote:
>
>> Aleksas Tunikas <mail@aleksas.ru> writes:
>>
>> > I want to make the beets plugin 'play' to redirect the output to emms,
>> > by default it already do that, so I must have beed specifying it
>> > somewhere in my system, but it starts a new Emacs instance every time,
>> > what I want instead is that it utilize emacsclient, the syntaxis to put
>> > a custom command is like this: command: /usr/bin/command --option1
>> > --option2 some_other_option (from this
>> > https://beets.readthedocs.io/en/stable/plugins/play.html)
>> >
>> > Or optionally maybe somebody knows where to change those default
>> > settings it appears to be related to the xdg-open explained here:
>> > https://wiki.archlinux.org/title/default_applications
>> >
>> > Meanwhile if I find the answer before somebody pointed out I will report
>> > here.
>> >
>> > Thank you and have a great day!
>>
>> I saw today on IRC that you were advancing with this. Definitely send in
>> a recipe if you figure this out.
>>
>> However, it would also be good if you can list the features of beets
>> that you think are missing in Emms. Perhaps we can use that as a way to
>> help roadmap tagging and library management in Emms.
>>
>> --
>>    "Cut your own wood and it will warm you twice"
>>
>>

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