INTERACT FORUM
Windows => Plug-in Development => Topic started by: PaulSinnema on May 01, 2007, 02:52:47 am
-
Hi,
Theatre View looks very nice but on my 4 year old MM PC (Pentium 4 2GHz 512Mb) which at the time I bought it was top of the bill has become too slow for the processpower needed for Theatre View. When I start it it just sucks up all of the processor and still wants more.
Is there a way to brake the Theatre View a bit so my PC can cope or do I need a new PC :D
Paul.
-
You could try dropping the frame rate. It's a setting in only very recent builds.
-
You could try dropping the frame rate. It's a setting in only very recent builds.
Hi Jim,
Already did that, set it 20 but it still consumes up all the juice of my processor. I'll try setting it to 10. Will let you know!
Paul.
-
Jim,
I've set the framerate to 10 and now the responsetime in the Theatre View is acceptable. My processor is still fully occupied by MC, but that doesn't bother me too much.
Paul.
-
For Theater View it may be worth just trying a better Graphics Card.
Theater view uses DirectX graphics, and as such the better the graphics card,
the less get's loaded on to the main processor.
-
Chriz is right. Any modern graphics card should work.
-
Jim, ChriZ,
Replacing the graphiccard is no option for this PC. It's a Compaq D510 with graphics on the motherboard and no place left to put any extra cards in. So my only option for this one is, replace it. For the moment I'll settle with the Normal View of MC to which I used anyway. And... in Theatre View I can't see my own beautiful plugins ;D (cough).
Paul.
-
I can run MJ8 full screen happily on far lower spec, so I'm doubtful the hardware is the problem. 2 things you can do that will much reduce cpu load:
Reduce visi resolution. Right click the visi screen, display quality...
Reduce screen resolution that this view uses. Right click the visi screen, display mode, full screen....
And of course there are the simple things like dropping unused windows modules (using autoruns) and closing background processes that tend to accumulate on so many PCs.
Tab
-
I can run MJ8 full screen happily on far lower spec, so I'm doubtful the hardware is the problem. 2 things you can do that will much reduce cpu load:
Reduce visi resolution. Right click the visi screen, display quality...
Reduce screen resolution that this view uses. Right click the visi screen, display mode, full screen....
And of course there are the simple things like dropping unused windows modules (using autoruns) and closing background processes that tend to accumulate on so many PCs.
Tab
I think Pauls running MC12, which is a tad more resource hungry to match
users modern requirements than MJ8. MC12 uses a much more graphics
intensive Theater View.
-
I agree MC eats more in some areas, but the visi engine is the same one used in MJ8, and when running full screen this uses way more resources than audio & gui etc. So I still think the problem lies elsewhere.
Tab
-
I agree MC eats more in some areas, but the visi engine is the same one used in MJ8, and when running full screen this uses way more resources than audio & gui etc. So I still think the problem lies elsewhere.
Tab
but... Paul was talking about Theater View which is uses a new 3D engine now, not the visuals.
-
ChriZ is right. I am running MC12 and using it often (not always) in Theatre View. The framerate suggestion did help a lot. The display is less fluent but my PC keeps up pretty good now. When I have a bigger budget I'm defenitly going to buy a faster PC. Thanks for the replies guys!
-
Try build 254 or later once it's available. We changed how we handled vertical syncs, which might help a bit in your case.
-
Replacing the graphiccard is no option for this PC. It's a Compaq D510 with graphics on the motherboard and no place left to put any extra cards in.
The d510 came with an AGP slot... are you using it for something else?
AGP cards can be picked up pretty cheap nowdays, although they are getting harder to find...
C.
-
Well the slot was filled with a graphic card with some more juice but it broke down a couple of years ago. Now I'm running on the buildin graphics, which is not too powerfull but it'll do for the moment.