Bug 118967

Summary:	Xine engine does not work in Amarok
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Daniel Wolstenholme <daniel>
Component:	KDE	Assignee:	E-mail List <kde-maintainers>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	gz058
Version:	RC 1
Target Milestone:	---
Hardware:	i686
OS:	All
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Daniel Wolstenholme 2005-09-27 04:00:22 UTC

With Amarok installed, I have two choices for audio engines: xine and arts.  
Arts hogs 20% of my CPU time (this is a 3.6GHz P4, not slow), so I filed a bug 
against that and it was rejected because arts seems to have fallen out of 
favor.  But the only reason I used arts was because xine doesn't work. 
 
So I select xine, and then have to choose an output plugin. 
 
If I choose "oss" and click "apply", Amarok immediate crashes.  I've sent the 
backtrace to the default email address. 
 
If I choose "AutoDetect" and click "ok", and then double-click on a song to 
play it, Amarok crashes.  I've sent the backtrace as with the previous one. 
 
If I choose "ALSA" (which is really what I have: NVIDIA MCP-04 using AC-97 
driver) and "ok", then select a song, it "plays" it for about a half-second, 
then goes on to the next song for about a half-second, etc.  No actual sound 
is produced.  The songs are all MP3s (I've installed the MP3 packages from the 
Packman repository through Yast). 
 
JuK, on the other hand, works just fine, aside from the fact that it's nowhere 
near as easy to use as Amarok's UI.  I can't seem to find any engine selection 
in JuK's setup, so I'm not really sure what it's doing underneath.  Why can't 
Amarok use the same engine JuK is using?

Comment 1 Daniel Wolstenholme 2005-09-29 04:59:38 UTC

Well I figured out why arts was hogging CPU time: my 3.6GHz P4 was being 
throttled to 450 MHz by the powersave daemon in "dynamic" mode.  I'll file a 
bug against that separately, but the rest of this bug about the Xine engine is 
valid still.

Comment 2 Stephan Kulow 2005-10-06 13:57:13 UTC

see if this works better in the final. You're so far the only one to report it

Comment 3 Oliver Wilson 2005-10-07 13:24:30 UTC

This seems the same as 116294.

I have the same thing - no engine will load.

Fresh install of rc1 followed by YOU.  Correct modules installed / loaded
(snd-emu10k1, SB Audigy for the record).  Command line utils work fine, perfect
sound output. BUT I cannot get xine to load for amarok, or indeed arts (no great
loss there!).

Off topic, why is xine the only bundled engine?  Every other distro seems to
default to gstreamer yet I can't even find a package for that in SuSE - am I
right?  An alternative engine would at least be useful in finding the cause of
this problem.  Stephan mentions upgrading to Final - how is this accomplished? 
YOU only upgraded a couple of packages, I must still be on rc1?

Comment 4 Stephan Kulow 2006-05-07 11:34:03 UTC

we fixed a bunch of problems in the xine engine and even made it online update for it. Xine is not the only engine, we have a gstream engine, a helix engine and even an arts engine package.