View Full Version : Removegrain, x264 and mkv
DigitalDivide
21st January 2006, 07:47
Hi, I currently use the undot filter in my encodes, mkv x264. I've read a bit about removegrain and wondering if I should use it instead? If so what exactly is the text that I enter into my avs script? I noticed that there are a couple of diff removegrain dlls in my folder. I couldn't find anything on this. I have a p4 2.8 and usually encode my movies to approx 2gb.
Also since I'm asking, am I better off using Bicubic resize or Lanzos? Still not sure what the diff is between them? I usually use Lanzos and am generally quite happy with my encodes but if I can squeeze a bit more quality without adding more time to the encode I'd be happier.
Thanks
JoeBG
21st January 2006, 08:02
This is a Avisynth question and Ißm sure this threat will get removed ;)
So a quick answer: RemoveGrain(mode=1) is identical to Undot() but faster
RemoveGrain(mode=2) is as fast as Undot() but also works with the chroma values.
RemoveGrain(mode=2) is a very good denoiser for DVD´s because in mode 1 or 2 the filter is fairly artifact free.
Read about it here (http://www.removegrain.de.tf/)
BigDid
21st January 2006, 08:26
+1 for mode=1
Concerning mode=2 some discussions in the autogk threads.
I now use mode=5 from the pre 1.0 release here: http://home.arcor.de/kassandro/RemoveGrain/
Possible to compare effects from the spreadsheet given.
Anyhow a quick and effective filter with multiple presets, pick your choice.
Did
CruNcher
21st January 2006, 11:00
you could also try x264 new internal noise reduction x264 -nr [value] something like 600 should be fine
JoeBG
21st January 2006, 13:45
you could also try x264 new internal noise reduction x264 -nr [value] something like 600 should be fine
but -nr 100 seems to have the same effect like undot() :)
DigitalDivide
21st January 2006, 17:07
Didn't realize this was the wrong area for this thread. Feel free to move this thread. So if I want to include removegrain in my avs script do I simply put in
LoadPlugin("C:\Program Files\GordianKnot\AviSynthPlugins\removegrain.dll")
removegrain(mode=2)?
I noticed there's a removegrains, removegrainsse2, removiegrainsse3. I'm assuming I should be using sse2?
As I go to removegrain 1 to 5 is each successive number removing more grain or less? I'd like to keep the image as close as possible to the DVD. If I don't see much of a diff between undot and say removegrain2, I guess I'll try 2.
shon3i
21st January 2006, 20:08
You sholud be try Convlution3D ("MovieHQ") because removegrain and undot doesn't do anythig or litle. DVD film have a strong noise which artent grain or with litle grain. This noise reduction in x264 what is recomended value or range.
BigDid
21st January 2006, 21:08
@digitaldivide
Did you read the spreadsheet from the removegrain pre 1.0 package?
If yes, it should be possible for you to choose between mode 5 to 9
If not please do so (link in previous post)
To keep as close to dvd as possible toggle from mode=1 (=undot) to mode=2 or mode=5 choose what best suit you
@shon3i
Now sir,
I will not say anything about Convolution3D ("MovieHQ"), you made a proposition as have other contributors, but stating "removegrain and undot doesn't do anythig or litle" is an accusation.
Either it is your opinion and you are welcome to rephrase your post (and also your spelling), either you want your assumption to be taken as facts (rule #2: respect the net-etiquette)
In this case I strongly urge you to give justifications and/or proofs. I am not the author (Kassandro) but I appreciate his work and I will forward your allegation if needed.
I will not engage in snapshot comparison but I made test encodes for the different modes and my conclusion is that removegrain mode 5 to 9 (beside mode=1) is good and quick at removing artifacts like grains/dots etc...
Have a nice day.
Did
PS: Going to hibernate until end of february except, maybe, for exceptions
Bye
shon3i
22nd January 2006, 02:06
I will not say anything about Convolution3D ("MovieHQ"), you made a proposition as have other contributors, but stating "removegrain and undot doesn't do anythig or litle" is an accusation.
I will not engage in snapshot comparison but I made test encodes for the different modes and my conclusion is that removegrain mode 5 to 9 (beside mode=1) is good and quick at removing artifacts like grains/dots etc...
I didn't say anithyng badly about removegrain and i am not say that Convolution3D ("MovieHQ") better solution for encoding. I have good encoding with Convolution3D ("MovieHQ"). And sorry on my bad english. btw What you recomend about removegrain i think mode.
Chainmax
23rd January 2006, 00:39
I read once that mode=2 blurs too much and that mode=5 is a much better choice. By the way, mode=1 is not exactly like Undot() because it also works in border pixels that Undot() doesn't process.
DigitalDivide
23rd January 2006, 20:29
Is the parameter for removegrain
removegrain(1)
or
removegrain(mode=1)
?
buzzqw
23rd January 2006, 22:23
the last
removegrain(mode=1)
BHH
DigitalDivide
24th January 2006, 15:05
Thanks, that might why it didn't seem to do anything for me...lol
Chainmax
24th January 2006, 17:33
By the way, better quality resizers probably do make encodes slightly longer and definitely lower compressibility, but if you want quality results stick to Lanczos4Resize(x,y).
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.