I want to give this new HybridFuPP script a try, but have 2 questions. Using this new function with TMPGenc:
a) Should I use the "High Quality" setting or the "Motion Estimate Search" seting? b) Should "Detect Scene Change" be checked or unchecked? Thanks, Icarus |
Quote:
But I was relating the word combination: (FU)FuPP(MA)Motion Adaptive a(N)d (CHU)lerias :lol: As for FUBAR, it's a term used in many programming examples and documentation almost everywhere. It stands for: (F)uc..d (U)p (B)eyond (A)ll (R)ecognition :hihi: ( Relating it to the complexity of the script, of course. Not to the functionality ) -kwag |
I have problem using HybridFuPP_071_b.
It complains about "no MotionMask" function. I saw on waterenterprise that it is included in Mpeg2Dec2 and Mpeg2Dec. The first one does not exists for avs2.5.4 (is that normal ?) so I installed Mpeg2Dec. Now the message is "MotionMask : no argument named thY1 (hybridfupp line 116) " :-( Can you help me ? |
Hi Phil,you need to get the correct version of masktools 149
http://forum.doom9.org/showthread.ph...0&pagenumber=2 Its about a quarter way down |
Quote:
Thanks :-) |
Its weird i was getting no motionmask(blah blah)when i was using a different version of masktools but since i got 149 no more problems
|
Quote:
|
Here is another place if anyone else is having trouble finding it
http://mf.creations.nl/avs/filters/ |
I tested the script, and it is great. However, there is a flaw :!:
After every scene change, there are trails of the prior scene, on the scene just after the change. Nobody saw this :?: -kwag |
@kwag
I can't see any of these flaws you're refering to. 8O Could you describe it more, please? BTW I'm using "Motion search precision: High quality (slow)" in TMPGEnc. If you're not, please try again with that setting... EDIT: No matter what "Motion search precision" I set I can't seem to get the flaws you mentioned... |
Quote:
Not to mention some color bleeding artifacts that I also noticed on some scene changes. Here, look at these screenshots, and look at the artifact from the first shot, clearly visible on the second shot. The planet's "halo", is clearly seen on the second shot, but not on the third shot. http://www.digitalfaq.com/archives/i.../2004/03/1.png http://www.digitalfaq.com/archives/i.../2004/03/2.png http://www.digitalfaq.com/archives/i.../2004/03/3.png |
I see what you mean, kwag. But no matter how hard I look I can't see any trace of this phenomenon on the movies I've encoded with HybridFuPP... :? Could you please post the script you used?
|
Quote:
Code:
## DLL Section ## |
Wierd :!: :? I'm lost... Do you use the latest version of the filters used in the function? I don't know if it makes a difference but what the heck...
|
Quote:
Mpeg2Source("K:\RED_PLANET\VIDEO_TS\red.d2v") Crop(11, 60, 698, 360) HybridFuPP(704, 272, Preset="High", Chroma=False ) ... or do not set the resolutions in HybridFupp if using the whole bicubic command as Hyb.Fupp it gots an internal incoming stream width/height detection ... As I remeber when I couldn't resist looking at the avsi inside ;-) |
@kwag
This is how my script looks: Quote:
|
Quote:
Is there really any advantage to do it that way :?: -kwag |
I have absolutely no idea. :roll: You're the script wizard kwag... 8) :wink:
|
Quote:
Well if advantage or not, if choosing Bicubic and its 0,0.6 algorythm you're already affecting/sharpening the Image before entering into Hyb.Fupp! So IF using Bicubic then change from 0,0.6 to 0,0 So I also do correct myself and recomend to let Hyb.Fupp do all the resizing including the usage of crop() before. |
Quote:
Quote:
-kwag |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.