Hi ppl,

After an "incident" I had to reinstall my Distri (ArchLinux with KDE4.3) and with my Distri I had to reinstall Amarok. Unfourtanetly I don't remember how I got Amarok to work last time but I'm having problems.
After I add some Tracks to the playlist and press the play button, Amarok just skips every track and stops after a while saying the playlist contains too many errors.
I am using Amarok 2.2-GIT. Can anyone help please?

--blackdeagle

Using 2.2-git on Arch here as well. The only time I had the problem you mention was when I had gstreamer set as my phonon backend. If that's your problem as well running:

Code: Select all

pacman -S phonon-xine

And setting xine as your phonon backend via systemsettings should clear it up.

And make sure you have the codecs installed, too.

...that might be hardware dependent. Here the xine backend didn't work, but gstreamer did, so I guess you just have to experiment.

Thanks for the responses.

I just started Amarok and wanted to change the Sound configuration but before that I wanted to test if Amarok works. I doubleclicked a Track in the Playlist and I was surprised: It worked! I didn't do anything, just double click on a Track. It didn't work for a week but now it works!
I don't understand the world anymore Can anyone explain this miracle??

It was likely that the KSycoca contained out of date entries ( possible, especially if you've just installed something ) or a library still had older versions loaded.

annew wrote:...that might be hardware dependent. Here the xine backend didn't work, but gstreamer did, so I guess you just have to experiment.

This is due to the fact that you are using pulseaudio. It doesn't work well with Phonon and the Xine backend, and there is no reason to use Pulseaudio in KDE in the first place, As KDE doesn't need it, the best would be to remove that and rely on Alsa and Phonon to handle sound, that's how it is intended in KDE anyway, and it works perfectly well.

Of course, if you actually want to use Pulseaudio, then you will need the Gstreamer backend, but from the Amarok and KDE POV gstreamer is very buggy and is not exactly something we recommend. Why using GTK when you can have Qt in all its glory

Mamarok wrote:

annew wrote:...that might be hardware dependent. Here the xine backend didn't work, but gstreamer did, so I guess you just have to experiment.

This is due to the fact that you are using pulseaudio. It doesn't work well with Phonon and the Xine backend, and there is no reason to use Pulseaudio in KDE in the first place, As KDE doesn't need it, the best would be to remove that and rely on Alsa and Phonon to handle sound, that's how it is intended in KDE anyway, and it works perfectly well.

Of course, if you actually want to use Pulseaudio, then you will need the Gstreamer backend, but from the Amarok and KDE POV gstreamer is very buggy and is not exactly something we recommend. Why using GTK when you can have Qt in all its glory

I was not sure if I used pulseaudio or not so I looked up: The package "pulseaudio" is not installed on my system.
To be honest I don't care why it works now. Only thing is it works

Here's one more mystery to solve:

If I start amarok using sudo it works! I can hear the songs. But if I start amarok with my username it won't!!

This explains also why it worked today in the morning (TimeZone is MiddleEurope). I'm currently experimenting on a simple script which starts kde via the console for me. I edited the script today in the afternoon removing "sudo" before the kde-start-command.
I was logged in with su rights! Oh my God haha!
And thats why it worked today and still works if I start amarok with sudo.

I hope this isn't written too complicated.. (You actually don't need to understand that )

blackdeagle wrote:Here's one more mystery to solve:

If I start amarok using sudo it works! I can hear the songs. But if I start amarok with my username it won't!!

This explains also why it worked today in the morning (TimeZone is MiddleEurope). I'm currently experimenting on a simple script which starts kde via the console for me. I edited the script today in the afternoon removing "sudo" before the kde-start-command.
I was logged in with su rights! Oh my God haha!
And thats why it worked today and still works if I start amarok with sudo.

I hope this isn't written too complicated.. (You actually don't need to understand that )

Can you play sound in anything other than Amarok when you're just logged in normally? If not you might just need to do:

Code: Select all

gpasswd -a YOURUSERNAME audio

To add yourself to the audio group.

Note that running KDE as root is very dangerous, and is definitely not recommended. As written by Jarsto above you likely need to add yourself into the appropriate group.

"ls -la /dev/ | grep dsp" will tell you which user and group own the audio devices.

whoa, didn't get a notification about the responses.
I am in the audio group and I solved the problem with the help of a friend He suggested installing another backend (Xine didn't work at all and amarok couldn't handle gstreamer). After installing the vlc-backend everything worked out fine!

Thank you all for taking your time helping me
Thread can be closed!