[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-multimedia
Subject:    Re: JEL - a job execution layer for aRts
From:       Martin Vogt <mvogt () rhrk ! uni-kl ! de>
Date:       2000-07-19 16:43:07
[Download RAW message or body]

On Wed, Jul 19, 2000 at 12:48:49AM +0200, Stefan Westerfeld wrote:
>    Hi!
>

> We can't do ... because it takes more than ... ms. Specially in the
> PlayObject discussion: we can't create a new PlayObject each time, because
> it takes to long to initialize and thus causes dropouts.

I have looked at it, but currently does not see
how it solves the problem.

The point is, that artsd is not threaded. 
The creation of the playobject should have nothing
to do with the already _running_ playobjects.

Droppouts only happen if the delivery thread is stopped.

(Or your system is too slow, but you cannot do anything against this)

All PlayObjects which are running (Gui sents play())
can be passed to the delivery thread.

All Playobjects which are _not_ running are removed from the
delivery thread and are passed to the "waiting" queue.
(gui sends anything != play())

Its ok if the GUI blocks during a call, but artsd should not block.

I know nothing about the internals of arts, these are only
some ideas.



regards,

Martin



_______________________________________________
Kde-multimedia mailing list
Kde-multimedia@master.kde.org
http://master.kde.org/mailman/listinfo/kde-multimedia

[prev in list] [next in list] [prev in thread] [next in thread]