digitalFAQ.com Forums [Archives]

digitalFAQ.com Forums [Archives] (http://www.digitalfaq.com/archives/)
-   Video Encoding and Conversion (http://www.digitalfaq.com/archives/encode/)
-   -   Overscan with MencodeMe (http://www.digitalfaq.com/archives/encode/9835-overscan-mencodeme.html)

maurus 05-24-2004 10:19 AM

Overscan with MencodeMe
 
I know how make overscan with AviSynth, but...

It is possible with MEncodeMe without script .avs.

How I set CROPPED zone for a overscan=2 (16 pixels). MencodeMe do also the AddBorders()?

Thanks.


-Maurus

Prodater64 05-24-2004 10:31 AM

Re: Overscan with MencodeMe
 
Quote:

Originally Posted by maurus
I know how make overscan with AviSynth, but...

It is possible with MEncodeMe without script .avs.

How I set CROPPED zone for a overscan=2 (16 pixels). MencodeMe do also the AddBorders()?

Thanks.


-Maurus

Maybe with this tool.



--------------------------
Visit: Intermediate guide: MencodeMe/Win32 - Avisynth - MakeAvis by Prodater64.
Visit: KVCD - MencodeMe - Auxiliar Task - KVCD Docking Gate by Prodater64.
Visit: Mencoder scripting with AVSEdit and Guide for Multiple Files by Prodater64.
Visit: Mini-guide quick and easy - DVD to (S)KVCD with MencodeMe by Maurus.
Visit: Mencode-me: a newbie oriented GUI - 0.23 is out! by VMesquita.
--------------------------

maurus 05-24-2004 11:28 AM

I see this tool, but I ask is it's possible set the overscan with current version of MEncodeMe 0.23 (CROPPED values), without any manually action.

I suposse, for a overscan=2 (16 pixels):

CROPPED Wdth: 464, Height: 560

How about the add borders in MEncodeMe (AddBorders( 8,8,8,8 ))?

Thanks.

-Maurus

incredible 05-24-2004 12:28 PM

Quote:

Originally Posted by maurus
I see this tool, but I ask is it's possible set the overscan with current version of MEncodeMe 0.23 (CROPPED values), without any manually action.

I suposse, for a overscan=2 (16 pixels):

CROPPED Wdth: 464, Height: 560

If you want apply an "overlayed/cropped" overscan area of 16px - means 2, that will be done by subtracting 16px on EACH side:

width= 480 -(16*2) = 448! (totally correct would be also here subtracting 8*2px as the "active"! px area at mod16 of 480x576 on a Tv is -8+480-8=464px!

height= 576 -(16*2) = 544!

result is 448x544 (432x544)

The addborders() command in mencoder is called Expand! Which is also shown in MenCalc. But it uses another logic as it "expands" to the final resolution using the needed black borders.

maurus 05-24-2004 05:36 PM

Overscan=2 is:

For script AviSynth (from FitCD):

Code:

BicubicResize(448,544,0,0.6,4,0,712,576)
AddBorders(16,16,16,16)

For MEncoder (from MenCalc):

Code:

-vf scale=480:576::0:9,crop=432:544:24:16,expand=480:576:24:16
Quote:

Originally Posted by incredible
width= 480 -(16*2) = 448! (totally correct would be also here subtracting 8*2px as the "active"! px area at mod16 of 480x576 on a Tv is -8+480-8=464px!

height= 576 -(16*2) = 544!

result is 448x544 (432x544)

My resolution is 448x544. I not understand 432 value...

Another question. If I use MenCalc with MencodeMe I have to edit temp.conf, edit this crop, expand values and then execute encode.bat?

Can I use this values direct in the GUI?

Thanks.


-Maurus

incredible 05-25-2004 04:02 AM

Quote:

Originally Posted by maurus
Quote:

Originally Posted by incredible
width= 480 -(16*2) = 448! (totally correct would be also here subtracting 8*2px as the "active"! px area at mod16 of 480x576 on a Tv is -8+480-8=464px!

height= 576 -(16*2) = 544!

result is 448x544 (432x544)

My resolution is 448x544. I not understand 432 value...

As I told above ...

In 480x576 Mode ... On Tv the effective Active Pixel area is 468x576! And thats a fact the same as If you would encode to 720x576 where in that case the effective Active Pixel area is 702x576

But as we do encode mod16 based these values now will be rounded to mod16

468x576 becomes therefore 464x576! at 0 overscan!

Because ONLY the 468x576 of the 480x576 will be stretched to 768x576 1:1 PAL square pixels the rest is out of bounds and WILL NOT be displayed, even if your TV wouldnt have an overscan area! Thats also the reason why it makes no sense to reencode a 720x576 to 720x576 for TV purposes as the active pix..area of that one is as said 702x576! in mod16 = 704x576.

Now lets add the overscan to 464x576

-16+464-16 = 432 pix width
-16+576-16 = 544 pix height

Your NEW active pix area is now 432x576 which will be "expanded" by just adding the black borders to:

480x576

And ... as the vertical alignment should be macroblock based:

576-544= 32 and therefore Mod16
therefore 16px borders at top and 16px borders at height will be applied

480-432= 48! and thats NOT Mod 16
but we at leas keep the width centered aligned so ...
24px borders at right and 24px borders at left will be added, where each of the 24px borders do have a macroblock (16px) inside which gives us a gain in compression as our mpeg encodings are macroblock based. ;-)

You dont trust me?? ok, ... its a lot of theory.
But in case of doubts do watch this site:
http://www.uwasa.fi/~f76998/video/co...nversion_table
(look at the 480x576 row in the PAL table and you can see at "actual active picture size" the 468x576 size ;-) )

This site is a reference used in FitCD, Moviestacker and my MenCalc.
BUT FitCD i.E. uses a "resized" overscan where mine uses "overlayed" overscan ... which results in diff. results
Also FitCD & Moviestacker do FIRST crop, Then Scale and then adding borders, mine does FIRST scale, then crop and then expanding (adding borders) ... so the approch is different (the same way as discribed in the link above) ... but the result on TV WILL be the same. ;-)

maurus 05-26-2004 07:09 AM

I understand your very good explanation.

In MenCal, this are the settings for PAL KSVCD overscan=2:

Code:

vf=scale=480:576::0:9,crop=432:544:24:16,expand=480:576:24:16
I not have any NTSC DVD... and I can't select this option in MenCalc. :cry:

Can you tell me this settings for KSVCD NTSC Overscan=2?

Thanks

incredible 05-26-2004 08:17 AM

Whats your source?? PAL or NTSC??
As if you gon in with ntsc, therefore NTSC resizings lists come up
IF you go into it with PAL resolutions PAL res. lists come up.

BUT! I figured out that in some AVI input cases MenCalc behaves strange when parsing. Im actually updating Mencalc where this issue will be solved.

maurus 05-26-2004 09:02 AM

My source is PAL, but I ask for NTSC...

But I think than I found the correct values for MEncoder:


For PAL KSVCD with Overscan=2:

Code:

-vf scale=480:576::0:9,crop=432:544:24:16,expand=480:576:24:16
For NTSC KSVCD with Overscan=2:

Code:

-vf scale=480:480::0:9,crop=432:448:16:16,expand=480:480:24:16
Thanks.

-Maurus


All times are GMT -5. The time now is 05:03 AM  —  vBulletin Jelsoft Enterprises Ltd

Site design, images and content © 2002-2019 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2019 Jelsoft Enterprises Ltd.