motion search precision in tmpgenc?
hi,
motion search precision in tmpgenc; is there any noticable difference setting from high quality to very high quality when encoding :? my other question is; i have a 28" 100hz widescreen tv and would to fill the screen with my kvcds and not have the black borders, is this possible? cheers all. |
A) Difference will be much more time you need, but IMHO no visible diff.
B) You can by doing a PAN-Scan on your encodes or a proportional Zoom afterwards using your TV set. First method you shouldn't do cuase you'll kill movie informations at the sides AND you'll need much more bitrate to encode with, and in case of KVCD where we need as less bitrate as its possible, you'll end up with a worse quality result. So use your Zoom function of the TVset IF avaiable. Uops ... how do they appear on your 16:9 Set? Still little black bars on top and bottom in case of an encoded 2.35:1 Movie? Or did you just forgot that 16:9 mode-Zoom in case of 4:3 sources... everything is possible ;-) |
A) Motion Search Precision set to "Very High Quality" will actually produce a clip that is larger encoded as "High Quality". And as incredible said: No visible differences.
In fact you should go with Motion Estimate Search, since it produces the less artifacts from all these plus it's VERY fast. :wink: |
Quote:
|
hey guys
thanks to all who answered my first question :D incredible, yes when playing widescreen dvds 2.35:1 i still get those black top and bottom borders but they are not as big as when i produce a kvcd at say a 544x576 res if i could produce the kvcd to a 2.35:1 ratio i would be very happy. any help mate? cheers. |
Quote:
Even when you play a DVD that is 2.35, the standalone feed the TV set with a black bordered 16:9 image. |
Quote:
|
Could you please explain what are "MA scripts" and "statics"? I guess there's a lot I don't know.
|
MA = Motion adaptive
This means that a script contains routines/filters which do act individual based on what happens in the frames. In Case of the KVCD MA script there is a command included Ydifferencetonext() And here's the MA part of Kwags optimal Script: Code:
ScriptClip(" nf = YDifferenceToNext()" +chr(13)+ "unfilter( -(fmin(round(nf)*2, 100)), -(fmin(round(nf)*2, 100)) ).TemporalSoften( fmin( round(2/nf), 6), round(1/nf) , round(3/nf) , 1, 1)* ") This value will be used mathematical to individual set continously the applied filters (unfilter for blurring and TempSoften for cleaning) in the script on each frame. And "static" means you "just" use a script where every filter does use the exact same values on every frame. |
Quote:
Also I thought that Motion Estimate Search produces less artifacts in STILL scenes (DCT blocks on flat surfaces). In still scenes there won't be a big difference between MA scripts or static ones no? |
Quote:
But remember, months ago the optimal setting was "High" and by experience I can say that Motion Estimate is not good with the script I use. Quote:
Quote:
|
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.