Resize or not resize, that is the question.
Is it worth to resize to 704*576 when we are doing 1:1 or 2:1 DVD backups?
If we keep resolution 720*576, encoding will be really faster, or not? |
For 1:1 I use to not resize to not introduce artifacts due to the resize (whatever the resizer, there is always more or less artifacts).
But for a 2 movie DVD (is that what you call 2:1 ?) you should resize to 704 because you will gain a lot of precious bits. |
That's what I usually do, resize to 704x576.
A doubt: also resize to 704x576 when encoding anamorph?. |
Quote:
|
720 --> 704 via resizing??? Since we do encodings in 704 we never used "resizing" from 720. That will end up in a generic PAR and not 128/117!
IF we go from 720 to 704 then we do use CROP, why? Because both will be played back using 13.5Mhz. The window of 720 is 53,333µs The window of 704 is 52,148µs The window of TV is 52,000µs So 704 comes nearest to the TV. All other higher widths can only bee seen on a NON Analogue TV device like a PC Monitor. When using 720 or 544 that is inefficient for TV purposes 704 or 528 is the best relation IF you do encode for TV purposes. So 704 by just using crop doesnt result in resizing interpolation artefacts, its faster and anyway you wouldn't see the pixel data gain of 720 on your TV. |
Quote:
All what you are speaking about is managed by crop/border calc. Noone never meant that the resize is done by a simple XXXrezize(704,576) command line in the script. * for memory : 720 -> 704 with FitCD first crops to 712, then resizes. |
Quote:
Why doesn't crop straight to 704? |
Quote:
Using crop will give you the same film area that if you read directly the DVD on the TV set, but not all the picture that you should have on an over screen like a plasma (or like Inc says : "on a NON Analogue TV device like a PC Monitor") But of course, this introduce some artifacts so you can choose to loose pixels insteed. Not: I just checked my scripts and for a 1 movie DVD I crop to 704 then letterbox for overscan. I thought I encoded in 720 but no, I never used that res finally. |
Quote:
Crop and letterbox, crop and addborders. When we use FitCD or Moviestacker, they give a script with resizers, so they are resizing. Hot to do for not resizing? |
I answered in my previous post (that I was modifiying while you typed your question ;-))
Quote:
|
Quote:
|
And the script, extracted from a very old thread (that means that the filters used are now obsolete - forget this part) :
http://www.kvcd.net/forum/viewtopic....ght=crop#68572 |
Quote:
Quote:
crop from 720 to 704x576 and apply an overlayed overscan by using letterbox(16,16,16,16) finally This avoids scaling/interpolation and shows the DVD content in its samne area like it would have been played back as original where also these pixels in the letterbox area wouldnt have been shown. You can use the argument "But I want to keep/see more of the given 720x576 active pixels." But then you have to resize. |
Quote:
Thanks. |
Quote:
Encoding at 704 is faster to encoding at 720, this answer to your question about speed. But this 704 can be obtained by cropping or resizing. And the two methods won't have a great difference in term of speed (except if you use Lanczos as resizer that is a little slow). So your choice is still : do you want to lost pixels (and so use crop) or to keep all pixels (and then use resize). |
Quote:
Mpeg2Source("PATH\NAME.d2v",cpu=4) Crop(8, 72, 704, 336) # 72_72 #Crop(8, 16, 704, 448) # 16_16 #Crop(8, 0, 704, 480) # fullscreen FluxSmooth() TemporalCleaner(ythresh=5,cthresh=7) Undot() DCTFilter(1,1,1,1,1,1,0.5,0) Addborders(0,72,0,72) # 72_72 #Addborders(0,16,0,16) # 16_16 LetterBox(16,16,16,16) :?: Which filters are currently deemed "best" for single movie DVD's (to replace the ones above)? Simple questions, but I have a tendency to screw things up without some guidance from you guys. :oops: Currently using only: RemoveGrain(mode=2) TemporalSoften(2,3,3,6,2) |
Quote:
Quote:
Quote:
And even that one (even it keeps most pixels of all) does a tiny bit erase details. |
Thanks, Incredible. :D I'm now trying to locate LRemovedust(). Several posts mention it, but it is a bit confusing. :?
|
hi nicksteel, look here for lremovedust:
http://www.kvcd.net/forum/viewtopic.php?t=16094 It's a function, and there are 2 versions: for SSE capable and non SSE capable cpu's. You should definitely try it, it works like a charm :D |
Quote:
The values I gave (72 and 16) are for PAL sources (2.35 and 1.85). For NTSC sources I don't know how large are the black borders you have to remove. Check it first on a source ! And for filters I use RemoveGrain().Deen(). Nothing more. |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.