Backup_Repos/beets
1
0
Fork 0
mirror of https://github.com/beetbox/beets.git synced 2026-01-06 16:02:53 +01:00
Code Issues Projects Releases Wiki Activity

update Tomahawk blog post

Browse source 
- New screenshot
- No longer need to check out the source from GitHub
- New config filename
This commit is contained in:
Adrian Sampson 2013-05-19 11:28:15 -07:00
parent 6e43792e24
commit 964bd7772c
2 changed files with 6 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
_posts/2012-08-03-tomahawk-resolver.md
View file

@ -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

BIN
images/tomahawk-resolver-config.png
View file

Binary file not shown.
Side by side Swipe Overlay

Before

Width:  |  Height:  |  Size: 25 KiB

After

Width:  |  Height:  |  Size: 44 KiB