-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reducing blocking? #5
Comments
Misoperation, sorry. |
Yes, it is possible by specifying |
Yeah, I'm already doing that. But what I mean is "using block_step smaller than basic estimate in final estimate". I mean if the "non-blockiness" of block_step basic and final (5,4) and (3,3) are close, that could still be some performance improvement, right? |
Each basic = bm3dcpu.BM3D(src, block_step=5)
final = bm3dcpu.BM3D(src, ref=basic, block_step=4) for your purpose. |
Well, thank you so much! I didn't know each function call olny corresponds to one estimate before. |
During some simple tests, I noticed that higher value of block_step will make more blocking when sigma is high, and block_step=8 will cause a few visible blocking even when sigma is relatively low (~5).
As mawen mentioned in this issue: HomeOfVapourSynthEvolution/VapourSynth-BM3D#18 (comment), using smaller block_step in final estimate will decrease some artifacts (including blockiness).
Is it possible to do in this implementation?
The text was updated successfully, but these errors were encountered: