Log in

View Full Version : Dual DVDRB


Penecho
18th February 2006, 17:53
I've read, that in Version 1.07 there is code implemented for Dual Core CPU's :) but CCE was not mentioned. Does it also work with CCE ???



Cu

Rumbah
18th February 2006, 17:58
No, it does not work with CCE.

Rockas
18th February 2006, 19:53
CCE doesn't need it... it will use the full horse power of you processor as default :)

l8nights
18th February 2006, 20:30
was actually interested in seeing if there was any plan's on implementing this as cce sp only registers ~72-80% on my p43.0 W/ht enabled and not much but a little less (60-75%)on the new pd 920@3.4

also memory was reading about 700mb's and not utilizing my 1024 but I will heed the wisdom of the elders if this is not a plausible addition!

seems procoder2 does better using 100% than cce in my particular "case"!

jdobbs
18th February 2006, 20:35
Unfortunately CCE will not allow a second instance to load. That's why it is not implemented.

betard
18th February 2006, 23:50
and although it would make the encoding faster, I am kind of glad it doesnt use 100% of my cpu/memory... only for the sake of not preventing me from doing other non intensive things on the computer still.

Penecho
19th February 2006, 00:12
CCE uses only 80% of one Core!! my other Core is always idle :(

My 2 GB Memory are also not fully loaded!!



Cu

jptheripper
19th February 2006, 00:19
its a cce issue, they block dual instances.

l8nights
19th February 2006, 00:28
No, it does not work with CCE.

I'm guessing that it will block a second version of cce in a second seperate file from being called upon then?!?!

wonder why those smart people @ cinema craft wouldn't want that?

jdobbs
19th February 2006, 01:55
Yep. I've tried it. It won't block two different versions, though.. I can run CCE SP and CCE Basic at the same time.

Boulder
19th February 2006, 08:59
My 2 GB Memory are also not fully loaded!!

If you really want to use more memory for the encoding process, you could create a file called setmemorymax.avsi in the Avisynth plugins folder (by default c:\program files\avisynth 2.5\plugins). The file contains only the line SetMemoryMax(1024) in it. That way Avisynth will always allocate a maximum of 1024 megabytes.

However, I'm quite sure you'll see zero difference in performance. Allocating more memory is useful only with rather complex scripts.