Re: [Protux-devel] RTS problems

[rsff]

Guys,

>From what I understood, Protux needs low-latencies in order to get good
recording performance. But it is forced by the kernel to share resources
with other running programs, and some of the operations it handles are
also resource hungry, which means, using a lot of resource for some
tasks plus having to share the leftover resources for recording.

I understand absolutely nothing about priorities, real times scheduling,
or threads and how this should be implemented. But it occurred to me
that one of the advantages of GNU/Linux (and future hurd as well) is the
possibility of using other dumb-workstations do devides intensive tasks
(Rendering Farms, so to speak). Shouldn't this be taken into account
when designing things related to how Protux relates to the kernel, and
how it handles resources in general?

Am I on an trip? Did anyone follow me? RFC... 
Fabio.

On Wed, 2003-09-10 at 21:01, Luciano Giordana wrote:
> > Using pthreads is IMO better as we have more control options compared to
> > QThread.
> good point. We moved from pthread to qthread cause a super-bug, which was
> solved a long time ago. We could get back to pthread now.
> 
> also, the best thread to put in RTC is Mixer->going. It is focused on 
> mixing/reading
> audio during go operatoin, and it is the only thing that needs the low 
> latency (wich require 
> rtc)
> 
> 
> 
> 
> _______________________________________________
> Protux-devel mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/protux-devel
-- 
rsff <address@hidden>