[openbeos] Re: mov reader
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Thu, 16 Jun 2005 02:05:13 +0200 CEST
"David McPaul" <dmcpaul@xxxxxxxxxxxxxx> wrote:
> > That doesn't sound too well, and could also point to problems in
> > the
> > Media Kit iself, not only in your code. Marcus?
> A further look I found that a thread called "<MovieName> control"
> gets
> given priority 110 and this thread is taking the CPU time, the mouse
> thread is only priority 104.
>
> I will look for where this thread is started from.
>
> Ultimately, the cpu issue is my code or something my code is doing to
> confuse the audio output. But I am not sure a media control should
> have such a high priority.
Only low computing tasks should get a high priority. If this thread
"owns" the CPU, there is something wrong with it.
Audio tasks are usually very time critical, so a high priority doesn't
sound wrong per se.
Bye,
Axel.
- References:
- [openbeos] Re: mov reader
- From: David McPaul
Other related posts:
- » [openbeos] mov reader
- » [openbeos] mov reader
- » [openbeos] Re: mov reader
- » [openbeos] Re: mov reader
- » [openbeos] Re: mov reader
- » [openbeos] Re: mov reader
- » [openbeos] Re: mov reader
- » [openbeos] Re: mov reader
- [openbeos] Re: mov reader
- From: David McPaul