Before amaroK was born, most KDE users were stuck with XMMS; others would even run console-based audio players. Now those days are over. amaroK, written for the KDE desktop environment with its slick GUI and plugable, engine-independent audio capabilities is coming to a computer near you!
amaroK is the first KDE application to use the GStreamer Multimedia Framework without any dependency on external bindings. amaroK can also integrate with xine so you have the freedom of choosing your own flavor.
With version 1.1 there are many exciting changes that make using amaroK even more fun. Here are some of the features that you will simply love :
- Fully Integrated with KDE: Play from your Samba share with smb:/, or use the fish KIO slave to play from a remote host.
- Simple and Elegant: Collection-based system where you can choose songs from a variety of criteria, including artist, most played, never played, etc.
- Stream Support: Listening to online radio has never been easier. Just load the playlist file and it starts playing.
- Engine Independence: Ability to use GStreamer or xine. (There is also aRts engine but it is not ported to the new engine architecture yet).
- Improved Crossfade: Crossfading with customizable fade-in/fade-out durations now works for GStreamer engine too
- Inline tag editing: Tag your music while you play it.
- MusicBrainz support for tag editing: No voodoo needed for tagging your music, just click the MusicBrainz button and it will get the song information from the online database.
- Album cover support: If you have album covers in your music directory amaroK will automatically load them - better yet, amaroK can automatically download album covers from the Internet!
- Multimedia Keyboard Friendly: If you happen to have extra multimedia buttons on your keyboard, using amaroK is even more fun. Just use KHotkeys to map those special buttons to amaroK's dcop functions (like play/pause/volume up/volume down and many more)!
- On-screen Display: amaroK can optionally announce the currently playing song using its smart and stylish on-screen display.
So give amaroK a spin today! You won't be disappointed and that is guaranteed. Fire up amaroK, start playing your favorite songs, and visit the amaroK development squad @ irc.kde.org #amarok. Tell us why you just love amaroK, or your killer new idea for it. We are waiting for you!
Comments
The path to a better way of life is to not use aRts at all! You should use amaroK with xine or GStreamer with direct alsa output instead, as we recommend.
If your soundcard does not provide hardware mixing, the natural solution is to use the dmix plugin for alsa. It allows you to run several audio applications at the same time, without the need for a clunky soundserver in between.
Information on dmix is available here:
http://opensrc.org/alsa/index.php?page=DmixPlugin
Your advice + a gentoo wiki on dmix+alsa and now I am free from sound server troubles!
I'd switch to either using GStreamer (what I use) or the XINE engine. Also, I'd recommend disabling the sound server, as it's not really all that useful these days.
Really, if you get right down to it, I'm guessing that aRts was adopted and adapted mainly to compete with ESD (which sucks worse than aRts.) GNOME moved away from ESD; I think it's time to ditch the notion of crummy software-based mixing and synthesis. aRts was a neat idea, but we've not really seen any improvement for quite a while now.
> Really, if you get right down to it, I'm guessing that aRts was adopted and adapted mainly to compete with ESD (which sucks worse than aRts.)
Nothing of the sort. In KDE1, we had KSoundServer which was quite akin to ESD.
> aRts was a neat idea, but we've not really seen any improvement for quite a while now.
Yes, arts is already pretty much depreciated. kdemm is the next generation KDE infastructure. This time, we aren't going to make the mistake of implemeting our own backend stuff; we'll let people like gstreamer and nmm do that.
The reason amarok has been the only player/orginzer/jukebox that I have stuck with is that it combines all the goods in one place. Mind you I am not saying that those feutures have been implemented/represented(GUI wise) in the best possible way, but it still has them while others don't. I would love to use Juk but it cannot handle my mp3 collection (40,000+ mp3s) without getting stuck for sometimes up to a minute before it starts responding again. I use Juk to do my mp3 tags but now that almost everything in my collection has tags amarok is great. The album art manager needs work though:
a) it should be configurable what the name of the file should be (aka Folder.jpg, Artist.jpg, whatever)
b) it should be able to place the jpeg in the album directory instead of its own ~./kde/share/apps/amarok/albumscovers....
c) it should scan for files already located in the folders.
I have images for almost half of my collection. The context tab displays the art beutifuly but the mng doesn't even get phased...
Overall though amarok is my choice of player so far. I have tried madman, yammi, and juk.
Btw if you ever wanted to be able to access your music from home check out http://www.gnump3d.org I was using that before I get my hands on amarok. I still use it from my office but no longer while I am at home. There is only one thing I am missing in amarok: ratings. I love to rate my songs, got hooked on it with my ipod. Talking about ipod can we get an ipod mngr for amarok too... that would great.
Keep on coding.
a) sorry, this is currently not possible - we might think about that once implementing the image database in sqlite.
b) we're not allowed to do this because of amazon licensing issues - sorry.
c) it does. we'll add mng support.
ratings? an intelligent rating system is already implemented in amarok, rating songs manually will follow.
regards,
muesli
I used xmms, then mp3kult (great app, which sadly was never updated to KDE3.) Then I discovered juk. But my MP3 collection kept on growing...
I now switched from juk to amarok because juk is just inbearably slow with a large collection of music. Startup times of several minutes with just 8000 MP3 on an Athlon-600 are a joke (with an existing database!!). Also the app freezes frequently for several seconds. After shutting juk down it consumed 100% CPU for minutes. Just unusable.
Rhythmbox crashes too much on invalid files. Also I tend to avoid GTK apps. The complete lack of KDE integration turns me off.
Amarok-1.1 is also still a little unstable for me, but I already like it better than juk. Great UI, much faster, I love the cover manager. This looks like a winner!
I agree that players need to be faster when loading the library, but rhythmbox has improved much of late and mine doesn't crash anymore. In fact, mst "rhythmbox crashes" are actually gstreamer problems now, and the ones I have are probably the result of mixing different repositories (Fedora) to play some esoteric file formats.
rhythmbox excersizes gstreamer a fair bit, and has removed all file format related code which is why it still doesn't have things like tag editing which should be implemented in gstreamer first. I really wish KDE and GNOME could work together (maybe through f.d.o) to make gstreamer the one for *nix at least for now. One interesting player out there is muine, but you seem to mind gtk based apps though. It is relly simple and it has most of what you want from a player, but is not big on configurability.
Why is it named "amaroK"? Is there some significance there?
The app is named after the album Amarok by Mike Oldfield. It is truly great music, and as a long time Oldfield fan I felt this is a nice name for a music program.
It is also worth noting that Amarok means "Wolf" in the Inuit language. In a different context it could also be interpreted as "I am a rock" ;)
Quoting a large Mike Oldfield fan site: http://tubular.net/discography/Amarok.shtml
"There is speculation on what the word Amarok might actually mean. Mike himself has said that it doesn't really mean anything, but it could sound a bit like 'am a rock' (as in saying I am a rock, perhaps a comment on his nature). Others say that, like Ommadawn, the title is a corruption of Irish gaelic words, which mean 'morning' and maybe most interestingly, 'happy'. The word 'happy' is spoken at various times throughout the album.
Also similar is the Innuit word for wolf, amaroq, which some say Mike heard on a TV programme about wolves."
That's the full story.
- Niels
(proud owner of the Amarok Gold Edition, and original transcriber of the Amarok Fast Riff).
I for one, enjoy amaroK's UI, especially the cool album cover feature. I do have stability issues, though.
I've compiled amaroK from source, under Debian with KDE 3.2.3, and GStreamer-0.8.4. Every once in a while, playback stops, without any other observable problem (i.e., amarok doesn't hang.) Clicking the play button in these cases does not resume playback, and I have to restart the application.
Any suggestions on how to solve/debug this issue? I suspect it has something to do with the underlying engine, so I'm not sure simply running amaroK through a debugger would help.
I have a similar, but worse, problem. Since last night upgrade from Debian/Kalyxo sources.list server, amarok just cannot play with gstreamer. It justs doesn't sound, and leaves the soundard/alsa/arts ina a very bad state, no other appilcation can play...
I have to disagree with other people here, I really like the original UI of amaroK. Perhaps they should try it a bit more. The context tab is awesome, the collection tab is simple and powerful, the browser tab and the "Add media" button allows you to not mess the database when you don't want (which is a weak point of iTunes or Rhythmbox in my view), and as the website says, amaroK "doesn't get on your way"
One tiny thing though : on the sidebar, you can quickly access each browsing mode by clicking on a tab. But for some reason, the "Playlist" tab and the "Smart playlist" are in the same tab.
http://amarok.kde.org/images/zoom/XLZENU/transparent.png
This splitted window is not very usable with a small screen (like me) when you a non-trivial number of playlists. Fortunately, you can make the "Playlist" or the "Smart Playlist" take the full screen of the tab. But this means that you have now two logics and two ways to change from a tab to another.
Why not just make two separate tabs ? Simple is beautiful.
I like Amarok's UI and it's feature set is dead on for what I need.
I know the UI is not like most other programs, but I think the differentiation is for the best and it is also quite common for such an application. Now if this was a word processor or web browser I would insist on a uniform interface, but these programs are not so complex to use anyway and people do not want the screen real estate to be limited by a menu bar and like the cool and different look IMO.
Great job!
I don't understand the comments about amaroK not looking like a KDE app. This is what caught my attention the first time I got a look at it. I also think that features added like the player window follows KDE color scheme makes it look more KDE-like then ever.
I don't understand the need for a menubar, could someone answer this for me. All of the functions (very few) that are needed to actually play music are right there in the toolbar. All of the more advanced features (read stuff not often used i.e. configuration) are in a single location, the menu button. Had the devs put a menu bar and every other "KDE-like" feature, the playlist would grow bloated with no playlist to look at.
This all really bothers me, of all the time I've spent in #amarok I have yet to hear anyone say it was non KDE-like, or that amaroK was hard to use. I can however speak of the many users who have traded in XMMS for amaroK.
But everyone is entitled to there opinion, I guess this explains the all of the recent "usability experts".
:)
Cheers,
Mike
I wrote this review:
http://grebowiec.net/archives/2004/09/amarok_11_revie.html
of Amarok 1.1 just to day :) I am rather enjoying it. It is what I have been waiting for in the music/media manager area.
Best media player I have ever used. I find the ui great too, despite the many people saying the ui is bad. Then the ultrafast tagging is great, when I ran some hot mediaplayer in windows it crashed when scanning my collection. taglib sweeped it very fast!
The hardest part with amaroK is remebering the name ;=)
Awesome guys!
P.
... is that it's not packaged for Debian so I can't try it. Currently I can't play my music at all under KDE.
I just ripped a new CD with the audio-CD ioslave, and it only gave me the options to rip as WAV or OGG, so naturally I picked OGG (KAudioCreator just sat and spun the CD, had to be killed [this is no copy protected CD, cdparanoia could rip it just fine at home]). Ripping went fine, but Juk can't seem to play OGG. It loads the files, starts playing, knows the file length and everything seems ok, but there is just no audio output! Playing a few old MP3:s I happen here at work works just fine.
So as Juk can't handle OGG I'd like to try Amarok, but I don't want to destroy my machine with randomly installed software, I prefer it packaged as deb:s (yes, call me lazy, but compiling and installing KDE apps with a different --prefix never seems to work properly).
Most of my music is in OGG, and it plays just fine in Juk. Something must be wrong with your setup.
Amarok-1.1 is packaged in Debs by Kalyxo.org. Follow the Debian link on the amarok homepage. There are some problems with gstreamer playbackin this build, so I use the xine playback. I detest and hate artsd.
JuK can certainly play MP3 and OGG files here (Debian unstable). Do you use the gstreamer or the artsd backend?
Debian packages are available on kalyxo.org. Just click the "Debian" link on our site.
> My only problem with Amarok is that it's not packaged for Debian so I can't try it.
You can find packages for Debian here:
http://www.kalyxo.org/twiki/bin/view/Main/KalyxoPackages
The KAudioCreator thing is a bug, and it should be fixed in KDE 3.3.1 and 3.4
http://bugs.kde.org/show_bug.cgi?id=87267
Hi,
I was beginning to think I was the only one to have such a problem with kaudiocreator. I can tell you why you can't hear a thing :
kaudiocreator just didn't succeed in ripping the cd tracks. I have the same problem here : it happens from times to times (espacially when I try to rip a cd all in 1 go) that kaudiocreator freezes. I then have to open a console an kill the kaudio_cd process related (you can also kill the kaudiocreator process). Then it _looks_ like everything is back to normal : you try re-ripping the cd and, let's say, this time everything goes ok. You open your , load the files : everything looks fine but you can't hear a thing. WTF ? I made some searches and I found that the wav file extracted by kaudiocreator is also "speechless". The only solution I got to be able to rip cds again is to reboot the entire system !!!
I think there are 2 problems :
1) The first one is how kaudiocreator deals with the CDrom drive (see the bug reported earlier http://bugs.kde.org/show_bug.cgi?id=87267 (which I just found out)
2) I think that this kaudiocreator behavior pushes the CDROM drive driver to its limits and that the kaudiocreator freeze is due to the CDROM driver getting "mad". When you kill the application, the driver is left in a "weird" state and cannot rip cds anymore...
My CDrom drive driver is built-in my kernel so I cannot test if unloading/reloading the kernel would solve the problem (and validate my theory). Also it could be that, with solved, won't appear anymore.
As I found nobody else that had the same pb, I gave up and was waiting for the new 2.6.9 kernel to test my theory. But I'm happy (sorry for you) that someone encounters the same problem : could you please tell me your distribution / kernel version and cdrom drive model ? That would be very helpful !
Thanks for having the same problem as me :)
thibs
For those who don't follow the bug link I have reworked KAudioCreator to not rely on the cdrom drive anymore and should solve the problem that a number of people's drives were having (too bad mine didn't or I could have caught it for3.)). This fix is in 3.3.1 which will be out very soon.
I've tried Amarok, just as I've tried Juk and Noatun, and in the end, I always
have to go back to either xmms or ogg123. I simply cannot figure out how to play music with Amarok. I fumble around as if it's my first day with a computer. Which is rather annoying, since I've been messing around with all kinds of computers for more than twenty years.
Maybe I should make a nice mpeg video of what I'm trying to do. I found Bart's video of him using Krita very useful in assessing Krita's UI. Maybe showing in what way I am simply incapable of getting Amarok to function would help the developers.
(The reason both Juk and Noatun fail to make the grade is that they skip when I'm compiling code, which is pretty much permanent with me).
that is just what I felt when I started amarok: damn, how does this work??? I hate that feeling, and I dont have it very often... please, can you guys try to make the interface a bit more like itunes or juk? its much easier to have play/pause/next on top of the interface.
hmmm, now I try it again - I think that's my mayor annoyance, altough the menu key is quite stupid, there - imho. I'd say make a normal menubar, put the tools now on bottom on top, and you'r interface is more KDE-like and more logical. or at least make it configurable (and use the KDE-like interface as standaard).
>please, can you guys try to make the interface a bit more like itunes or juk?
Why not using juk instead? Why do you want amaroK to look like juK? I never use Juk, i hate Juk GUI but i'm not mailing juK devel to make his soft looking like window media player...
>its much easier to have play/pause/next on top of the interface.
ok, good argument, so
its much easier to have play/pause/next at bottom of the interface.
check other interfaces. where are the buttons in kmail? kopete? konqueror? need I say more?
and juk has a clean interface, its a good starting point. I like amarok, I use it, but I really dont like the way it handles playlists. I still have trouble figuring out how to do them in an easy way... in juk this was easy.
"(The reason both Juk and Noatun fail to make the grade is that they skip when I'm compiling code, which is pretty much permanent with me)."
Do you have dma on? (use 'hdparm /dev/hd?' )
Yes... I must admit that I goofed when I specified my laptop. I should have gone for the bigger & faster hard disk, but on the other hand, xmms never skips.
with realtime-priority turned on and akode from kde 3.3 (instead of mpeglib) artsd can play mp3 and ogg pretty reliable. I always had dropouts on cvs up, even with xmms. akode finally has cured this here.
Xmms/winamp must be the worst interface there is for a music collection.
Using only 5% of your screen-space when you have a collection of maybe over 1000 songs just does not make sense.
Well just resize the playlist window?
...and resize the file dialog open window. That's what I remember about playing MP3s back in the bad old days of XMMS, having to resize the open file or directory window all the time. And well, 'of course' you have to open a seperate window to select a directory in XMMS. And then the Open Directory window would take like 5 seconds to open (but I'm sure that was just a GTK1 thing).
For some folks I'm sure the XMMS UI does work for them. And amaroK can be setup to be pretty XMMS-like for those folks.
Hi Boudewijn,
it distresses me to hear you find our player confusing. I'd like to address this. If you could take the time to describe what was confusing for you I'll take the time to fix it up and make amaroK perfect for you too! If you want to either reply here or write to our mailing-list, or visit us in #amarok.
Thanks!
Max
I spend some time yesterday to mail Max a description of what I was doing, and true to the tradition of debugging-by-confessional discovered that I was using a backend that couldn't play oggs. Without attempting to get that backend to play oggs, I switched to another, and lo! and behold, I could play my music files.
I'm still not sure that I'm among the intended audience of Amarok, because what I mostly do is drag a bunch of oggs from konqueror onto the systray icon, and and let them play, which hardly makes use of all that work on making playlists powerful
Yes, I have _exactly_ the same experience. I tried a lot of those music managers, but at the end, my vast collection breaks them all.
eg amarok would scan on each change of a tag, and makes it use 100% then for very logn time. You can't sort after path+filename, and it rescans the tags everytime you drop them into the playlist (why then use sqllib inside?).
At the end for just playing music, I use xmms (either with arts or direct alsa) and for tagging easytag (old but works very good). The rest I do in the shell, like ripping with abcde (works just flawless) and moving around file.
amaroK used to be really annoying about scanning files. I think its improved a lot in 1.1.
I doubt, I used 1.1 in debian unstable and it was still unbearable :(
Juk appears with cleaner interface & is such a pleasure to use. my 2 cents.
Thanks for sharing this very interesting and helpful information.
All this comments are just reaction of Juk fans thinking that amarok is going to replace it ...
So stupid, all I wan't to say is : "JUK SUX, STUPID GNOME LIKE APPS WITH NO OPTION/FEATURE"
Really intelligent, no?
But i don't think this, i don't think amaroK should be like juK and vice versa. I don't like juk gui, i prefer amaroK ... Don't troll in this news, i you like juK use it, please...
Don't listen to all the ppl here that says they prefer JuK, noatun, xmms or whatever. Let them use the things they prefer and keep amaroK the way it is for those of us that like it!
I just installed this new version but I just can't get it to work. When I start it it says that I need to select output plugin gstreamer. And when I select it later and click Apply amarok just closes (no crash or something like that). I also tried to select arts and it also just silently closes. I'm runing this on AMD Athlon 64 in 64-bits if it has anything to do with this.
Yep, I would say I have the same problem here (and I use also amd64 :-) gentoo? )
It's a problem with the gstreamer method (gst_emelent_link many) as far as I can tell you (placing kdDebug code before and after that method in createPipeline()).
The funny thing is, if you start amarok for the first time, it wants you to select a gstreamer output plugin. So if one chooses for example arts or xine or whatever instead (we don't want to use gstreamer because it crashes/exits), it will call after applying the changes also the gst_element_link_many method and exits:) Although I exepcted it to switch the engine without calling gst_element_link_many again.
One possible solution:
If you disable gstreamer for amarok (-gstreamer) during compilation, it works here with arts...
Actually, I pulled this off with switching to Xine, then switching back to GStreamer, then selecting the alsasink output plugin. Didn't close. I'm on an AMD TBird, so obviously that ain't it, but I am running gentoo.
I tried to compile without gstreamer but now I get this error:
g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../amarok/src/amarokcore -I../../amarok/src/amarokcore -I../../amarok/src/analyzers -I../../amarok/src/engine -I../../amarok/src/plugin -I/usr/kde/3.3/include/arts -I/usr/include/taglib -I../../amarok/src/sqlite -I/usr/kde/3.3/include -I/usr/qt/3/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -march=athlon64 -pipe -O2 -fomit-frame-pointer -frename-registers -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o collectionbrowser.o `test -f 'collectionbrowser.cpp' || echo './'`collectionbrowser.cpp
g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../amarok/src/amarokcore -I../../amarok/src/amarokcore -I../../amarok/src/analyzers -I../../amarok/src/engine -I../../amarok/src/plugin -I/usr/kde/3.3/include/arts -I/usr/include/taglib -I../../amarok/src/sqlite -I/usr/kde/3.3/include -I/usr/qt/3/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -march=athlon64 -pipe -O2 -fomit-frame-pointer -frename-registers -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o collectiondb.o `test -f 'collectiondb.cpp' || echo './'`collectiondb.cpp
g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../amarok/src/amarokcore -I../../amarok/src/amarokcore -I../../amarok/src/analyzers -I../../amarok/src/engine -I../../amarok/src/plugin -I/usr/kde/3.3/include/arts -I/usr/include/taglib -I../../amarok/src/sqlite -I/usr/kde/3.3/include -I/usr/qt/3/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -march=athlon64 -pipe -O2 -fomit-frame-pointer -frename-registers -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o configdialog.o `test -f 'configdialog.cpp' || echo './'`configdialog.cpp
g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../amarok/src/amarokcore -I../../amarok/src/amarokcore -I../../amarok/src/analyzers -I../../amarok/src/engine -I../../amarok/src/plugin -I/usr/kde/3.3/include/arts -I/usr/include/taglib -I../../amarok/src/sqlite -I/usr/kde/3.3/include -I/usr/qt/3/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -march=athlon64 -pipe -O2 -fomit-frame-pointer -frename-registers -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o contextbrowser.o `test -f 'contextbrowser.cpp' || echo './'`contextbrowser.cpp
collectiondb.cpp:1342: warning: unused parameter 'parent'
collectiondb.cpp:1342: warning: unused parameter 'artist'
collectiondb.cpp:1342: warning: unused parameter 'album'
collectiondb.cpp:1342: warning: unused parameter 'noedit'
g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../amarok/src/amarokcore -I../../amarok/src/amarokcore -I../../amarok/src/analyzers -I../../amarok/src/engine -I../../amarok/src/plugin -I/usr/kde/3.3/include/arts -I/usr/include/taglib -I../../amarok/src/sqlite -I/usr/kde/3.3/include -I/usr/qt/3/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -march=athlon64 -pipe -O2 -fomit-frame-pointer -frename-registers -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o coverfetcher.o `test -f 'coverfetcher.cpp' || echo './'`coverfetcher.cpp
g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../amarok/src/amarokcore -I../../amarok/src/amarokcore -I../../amarok/src/analyzers -I../../amarok/src/engine -I../../amarok/src/plugin -I/usr/kde/3.3/include/arts -I/usr/include/taglib -I../../amarok/src/sqlite -I/usr/kde/3.3/include -I/usr/qt/3/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -march=athlon64 -pipe -O2 -fomit-frame-pointer -frename-registers -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o covermanager.o `test -f 'covermanager.cpp' || echo './'`covermanager.cpp
covermanager.cpp: In member function `void CoverManager::showCoverMenu(QIconViewItem*, const QPoint&)':
covermanager.cpp:379: error: `FETCH' undeclared (first use this function)
covermanager.cpp:379: error: (Each undeclared identifier is reported only once for each function it appears in.)
make[4]: *** [covermanager.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[4]: Leaving directory `/var/tmp/portage/amarok-1.1/work/amarok-1.1/amarok/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/amarok-1.1/work/amarok-1.1/amarok/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/amarok-1.1/work/amarok-1.1/amarok'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/amarok-1.1/work/amarok-1.1'
make: *** [all] Error 2
That's a bug that is fixed in amarok cvs.
But it comes from not using "amazon" with amarok,
but the amarok ebuild is(was!?) broken anyway
when it comes to the "amazon" use.