Resolume Forum

hi,

first off, hello everyone! i am new here.

most people nowadays have dualproc/core-computers, they come really affordable these days. and are so handy. but obviously resolumes code seems to be single threaded yet not using both procs. meaning ~40% or whatever of your computers power is idle while its doing heavy stuff like real time compositing. which is a waste, meaning i could use higher resolutions with smoother results without having to invest a single cent in hardware. is there any estimation in which version resolume will come multithreaded?

btw, another odd thing: it is hard to tell and monitor what effects and comp-modes are hard for the processor and which are not - resolume seems to be running on a very steady 50% of my dualcore (=1proc), no matter if its doing heavy stuff or if its just all layers empty doing nothing. seems like a blackbox looking at it in taskmanager - why is that?

cheers, a.

[Edited on 12-12-2006 by electricgobo]

it is true that resolume only uses 1 of the 2 cores in dualcore comps. However, that other core is great to have if using any usb or firewire devices... it reduces the load on resolume, and can use a dedicated processor for these usb/firewire translations.

As far as which videos are using more load... 2 part answer. First off, resolume will always show %100 on one of the processors - that's just the nature of it's programming - it "reserves" the full processor for itself, even if it's not using it all. The best way to see what the loads are is by pressing "ctrl+alt+i" ... this will give you a frame rate. The lower the frame rate, the harder your comp is working. For a comparison, running a single indeo 5.1 640x480 @ 95% quality runs about 60-70 fps for me.

Hi,
we will are looking into multithreading because it will definately improve performance without having to make an hardware upgrade.

Resolume allways takes almost 100% cpu power because it runs like a game and therefore will be able to react faster on user input.

edwin

that's great - thanks a lot for the info! especially the framerate-hint is appreciated, i must have missed it reading the manual.

cheers, aksel.