JACK support for amarok

[Andrew Turner]

Amarok's aRts support was quite buggy, with many users reporting
problems. Added to that, other engines such as xine are far more
capable, and aRts itself will be scrapped for KDE4. Therefore keeping
it around seemed to be doing more harm than good.

The rôle of engines in Amarok requires them to decode the streams or
files, and then output the result to the selected audio sink (eg ALSA,
OSS, JACK, ESD).

The two recommended engines in Amarok are xine and Helix/Realplayer.
Both of these will not output directly to JACK as far as I can tell.
However, It is possible to get xine to output the decoded stream to
aRts, which you may find convenient, and has none of the downsides of
getting aRts to decode the stream itself.

There is a gstreamer output plugin for JACK, however Amarok does not
yet support gstreamer 0.10 well enough to recommend its use, although
it is being worked on. In the meantime, gstreamer 0.8 support has been
removed, as it is considered deprecated.

Andrew

On 04/07/06, Slavko Glamocanin <slavko.glamocanin at gmail.com> wrote:
> Hello,
>
> while wondering why ARTS support got dumped in the new version, i started
> thinking that this was the perfect time to ask about Jack Audio Connection
> Kit support in amarok. As i personally dont use any of your other supported
> "engines" my question is:
>
> how hard would it be to implement JACK audio out?
>
> I've used it quite a bit and can surely code an audio out wrapper for
> amarok, but i dont know how your system is designed and why do you call your
> audio outs "engines". do they do more than just audio out? (i know gstreamer
> can do a LOT more)
>
> Thank you for your answers.
>
>
> Slavko
>
> _______________________________________________
> Amarok mailing list
> Amarok at kde.org
> https://mail.kde.org/mailman/listinfo/amarok
>
>
>