Backup_Repos/beets
1
0
Fork 0
mirror of https://github.com/beetbox/beets.git synced 2025-12-16 05:34:47 +01:00
Code Issues Projects Releases Wiki Activity

link to the advanced guide from "getting started"

Browse source
This commit is contained in:
Adrian Sampson 2013-05-19 17:43:10 -07:00
parent 45baa6efe1
commit f3962e6275
2 changed files with 10 additions and 32 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/guides/advanced.rst
View file

@ -5,9 +5,9 @@ So you have beets up and running and you've started :doc:`importing your
music </guides/tagger>`. There's a lot more that beets can do now that it has
cataloged your collection. Here's a few features to get you started.
Most of these tips involve :doc:`plugins </plugins>` and fiddling with beets'
:doc:`configuration </reference/config>`. So use your favorite text editor
create a config file before you continue.
Most of these tips involve :doc:`plugins </plugins/index>` and fiddling with
beets' :doc:`configuration </reference/config>`. So use your favorite text
editor create a config file before you continue.
Fetch album art, genres, and lyrics

36
docs/guides/main.rst
View file

@ -152,9 +152,8 @@ metadata for every album you import. Option (a) is really fast, but option (b)
makes sure all your songs' tags are exactly right from the get-go. The point
about speed bears repeating: using the autotagger on a large library can take a
very long time, and it's an interactive process. So set aside a good chunk of
time if you're going to go that route. (I'm working on improving the
autotagger's performance and automation.) For more information on the
interactive tagging process, see :doc:`tagger`.
time if you're going to go that route. For more on the interactive
tagging process, see :doc:`tagger`.
If you've got time and want to tag all your music right once and for all, do
this::
@ -228,35 +227,14 @@ you have::
Artists: 548
Albums: 1094
Playing Music
-------------
Beets is primarily intended as a music organizer, not a player. It's designed to
be used in conjunction with other players (consider `Decibel`_ or `cmus`_;
there's even :ref:`a cmus plugin for beets <other-plugins>`). However, it does
include a simple music player---it doesn't have a ton of features, but it gets
the job done.
.. _Decibel: http://decibel.silent-blade.org/
.. _cmus: http://cmus.sourceforge.net/
The player, called BPD, is a clone of an excellent music player called `MPD`_.
Like MPD, it runs as a daemon (i.e., without a user interface). Another program,
called an MPD client, controls the player and provides the user with an
interface. You'll need to enable the BPD plugin before you can use it. Check out
:doc:`/plugins/bpd`.
.. _MPD: http://mpd.wikia.com/
You can, of course, use the bona fide MPD server with your beets library. MPD is
a great player and has more features than BPD. BPD just provides a convenient,
built-in player that integrates tightly with your beets database.
Keep Playing
------------
The :doc:`/reference/cli` page has more detailed description of all of beets'
functionality. (Like deleting music! That's important.) Start exploring!
This is only the beginning of your long and prosperous journey with beets. To
keep learning, take a look at :doc:`advanced` for a sampling of what else
is possible. You'll also want to glance over the :doc:`/reference/cli` page
for a more detailed description of all of beets' functionality. (Like
deleting music! That's important.)
Also, check out :ref:`included-plugins` as well as :ref:`other-plugins`. The
real power of beets is in its extensibility---with plugins, beets can do almost