Quote:
Originally Posted by burt123
Hi byteshare,
Yeah, on further observation, I have noticed that the problem occurs on other encodes, not just with MDegrain, so I must have a problem somewhere.
Interested in your mention of a manual edit to use MDegrain3....more info on that, please
Yep, I have to agree with your idea about the servers activity at the end of a job....good idea !!!
But I'd still like MORE.....
|
MDegrain3 Grainy Stuff (Removes extra noise):
Code:
#Denoise
Loadplugin("YourPathHere\RipBot264v1.19.5\Tools\AviSynth plugins\mvtools\mvtools2.dll")
LoadPlugin("YourPathHere\RipBot264v1.19.5\Tools\AviSynth plugins\flash3kyuu_deband\flash3kyuu_deband.dll")
super = video.MSuper(pel=2)
bv1 = MAnalyse(super, isb = true, delta = 1, overlap=4)
fv1 = MAnalyse(super, isb = false, delta = 1, overlap=4)
bv2 = MAnalyse(super, isb = true, delta = 2, overlap=4)
fv2 = MAnalyse(super, isb = false, delta = 2, overlap=4)
bv3 = MAnalyse(super, isb = true, delta = 3, overlap=4)
fv3 = MAnalyse(super, isb = false, delta = 3, overlap=4)
video=video.MDegrain3(super,bv1,fv1,bv2,fv2,bv3,fv3,thSAD=400).f3kdb
Quote:
Originally Posted by slalom
You're talking about 3-5 minutes max of idle time. Not worth the trouble
|
That would depend on your encode settings/FPS, not to mention how many server you have sitting idle to multiply that by. With slow encodes that use MDegrain I can have a 60s clip take 30 or more min. so that means I can have all but 1 server idle for 30 min. just waiting for the job to end and start encoding again.