VideoHelp Forum




+ Reply to Thread
Results 1 to 9 of 9
  1. Member
    Join Date
    Jul 2006
    Location
    United States
    Search Comp PM
    Can anyone explain to me what are those numbers from?

    BicubicResize(336,224,0,0.6,0,6,640,468) <---- the numbers...


    I've read a few guides and so far they all got me headache... so if anyone would explain this to me, it would help a lot. Ya, I know... im a nab at this.
    I'm using FitCD for scripts to fix overscan problem. It helped a lot but...
    --------------------------------------------------------------------------------------
    # -= AviSynth v2.5.7.0 script by FitCD v1.2.8 =-
    AVISource("C:\Documents and Settings\Compaq_Administrator\Desktop\Stuff\Anime\ DN Angel\DN Angel - 10.avi")
    BicubicResize(336,224,0,0.6,0,6,640,468)
    AddBorders(8,8,8,8 )
    #Trim(0,33556).FadeOut(150)
    -----------------------------------------------------------------------------------------
    The one above is a bit too big

    ----------------------------------------------------------------------------------------
    # -= AviSynth v2.5.7.0 script by FitCD v1.2.8 =-
    AVISource("C:\Documents and Settings\Compaq_Administrator\Desktop\Stuff\Anime\ DN Angel\DN Angel - 10.avi")
    BicubicResize(304,208,0,0.6,0,0,640,480)
    AddBorders(24,16,24,16)
    #Trim(0,33556).FadeOut(150)
    --------------------------------------------------------------------------------------
    This one is good but there still is a little amount of space left by the right of the image which is no problem... though too much space left there by the top and the bottom of the screen. (when I watch the VCD on my TV, i mean) So this one is a bit too small.
    Therefore I'm kinda looking for something in the middle of those two scripts above. But, I would appreciate it if you explain to me how that script works so I can at least "try" to edit it myself :P ...

    Not only im nab at those videos stuff but my English is terrible, too. Sorry if there are any parts you don't understand of what I'm talking about @_@
    Quote Quote  
  2. Hi-

    BicubicResize(336,224,0,0.6,0,6,640,468)

    336,224 is the final resolution (before adding borders), 0,0.6 are the BicubicResize parameters (nice normal figures), and 0,6,640,468 are the crop figures. The cropping is done so that after being resized and encoded it'll have the same aspect ratio as the source (640x480). It's cropping 6 pixels from both the top and bottom, none from left or right.

    It looks to me like the first script uses 1 block overscan, and the 2nd script 3 blocks overscan. So, I guess you want 2 blocks overscan.
    Quote Quote  
  3. Member
    Join Date
    Jul 2006
    Location
    United States
    Search Comp PM
    You are right about the first script that I used 1 block overscan but the 2nd script, I used 2 blocks overscan.... They should've put the 1.5 blocks overscan option...
    And what you had there... that should help a lot if i actually understand what parameters and aspect ratio are... ;__; There are a lot for me to learn *sigh*...
    Before I posted this topic, I pretty much figured out (was a wild guess) that the lass 4 were cropping (not that I know much about what cropping is...) Although I was wondering why it was there even though I can just edit the AddBorders part... so, I guess here come the aspect ratio problem, not only the script...

    I wonder when I can actually even edit a script like this Zzzzz....
    Quote Quote  
  4. Hi-

    but the 2nd script, I used 2 blocks overscan

    Sorry, my mistake. I was just going by the looks of it, and didn't check FitCD.

    that should help a lot if i actually understand what parameters and aspect ratio are.

    Maybe I should have chosen my words more carefully. The 0,0.6 for BicubicResize means it's not making it too sharp (as 0,0.75 or 0,1.00 might), so there's no edge enhancement or ringing being added, and it's not making it too soft or blurry (as 0.33,0.33 might).

    Aspect ratio is the width to height. The original 640x480 AVI is 1.33:1. Your ultimate goal is a 352x240 DVD, I guess, although I don't know why you want to give it such a low resolution. Maybe you're one of those that likes to cram as many episodes as possible into a DVD (or VCD?), and don't much care what it looks like. Anyway, after cropping, resizing, and adding borders, it'll also play with the correct aspect ratio. People won't look short and fat, or tall and thin, and the sun and moon will really be round, instead of oval shaped.
    Quote Quote  
  5. Member
    Join Date
    Jul 2006
    Location
    United States
    Search Comp PM
    So I'll need calculation for the script in order to get a correct "aspect ratio"?
    If so, how do I do it? And ya, I'm making VCD, it want to start VCD first before actually going for DVD cuz I heard that it's easier (not sure though).
    And does "correct aspect ratio" mean to have the same proportion? If so... when I used the calculator 640/336 and 468/224 don't match... so ya, I'm believe I'm wrong.
    Thanks in advance
    Quote Quote  
  6. So I'll need calculation for the script in order to get a correct "aspect ratio"?

    You got the script from FitCD, right? That's one of its functions, to give you back good scripts that produce proper AR. As long as you plug in the source and destination carefully, you can use the scripts as it gives them to you. For example, if you don't check anamorphic for destination, make sure you don't encode for 16:9. If you do intend on encoding for 16:9, make sure you check the anamorphic box. Have you seen FulciLives' guide for FitCD? Everything you ever wanted to know:

    https://forum.videohelp.com/viewtopic.php?p=1487285&highlight=fitcd+easytouse#1487285

    And does "correct aspect ratio" mean to have the same proportion? If so... when I used the calculator 640/336 and 468/224 don't match

    They'll have the same proportions at playback, and that's what counts. Your AVI gets scaled 1:1. Your VCD gets resized by 4:3. DVDs can be resized by 4:3 or 16:9, depending on how they were encoded. You don't really have to understand it at this point. Suffice to say, they're not supposed to have the same proportions before being encoded. Maybe this will help (and maybe not):

    http://www.doom9.org/aspectratios.htm

    And if I were doing it, I'd skip right over learning to make VCD or SVCD and go right to DVD.
    Quote Quote  
  7. Member
    Join Date
    Jul 2006
    Location
    United States
    Search Comp PM
    Ya, I already read that guide before but what I'm looking for is something in the middle of 1 block overscan and 2 blocks overscan... Since 1 block is a little too big, and 2 blocks is a bit too small. The width of the 2 blocks overscan is alrite when watch on TV but I wanna extend its height a bit. But all those aspect ratios made my head ache =/
    So ill need some calculations... but I don't really know how to calculate them considering how the numbers keep changing when I use different blocks overscan on FitCD.
    For example... the 1 block overscan uses crop, the 2 blocks doesn't, and the 3 blocks does... and I don't really know how to calculate those stuff for the correct aspect ratio...

    And the reason why I use VCD is because it's cheaper since doubtfully I will get it success by the first try.

    At first, I thought I would only have to add the video file into Nero and burn it and I'm done but then the overscan problem got me all the way to this... Those video stuff are complicate @_@
    Quote Quote  
  8. OK, I think I can help there. I may not get it exact, but close enough so you shouldn't notice any glaring aspect ratio errors. If you're getting either not enough borders, or too much borders, and you want an in between, then make the resolution slightly larger, keeping roughly the same aspect ratio, and then create AddBorders so that the final resolution becomes 352x240 (or whatever you want). So, starting with the 2 blocks overscan script:

    BicubicResize(304,208,0,0.6,0,0,640,480)
    AddBorders(24,16,24,16)

    The ratio (304/208) is 1.4615:1. Add 12 to the width and 8 to the height. It's a similar ratio of 1.5:1, and kind of in between the 304x208 ratio with 2 blocks overscan, and 336x224 with 1 block overscan, becoming:

    BicubicResize(316,216,0,0.6,0,0,640,480)

    I chose the 2 blocks overscan one to work with because, I agree, it's easier without having to worry about the cropping.

    Now 316/216=1.4630:1, a ratio very similar to the original.

    And AddBorders to make it VCD compliant (352x240):

    BicubicResize(316,216,0,0.6,0,0,640,480)
    AddBorders(18,12,18,12)

    Why do you have to do this anyway? Unless you have burned in subtitles being cut off, I wouldn't even bother. There are many people better at this than I. If I've done it completely wrong (very possible), I hope one of them will explain the math to you so you can do it easily yourself.
    Quote Quote  
  9. Member
    Join Date
    Jul 2006
    Location
    United States
    Search Comp PM
    thanks a lot for the help ... Kazaa kinda messed my computer up so I guess I gotta do it later... thanks though
    Quote Quote  



Similar Threads

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