Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change MPD 'title' to 'track_name' instead of 'track' to avoid confusion #535

Closed
ZenithDK opened this issue Oct 13, 2013 · 3 comments
Closed
Assignees
Labels
A-core Area: Core layer

Comments

@ZenithDK
Copy link
Contributor

MPD uses "track" to filter on a track number, mopidy converts "title" from the MPD frontend to "track" in the local backend.
Having track mean one thing in the frontend, but something completely different in the backend is confusing.

Edit: Retitled the issue as it was...well, confusing :-P

@jodal
Copy link
Member

jodal commented Oct 13, 2013

Mapping between varying terminology in different systems is a large part of the job of Mopidy, sitting between MPD, MPRIS, tags in files on disk and various music services. Mopidy has to choose its own names for things and map it to all the variations. Staying true to MPD will just take us farther away from the other systems we integrate with.

I don't want to change the name fields on Mopidy's models. Though, I'm open to changing the track field in Mopidy's search queries to track_name. That way, title in MPD maps to track_name in Mopidy, and track in MPD maps to track_no in Mopidy.

@ZenithDK
Copy link
Contributor Author

That was actually what I meant, as we discussed on IRC.
I have no idea how I got into my head that it was track.name and
album.nameI wanted to change, between discussing with you and typing
in the issue :)

I blame too many long days in Korea....

@ZenithDK
Copy link
Contributor Author

ZenithDK commented Nov 3, 2013

Closed via #557

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-core Area: Core layer
Projects
None yet
Development

No branches or pull requests

2 participants