Yoni Rabkin <[email protected]> writes:
Ian Eure <[email protected]> writes:
Yoni Rabkin <[email protected]> writes:
Aleksas Tunikas <[email protected]> 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.
IMO, MPD/EMMS and beets are complimentary -- they do very
different
things, in different ways. I think some tighter integration
might be
nice, but I don’t think all the stuff beets does makes sense to
have
in EMMS.
The more I think about it, the more I agree. What would that
integration
look like in your opinion?
That’s a good question. Off the top of my head, I think the most
obvious is using the beets library as the backend for the EMMS
browser, which I think would be a nice bridge from beets into
EMMS. Possibly also a way to load beets-managed playlists.
It’d be very nice to have an Emacs UI for `beets import', but I
don’t think that’s something that makes sense to have in EMMS.
— Ian
