graysky
27th September 2008, 10:55
I'm using the "XviD: 2pass HQ" template on MeGUI 0.3.0.2017 to downsize some xvid files from HD sizes.
# Set DAR in encoder to 16 : 9. The following line is for automatic signalling
global MeGUI_darx = 16
global MeGUI_dary = 9
AVISource("\\nas\todo\1.avi", audio=false)
LanczosResize(640,352) # Lanczos (Sharp)
My question is about the # of threads I should use for a quad core chip... 4 or 6? x264 has an auto threads (0), but in the profile for xvid, I don't see this option - I have to select an integer.
A value of 6 gave about 104 fps on the first pass and ~70 % CPU time for xvid_encraw.exe.
A value of 4 gave about 135 fps on the first pass and ~50 % CPU time for xvid_encraw.exe.
# Set DAR in encoder to 16 : 9. The following line is for automatic signalling
global MeGUI_darx = 16
global MeGUI_dary = 9
AVISource("\\nas\todo\1.avi", audio=false)
LanczosResize(640,352) # Lanczos (Sharp)
My question is about the # of threads I should use for a quad core chip... 4 or 6? x264 has an auto threads (0), but in the profile for xvid, I don't see this option - I have to select an integer.
A value of 6 gave about 104 fps on the first pass and ~70 % CPU time for xvid_encraw.exe.
A value of 4 gave about 135 fps on the first pass and ~50 % CPU time for xvid_encraw.exe.