You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in the image sequencer, it seems there is no image sharpening module which can sharpen the image based on the intensity. This might be very useful for use cases where the image is a bit blurred and needs some sharpening.
The proposed idea for the module, I believe dates back to issue #1612
So, I managed to implement the functionality by applying a 3x3 convolution filter on a given image and transforming it according to this resource
The image does get sharpened but as the intensity is increased, the image gets overexposed.
Here are the relevant sources that confirm the same.
Screen.Recording.2021-03-14.mp4
@jywarren and @harshkhandeparkar, I would like to know if this is the expected behaviour of the algorithm or there is something wrong with my approach so that we can improve upon and add this functionality soon or is there a requirement for such module at all in the first place.
Thanks :)
The text was updated successfully, but these errors were encountered:
Currently in the image sequencer, it seems there is no image sharpening module which can sharpen the image based on the intensity. This might be very useful for use cases where the image is a bit blurred and needs some sharpening.
The proposed idea for the module, I believe dates back to issue #1612
So, I managed to implement the functionality by applying a 3x3 convolution filter on a given image and transforming it according to this resource
The image does get sharpened but as the intensity is increased, the image gets overexposed.
![Screenshot 2021-03-14 at 6 59 36 PM](https://user-images.githubusercontent.com/58583793/111071280-75074300-84fb-11eb-8655-92ac302f5a01.png)
Here are the relevant sources that confirm the same.
Screen.Recording.2021-03-14.mp4
@jywarren and @harshkhandeparkar, I would like to know if this is the expected behaviour of the algorithm or there is something wrong with my approach so that we can improve upon and add this functionality soon or is there a requirement for such module at all in the first place.
Thanks :)
The text was updated successfully, but these errors were encountered: