lils000 / xvid4psp

Automatically exported from code.google.com/p/xvid4psp
GNU General Public License v2.0
0 stars 0 forks source link

Some requests #22

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Any chance of incorporating again MSUFramerate between framerate converter 
options?

Original issue reported on code.google.com by martines...@gmail.com on 17 Jun 2011 at 4:07

GoogleCodeExporter commented 8 years ago
No. It`s very slow, it`s accepts only mod16 resolutions (both for height and 
weight) and can change framerate only by an integer values. In my own tests 
ConvertMFlowFPS was much faster and quality of m.e.\interpolation was better.

Why do you need MSUFRC?

Original comment by forc...@gmail.com on 19 Jun 2011 at 9:27

GoogleCodeExporter commented 8 years ago
I usually do upscaling to MKV 1080p/24 frames and the MSUFRC convert between 
9-11 fps with my PC (Phenom2 X6 +4 GB Ram 1055T) regardless of the source file. 
With the 2-4 fps ConvertMFlowFPS encodes the same presets. I agree that quality 
is far superior but the fps drop very drastically in my case, (codified 
clarified that black bands completely Rescaling image with a 16:9 format and 
preset to 1 pass very strict).
 Wondering if you could add, because I do not know how to achieve the same speed as the MSUFRC not know how you tune the ConvertMFlowFPS.
 With the same, keep using the old version of XviD4PSP. Sorry for the bad English but I translate with Google because I speak Spanish.

Original comment by martines...@gmail.com on 19 Jun 2011 at 6:13

GoogleCodeExporter commented 8 years ago
"to MKV 1080p/24" - to 24fps? And what was the source framerate? 12fps? As I 
stated before, MSUFRC can change the framerate only by an integer values (i.e. 
x2, x3, x4, x5,..), so if we need to change fps from 25 to 60 there were 
two-steps processing: 1. x2 with MSU_FRC (25->50) and after that with ChangeFPS 
(50->60). And if destination framerate is lower than source*2 (we want 25->30 
for example), then only ChangeFPS were used and step 1 was ommitted.
So, if 24fps for output wasn`t a typo and your source fps is not 12 or lower, 
then when you switching to MSUFramerate you actually switching to ChangeFPS, 
wich is pretty fast. Thats how it was before r233..

Original comment by forc...@gmail.com on 20 Jun 2011 at 1:20

GoogleCodeExporter commented 8 years ago
Thanks for the reply and clarification, I really know how it worked internally 
such filters.
Thanks again for the effort you make to refine the program and evacuating doubt 
those who use it.

Original comment by martines...@gmail.com on 20 Jun 2011 at 5:45

GoogleCodeExporter commented 8 years ago
OK :) Since there is no more questions, this issue is closed.

Original comment by forc...@gmail.com on 9 Aug 2011 at 8:44