Skip to content

Use Mopidy API directly #16

@ndarilek

Description

@ndarilek

I'm struggling a bit with some aspects of this as implemented:

  • If I say an exact song name, it often doesn't get played.
  • The playlists seem a bit arbitrary. If I say "Play ", for instance, I hear the same album by that band, but I have lots of their albums and the choice of which gets played feels arbitrary.
  • I don't know how to target specific songs or albums. Further, if an album and song are named the same thing, I don't know of an easy way to disambiguate them.
  • It isn't clear that updating the Mopidy library would propagate those changes to Mycroft without a restart, or at the very least a refresh of this skill.

Would you accept a PR that does the following?

  • Ports the existing functionality to Mopidy's Python API.
  • Creates intents for playback, with optional selection of specific songs/albums (I.e. "Play the album Torn by Evergrey" to specify searches of the library.)

I'm happy to do the work, I just figure there's a reason you scrape the library and create intents manually. Maybe it's so fuzzy text searches can work, but if so I wonder how much of a performance hit it is to fetch the data each time and search that?

Thanks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions