johnr

i have an apple NVIDIA GeForce 9400m internal graphics card... it came with my macbook pro. it has 256 mb of vram (i can provide further info as required).

i find that when simply editing an image in realtime, the cpu processing power goes beyond 100%.... is it my graphics card? i thought my card would be good enough for jitter, to run HD video, but i can hardly edit images in real time.

my goal is to be able to play HD video (1080p) and edit it in realtime on a projector, while keeping processing power below 30ish percent; so i can reserve it for music applications as well.

-is my video card not good enough for running and editing in realtime, HD video in jitter? and therefore should i be going with an external video card?

-could it be a setting i have turned on in jitter?

i find that when simply editing an image in realtime, the cpu processing power goes beyond 100%.... is it my graphics card? i thought my card would be good enough for jitter, to run HD video, but i can hardly edit images in real time. 

-could it be a setting i have turned on in jitter?


hardware-support-for-jitter

Some processes are done on the CPU others (like open GL stuff) are done on the GPU. It is in general good to try to do things GPU accelerated.

Have a look at the whole jitter/gen family also.

I would guess what ever you are trying to do could more or less be done, the question often is one about optimisation.

What do you mean by "editing"?
Some processes are done on the CPU others (like open GL stuff) are done on the GPU. It is in general good to try to do things GPU accelerated.
Have a look at the whole jitter/gen family also.
I would guess what ever you are trying to do could more or less be done, the question often is one about optimisation.
cheers,
not-a-jitter-pro


oh forgot.. specially when it comes to playback of highres, the hard disk also can be a big point in there of course.

no, i don't believe you need another graphics card because you CPU is at 100%

oh forgot.. specially when it comes to playback of highres, the hard disk also can be a big point in there of course.
What i was trying to say is mainly,
no, i don't believe you need another graphics card because you CPU is at 100%


i went with GPU processing through use of jit.gl.slab and am still getting 100% plus system utilization on max. i put together this patch... is there something else i could try that will use less resources?

thanks for your response.
i went with GPU processing through use of jit.gl.slab and am still getting 100% plus system utilization on max. i put together this patch... is there something else i could try that will use less resources?


if you have a dual core the max is 200%, quad core = 400% etc

so assuming yours is dual core you actually have half of your CPU power left for other stuff.

that's an integrated graphics card (embedded in the motherboard of your computer), these have lower graphics performance compared to discrete laptop and desktop graphics cards

here's the standard video optimization starter: 

a lot depends on the codec of the source video file. see here: 

https://cycling74.com/docs/max5/tutorials/jit-tut/jitterappendixa.html

some years ago motion-jpeg was advised as the optimal codec. don't know if this still holds up. it might be interesting to see how resolume's DXV codec performs in jitter as it is developed for GPU decoding in VJ'ing apps: 

about CPU load:
100% = 1 core of your CPU
if you have a dual core the max is 200%, quad core = 400% etc
so assuming yours is dual core you actually have half of your CPU power left for other stuff.

about 9400m:
that's an integrated graphics card (embedded in the motherboard of your computer), these have lower graphics performance compared to discrete laptop and desktop graphics cards

about video:
here's the standard video optimization starter: http://abstrakt.vade.info/?p=147 (don't use pwindows like you did!)
a lot depends on the codec of the source video file. see here: https://cycling74.com/docs/max5/tutorials/jit-tut/jitterappendixa.html
some years ago motion-jpeg was advised as the optimal codec. don't know if this still holds up. it might be interesting to see how resolume's DXV codec performs in jitter as it is developed for GPU decoding in VJ'ing apps: http://www.resolume.com/software/dxv.php


forget about that dxv tip: "Note that hardware accelerated playback is only done when played in Resolume 3."

hardware support for jitter