Skip to content
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

Allow user to smooth bounding box transition #32

Open
balintlaczko opened this issue Feb 29, 2020 · 4 comments
Open

Allow user to smooth bounding box transition #32

balintlaczko opened this issue Feb 29, 2020 · 4 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@balintlaczko
Copy link

Even a little smoothing of what [jit.findbounds] returns can get rid of a lot of flickering.

@balintlaczko balintlaczko added the enhancement New feature or request label Feb 29, 2020
@balintlaczko balintlaczko added this to the More functionality milestone Feb 29, 2020
@alexarje alexarje modified the milestones: More functionality, v2.1 Mar 15, 2020
@alexarje
Copy link

Yes, good point.

@aleksati aleksati self-assigned this Mar 19, 2020
aleksati pushed a commit that referenced this issue Mar 22, 2020
…y parameter to the Box-image with [VA_findbounds_interpolation], and option to export Videograms in the Menubar. Issue #32 , #40 , #44 .
@aleksati
Copy link

aleksati commented Mar 22, 2020

I added [VA_findbounds_interpolation] to the box-image now which interpolates between median values coming from the [jit.findbounds]. This should smooth the drawing of the box rectangle pretty well. These median values are based on N-large lists of boundmin and boundmax values.

Therefore, I added a sensitivity parameter to the box-image section in the UI that specifies how large the lists are in which the median values are derived. This gets rid of a lot of flickering especially when tuning the sensitivity together with the radius and threshold parameters.

However, it might need some more finetuning. Especially to find a good default setting. Great if we can test this a bit further.

@alexarje
Copy link

Yes, I am struggling to find good values here. This function is not very important, I think. I implemented it for a particular project, but I haven't really used it much myself, and not sure if others have either. So I wouldn't say that it is high priority.

@aleksati
Copy link

Jepp, there is still some work to be done here, and I have a few things in mind. But let's not focus on this right now, as you said. Ill relabel this with a 3.0 label.

@aleksati aleksati modified the milestones: v2.1, v3.0 Mar 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants