Overdrive...

Hi,

First off, I don't have more answers about this topic, sorry; I just wanted
to add some more questions :).

I also read the article some time ago and it surely helped me understanding
what overdrive is and how to use it, but still it also leaves me a bit hazy
on the topic.
What still can't completely grasp is the multithreading issue. The article
gave me the idea that whithout overdrive, Max is running 1 thread and with
overdrive enabled 2 threads being the queue and scheduler. But then, when
i'm using multiple metro/qmetro objects to bang scheduler priority
processing paths, are these both in the same thread (=scheduler thread)? or
are they able to run in parallel?... like this i could go on for 10 pages
enumerating all the cases i came across where i questioned myself about this
threading/priority issue, so i'll try to summarize my 'haze' in some 'to the
point' questions:

- how do i identify a single processing thread?
- what is the general practice when u come across a bottleneck like frame
dropping or too low frame rate?
- Is it possible that 1 issue that takes too much processing time slows down
the entire patch?
- what about the combination of GPU and CPU processing? can the performance
of one influence the other negatively?
- ...

I hope it is clear to someone where my understanding problem lies, so that
Rick and I and probably a whole lot more Maxers can be helped.

thanks for your time!

d

On 8/2/07, Rick Burnett wrote:
>
>
> Thank you, this information was very useful. Yes, it left me with a
> little bit more haze in my brain about the topic, but at the same time, now
> I understand about the priority levels.
>
> I wonder, is it possible to get the video stuff into a higher priority to
> keep it from dropping out at times? (like when changing the rate of a
> different movie, all of them seem to glitch).
>