I would just like to report, that Amarok 2.0, running KDE4 technology is successfully able to play music with Phonon and the Phonon-xine backend. The rest still works/looks as if it was hit by a bus.
Pages
Tags
akademy akademy2008 amarok asia audio belgium cairo concert debugging egypt europe felluca game gcds giza gnome google gran canaria hacking holiday howto humour ifp israel jordan kde mda middle east music nvidia open tech summit otst2008 petra puzzle pyramids qt quiz riddle sinai snow software spain taipei taiwan travel
7 Comments
Even if it’s a trainwreck it’d be great to see a screeny.
will Crossfading work with Phonon?
And what do you think about Phonon?will you keep your own Engines and will you maintain them?or you will only on Phonon?
I think being on Phonon, and adding more features/Options to Phonon backends is the best solution.Maintaining those backends takes a lot of time from AmaroK developers, if they drop their own backends, and only support Phonon, they will have time to implement other Cool things.
Thanks
(Sorry for Bad English)
P.S: Only works with Phonon-Xine???Phonon is there because i dont want to care about xine/gstreamer/… anymore!
Naturally, Phonon is easy to work with, since the API is modelled after Qt/KDE. As for the other engines, we have not decided about the future of the backends, we’ll be sure to notify you all when we do!
Crossfading will work with phonon. And the reason why it currently only works with phonon-xine is that at the moment, the phonon-xine backend is the one with the most progress. GStreamer and others like NMM will follow soon, don’t worry, until Amarok 2.0 comes out, they will all be finished.
Nice.Im sure AmaroK guys can help phonon.i love you amarok…
Quoting Seb:
“As for the other engines, we have not decided about the future of the backends, we’ll be sure to notify you all when we do!”
What do you mean with that? You only support the xine phonon backend? If so, why?
You use Phonon, not it’s backends, so it should make no difference which backend is installed or choosen by the user.
I edited the amarok development wiki page to also use the other backends, but it was reverter very fast. Which is not very motivating in my opinion.
Tim…
About the engines. We will support phonon. whatever phonon backend you choose is irrelevant, it will also be supported. I was talking about our own engine implementations which interface with xine/gst/nmm etc. We don’t know if we’ll keep them or simply let phonon do the talking.
And the wiki page? You have to realise that xine is the most complete backend. Make a note of the others, but don’t force the user to get all the backends if they aren’t needed. The page is a development howto.