diff --git a/_posts/2012-08-03-tomahawk-resolver.md b/_posts/2012-08-03-tomahawk-resolver.md index d929abbcd..fb6d77f01 100644 --- a/_posts/2012-08-03-tomahawk-resolver.md +++ b/_posts/2012-08-03-tomahawk-resolver.md @@ -7,13 +7,11 @@ Beets is a music library manager---not, for the most part, a music player. It do [Tomahawk][] is one particularly exciting new open-source music player. The magic of Tomahawk lies in its ability to consolidate many sources of music into a single player interface. (It's also a very nicely-designed, cross-platform player even if you don't count the magic.) To integrate new sources of music with Tomahawk, you just have to provide a [resolver][]: a piece of code that searches for music and gives it to Tomahawk to display and play back. -There's now a [beets Tomahawk resolver][beets resolver] that can hook your meticulously organized beets music library into the Tomahawk interface. And it even works remotely, so you can stream music from a server running beets to a different machine running Tomahawk. +There's now a beets Tomahawk resolver that can hook your meticulously organized beets music library into the Tomahawk interface. And it even works remotely, so you can stream music from a server running beets to a different machine running Tomahawk. -To use the resolver, first run the [beets Web plugin][web] on the machine with your music. Just add `web` to your "plugins" line in [~/.beetsconfig][config] and then run `beet web` to start the server. Then, on the machine running Tomahawk (this might, of course, be the same computer), get a copy the resolver repository. For example: +To use the resolver, first run the [beets Web plugin][web] on the machine with your music. Just add `web` to your "plugins" line in your [config file][config] and then run `beet web` to start the server. - git clone git://github.com/tomahawk-player/tomahawk-resolvers.git - -Then, open the Tomahawk settings and add a new service using the "Install from file..." button. Navigate to `tomahawk-resolvers/beets` and choose the `beets.js` file. Then, click the wrench icon next to the beets resolver to configure it: +Then, open the Tomahawk settings and check the beets service. Click the wrench icon next to the beets resolver to configure it: ![Configuring the beets Tomahawk resolver.](/images/tomahawk-resolver-config.png) @@ -21,14 +19,10 @@ You'll need to enter the hostname and port of the beets Web server. (You don't n Tomahawk will now be able to find tracks from your beets library. Type a query into the "global search" box and rock out. -If you have trouble getting the beets resolver to work, try the latest [nightly Tomahawk build][nightly]. Some users have better luck with the cutting-edge version. - -[nightly]: http://download.tomahawk-player.org/nightly/ -[beets resolver]: https://github.com/sampsyo/beets/tree/master/extra/beets-resolver [resolver]: http://www.tomahawk-player.org/resolvers.html [Tomahawk]: http://www.tomahawk-player.org/ -[bpd]: http://readthedocs.org/docs/beets/-/plugins/bpd.html -[web]: http://readthedocs.org/docs/beets/-/plugins/web.html -[config]: http://readthedocs.org/docs/beets/-/reference/config.html +[bpd]: http://beets.readthedocs.org/page/plugins/bpd.html +[web]: http://beets.readthedocs.org/page/plugins/web.html +[config]: http://beets.readthedocs.org/page/reference/config.html [git]: https://github.com/sampsyo/beets [mercurial]: https://bitbucket.org/adrian/beets diff --git a/images/tomahawk-resolver-config.png b/images/tomahawk-resolver-config.png index 710366525..4b7b3df27 100644 Binary files a/images/tomahawk-resolver-config.png and b/images/tomahawk-resolver-config.png differ