VideoHelp Forum




+ Reply to Thread
Results 1 to 2 of 2
  1. I'm sure this is my fault rather than FitCDs, but I could really use someone giving an explanation for it:

    1. Load up the source .avi. It is correctly recognized as a 640x272 resolution 1:1 Monitor file. Source and Film Pixel are both 640x272, as they should be for this source.

    2. Change the destination dropdown to XVCD (704x480).

    3. FitCD says that the correct resize is 704x272, with no cropping of the original source. It claims this maintains the exact same aspect ratio! (2.3529)

    I'm thinking this is totally wrong. Resizing from 640x272 to 704x272 cannot be the same ratio! Shouldn't the 272 need to be scaled as well? This is what is given as the sample AVISynth script:
    BicubicResize(704,272,1/3,1/3,0,0,640,272)
    AddBorders(0,104,0,104)

    If this _is_ somehow correct, could someone explain why? Doing very basic calculations, 704x300 seems more correct.
    Quote Quote  
  2. As expected, this was my fault, but I'm unclear as to why. If someone could enlighten me, it would be greatly appreciated.

    I fought with FitCD some more, and I finally got it to generate the numbers that I believed were correct. As I said above, FitCD was loading the 640x272 source as 1:1 Monitor. I changed this to be DVD, and enabled the ITU-R BT.601-4 box. And gee, look at this! Suggested crop: 630x272, suggested resize 704x304! Exactly what I thought should be happening.

    The question then, is that why is 640x272 being initially identified as 1:1 Monitor?

    The following AVISynth lines give a perfect picture:
    BicubicResize(704,304,1/3,1/3,5,0,630,272)
    AddBorders(0,88,0,88)
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!