how to tell if divx502 encoding with dual processor and not just single?

[takeru]

i have a dual athlon system, but i can't tell if divx502 is encoding using both cpu's, since its only going at 8-12fps. smart deinterlace is on. is this normal speed for a dual 1800+ system? :confused:

[Acaila]

Check the cpu load you get (task manager), if the average is 50% it's only using one, if it's over 50% it's using two.

[drmr_vr]

you have to use windows NT to enable the second CPU, and the NT task manager shows you the load on the two CPUs independently so you can see for yourself
but i think that divx502 can't still use more than one CPU but i'm not very sure about this

[DJ Bobo]

@ drmr_vr
I don't have double CPU, but I'm pretty sure it can, since the Gej DivX PC that was in the eBay auction at the moment of the release of DivX5 had double CPU, so DivX5 can exploit 2 CPUs definitely.
As you said, the OS must also support this, so Win 2K or XP is needed I guess (I havn't said NT since I don't consider it as a home user OS)

[Acaila]

DivX5 isn't the only thing that influences your speed. The programs you use to encode play a major part as well, as does the amount of filtering you do on your video.

If you use Avisynth->VDub and add a spatial, temporal, ivtc, deinterlace, etc. filter, no matter how SMP efficient DivX5 is you'll still end up with only 50% cpu load. The more filtering you use, the more you'll shift the balance towards one processor (because Avisynth/VDub aren't completely SMP capable either).

For the full benefit use nothing except cropping and resizing, but often you have to use some other filters as well. Basically just try to live with what you get :)

[MaTTeR]

Is Divx 5.x really doing any kind of multi-threading? AFAIK the real multi-threading is happening within Vdub and/or AVS in my case. Do an encode with DVD2AVI instead of Vdub/AVS and I bet you'll see that the CPU usage stays around 50-60% at the most if I'm not mistaken. If your using Vdub/AVS methods with no filters then your almost guaranteed to see the CPU usage around 90-98% all the time.

My point...I don't think Divx 5.x is really all the intelligent on SMP machines, more likely it's the encoding method. However, XviD is SMP aware and will be more effecient on MP systems once they clean the code up a little more:)

Edit- It might be safe to say the system that DXN/Gej built was more designed for Vdub/AVS than Divx 5.x:D

[takeru]

i am only using a resize filter. i see it only using 54% cpu.
d2v -> tpr -> vfapi -> vdub

[DJ Bobo]

@ takeru
Mattaku! still using such outdated methods?!
After DVD2AVI, make an AviSynth script, which you load in VD in Fast Recompress mode, works a loooot faster and is a lot better than your actual method (unless you're doing manual IVTC of course :D)

A typical avisynth script for a telecined anime would be:

loadplugin("...\mpeg2dec.dll")
loadplugin("...\ivtc.dll") <- get IVTC2.2 from the download page
loadplugin("...\decomb.dll") <- optional
mpeg2source("projectname.d2v")
ivtc(44,11,95)
FieldDeinterlace() <- optional
crop(a,b,x1,y1)
Bicubicresize(x2,y2)

you may add filtering lines if you want.
Check the avisynth forum for more details about that.

[takeru]

well of course i do manual ivtc too. i do auto first and then manually tweak it. so time consuming but worth it sometimes.
:) i am using win2k advanced server. hud is set for multi-processor, so shouldn't it recognize it and use both cpu's for divx encoding? photoshop uses both cpu's.

another thing about avs. i tried using avs a few times in the past already. first of all, for some odd reason, using vobsub in the avs script kills the encode and it won't do anything. so basically i can't burn in subs to the encode. second, i like to use tmpg for ivtc (auto then manual). still can't compare the quality of eyeball killing manual method. :)

[MaTTeR]

Originally posted by takeru
so shouldn't it recognize it and use both cpu's for divx encoding? photoshop uses both cpu's.


Like Acaila mentioned above...if your chaining filters or using something like IVTC then your going to see your CPU usage drop considerably. With no filters except for resizing, then you should be seeing both CPUs almost maxed out when using Vdub with AVS.