Phil wrote:
"Think about that... You too Jorel"
i'm trying Phil...but it hurt so much!
(just kiddin)

i understood....but please Phil, do me a favor,
test this script (do a sample) for me and post what you see wrong (if any) :

GripCrop(720,480,overscan=1,source_anamorphic=true ,dest_anamorphic=false)
BicubicResize(GripFit_resize_width,GripFit_resize_ height,0,0.6)
GripBorders()

i know, your sources are PAL, "transpose" it please!


waiting...

.
In fact first try was too awfull to decently report it. I mean it wasn't only bad "compared to tmpgenc". It's really bad "period". There is no way to consider what I obtained as watchable, even for a newbie.
But I used all parameters you gave to me. So I surely did a mistake somewhere. I have to check back and redo some tests before to take a conclusion. And I didn't find the time this we.

jorel, i think you don't understand Phil completely. He doesn't say that you sample will be wrong. He say maybe can have any error, cause of :
Murphy's law (do you know it?)
Do you want take this risk?
Anyway, if your sample is ok, go ahead. Why not?

In fact Jorel you already now that a resizer does not just resize the picture by deeply modify it : you never use Lanczosresize because with it you see "ants", isn't it ?

The same, you use bicubic precise (0 and 0.6) and not bicubic standard (0.33 and 0.33). Why ? Surely because you find the precise more "at your taste" than the standard one (ofen found "too soft").

This way you can understand that resizing is not a passive operation (like cropping). It's actually as "active" as a spatial filter like asharp or unfilter !

from Prodater64
"Anyway, if your sample is ok, go ahead. Why not?"
if nothing is wrong.....yeah,..why not?


Phil:
yes, i see "moving ants" using lanczos and don't like it!

and bicubic precise is my taste!

i always use asharp or unfilter (gentle values)!

again i understood!



but please Phil,
don't "think" in the result from the script that i posted.
do a sample and "SEE" if have something wrong, PLEASE


do you understand me now


i'm still waiting....

Sorry my pal but my faster PC is currently encodign a KDVD and the slower one is doing KVCDs
I won't have the possibility to test that now. But why do you want me to test that ? You already report that this script solved your problems with gripcrop. Why do you expect from me exactly ?

why?....you ask....

like Prodater64 wrote:
"I'm here learning (¡you are a professor!), i'm an "asker"!"

you are one of my professors here Phil,
this is the reason!
your opinion and the opinion of others professors here have weight!
don't need names, everybody knows who are this teachers, is very clear.


not kiddin,
i can wait.....

I would want to know:
1. When use letterbox(16,16,16,16) for movie 2.35:1 or 1.85:1 I do not lose nothing because I add the borders. It's true?

2. Why you use "cpu=4" since that incredible advises to use this option
for sources much compressed like divx?

by

CPU=4 is a spatial filter in general and therefore not only purposed to work with divx! Watch the source and its quality then you do choose if applying this filter is needed. (I do choose it almost everytime as it won't harm )

By letterboxing 16px at each edge, YOU WILL loose effective picture information BUT you won't recognise it as this area is WITHIN the overscan area of your TV and wont be shown anyhow.

See here where the Overscan-Thing is explained:
www.incredible.de.tf/aspectratios.html

ok, i have read your guide.

can I make an example practical?

we take a film 2.35:1

with
Crop(8, 72, 704, 432)

We make a frame 704x432 and crop on the left and right 8 px
while at the top and bottom 72px.

filters.................

with
Addborders(0,72,0,72)
we add the borders at the top and bottom (72px).


with
LetterBox(16,16,16,16)

We make the letterboxing 16px at each edge.

until it is all right here?
With this procedure from ours frame original we lose 8px on the left and 8px to right because of ours cropping.
Then we lose others 16px on the left and others 16px to right because of the letterboxing, these but we would have lost them however because of the overscan of the tv.

if I do not want to lose nothing, I will have to use then

Crop(0, 72, 720, 432)

but in this way I will have a frame of 720x432.

if I do not want to lose nothing with the letterboxing, what I have to do?
perhaps:

Addborders(16,72,16,72)
LetterBox(16,16,16,16)

it's right?
by

Everything is right.

If you don't want to lose anything you musn't use letterbox but you must RESIZE the picture to be fully outside the TV-overscan area and then add a border ARROUND the picture that will represent the actual area masked by the TV-overscan.

If you want to see visually the diff between letterbox (called also overlapping) and addborders (resizing) you can use moviestacker. Next the the "overscan" setting you have a "resize/overlap" choice. Change from one to the other and observe how crop and resize settigns change.

Just circles walking

Absolutly

This question was talked before in this same thread.
http://www.kvcd.net/forum/viewtopic.php?p=69187#69187

ok, it goes well, crop is better than resize. this I have understood it.
Why not fairies, inasmuch as you are of the experts, of the guides in which it comes explained all in clear way and exhausting.
"Object: Like making a Kdvd from a dvd ". A thread can be made in which explaining all problematic the relative ones to the object. I as an example have read to all the guide of vmesquita 2,00, but this not enough alone. For being able to comprise to bottom the argument I must read the several one post of the several one thread and ask, naturally, information on the argument. To times the questions are banal for who know already the matter. Many concepts base that emerge from the several one thread, second me, to have to be re-united in an only one thread, that they can serve from miniguides for all.
by

I understand your point but there is something that often (always ?) miss to people reading a guide : the guide reports only its author won advices/choices/tastes/habits !

No one has the only one truth. All is matter of taste and every tastes are in the nature.

In my KVCD guide for instance you would find "use besweet for audio, set it in stereo (and not dual chanel), do not use asharp in any script, and mux all with tmpgenc (not bbmpeg)".

Not sure this will be accepted by all readers here.

Be shure these 72px are correct on your 2.35:1 Source (encoding letterboxed non anamorph???)!
(I got a headache right now, so Phil will check that for you )

Actually 72 pixels is the border size for a 2.35:1 movie encoded in anamorphic.
If you want to make it letterboxed, the size is 104

BUT be carrefull ! All this is for PAL resolution (height = 576, not 480).

In all cases you must check the actual border size in DVD2AVI when you are doing the d2v project.

oh my GOD!

inc, Phil, zagor, Prodater64, Jell, everybody please:

do a picture using vdub

withGripCrop(720,480,overscan=1,source_anamorphic= true,dest_anamorphic=false)
# with or without overscan, no matter
BicubicResize(GripFit_resize_width,GripFit_resize_ height,0,0.6):
GripBorders()

and another picture loading the same source but using crop and letterbox
and post the 2 pictures here,PLEASE..
no matter how i use crop and or letterbox,i cut more than the borders,
i loose part of the scene

the only way to remove my doubts is if one of you post 2 pictures
using vdubmod(for example) with the 2 scripts!
no matter if is 720x480, 480x480, 352x240...your choice but...
please, post the 2 pictures here!!!

i need to see if you can use it WITHOUT loose part of the SCENE!
(sorry the caps lock,is to realce the intention)


please,not kiddin!