1 |
Barry Schwartz posted on Wed, 12 May 2010 16:18:57 -0500 as excerpted: |
2 |
|
3 |
> [...] on account of Amarok. [...] I myself would have been reluctant |
4 |
> to tie my software to anything as cumbering as mysql. |
5 |
|
6 |
This isn't a solution for everyone, YMMV, etc, particularly for those who |
7 |
actually use all the Amarok fancy features, but for me, most of them were |
8 |
just bloat, and when amarok decided to go with a mysql feature that at the |
9 |
time didn't even work properly on amd64, I decided it was time I find a |
10 |
less bloated and complicated to keep working music player. Again, YMMV. |
11 |
|
12 |
I ended up choosing mpd, music player daemon, here, because it has all |
13 |
sorts of front ends, including command line, ncurses, gtk, qt (both 3 and |
14 |
4), kde, even a web based front-end so you can control it remotely. I |
15 |
didn't use all those but did merge mpc (command line), the two ncurses |
16 |
frontends, and qmpdclient (qt4), as well as mpd itself. At the time I was |
17 |
still running qt3/kde3, so I merged one for that too, but of course it's |
18 |
now unmerged. |
19 |
|
20 |
Basically I traded a bunch of features I didn't use anyway, plus the kde3 |
21 |
amarok visualizations which I still miss but which the kde4 version didn't |
22 |
have at the time anyway, for a **MUCH** simpler and less troublesome to |
23 |
maintain install, and a player that can be started at bootup and |
24 |
controlled from the command line if desired, regardless of whether X is |
25 |
running or not. |
26 |
|
27 |
There were a couple other more traditional ncurses based players I looked |
28 |
at too, with the idea of killing the X dependency. If I hadn't decided on |
29 |
mpd due to its multiple front-ends, I'd have likely chosen one of those, |
30 |
and simply run it from a VC or a konsole window. One of them even offered |
31 |
a disconnectable control interface, so I could have started it in a |
32 |
konsole window, then shut down the controller, konsole, KDE and X, and had |
33 |
it still playing. That was the runner-up to mpd. But mpd by virtue of |
34 |
its front-end and daemon design did that too, plus had multiple front-ends |
35 |
to choose from including graphical ones if I was running X, so that's what |
36 |
I chose. |
37 |
|
38 |
So anyway, what I'm saying is that there /are/ alternatives to amarok. |
39 |
They may be worth considering, particularly if you're not using all the |
40 |
fancy amarok features anyway. They are CERTAINLY less complex and |
41 |
therefore less trouble to keep "just working". But if you're using all |
42 |
the fancy amarok features, particularly the database backed ones, it may |
43 |
very well be worth the hassle of keeping it working, to continue to use |
44 |
those features. Your computer, your music, your decision. =:^) Just be |
45 |
aware that amarok isn't the only player out there, and don't artificially |
46 |
constrain your choices. No use going to all the repeated hassle of |
47 |
keeping it working, if you're not using the fancy features that make it so |
48 |
complex and hard to keep working in the first place. |
49 |
|
50 |
-- |
51 |
Duncan - List replies preferred. No HTML msgs. |
52 |
"Every nonfree program has a lord, a master -- |
53 |
and if you use the program, he is your master." Richard Stallman |