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

Processing images from video #9

Open
bhack opened this issue May 27, 2024 · 13 comments
Open

Processing images from video #9

bhack opened this issue May 27, 2024 · 13 comments

Comments

@bhack
Copy link

bhack commented May 27, 2024

Is there any specific setting to take advantage of images from video sequences?

@jytime
Copy link
Contributor

jytime commented May 27, 2024

Hi @bhack we are preparing for this and should be available in next version.

@bhack
Copy link
Author

bhack commented May 27, 2024

Do you have just another planned version or paper?

@jytime
Copy link
Contributor

jytime commented May 27, 2024

yes we are planning to release a new version of (a) a hugging face demo that can run on arbitrary input videos and (b) training script. The new version will also reduce the gpu usage by half

@bhack
Copy link
Author

bhack commented May 28, 2024

Do you will have also an option to mask non rigid pixels in video mode?

@bhack
Copy link
Author

bhack commented May 29, 2024

@bhack
Copy link
Author

bhack commented Jun 25, 2024

@jytime So is there something available in the new V2?

@bhack
Copy link
Author

bhack commented Jun 28, 2024

In the case currently we cannot autocluster/classify rigid and non rigid points can you at least support an init mask on the dynamic parts in the tracker?

@jytime
Copy link
Contributor

jytime commented Jun 28, 2024

Hey,

Currently, we do not have an update on the video processing feature as we are focusing on improving memory efficiency, as the mem problem seems to bother many people.

Regarding non-rigid pixels, you have two options:

(a) Avoid using non-rigid points as query points. You can achieve this by passing a mask to the get_query_points() function

vggsfm/demo.py

Line 453 in 8c47df8

def get_query_points(query_image, query_method, max_query_num=4096, det_thres=0.005):

or

(b) set all non-rigid points as non-visible, such as done at:

vggsfm/demo.py

Line 236 in 8c47df8

# If necessary, force all the predictions at the padding areas as non-visible

All the non-visible will be ignored during triangulation.

@bhack
Copy link
Author

bhack commented Jul 6, 2024

What kind of mask density this is going to require over a sequence? How many query you are preparing?

@cv-lab-x
Copy link

cv-lab-x commented Jul 25, 2024

any schedule to release the version of processing video ?
Looking forward to your reply, thanks.
@jytime

@jytime
Copy link
Contributor

jytime commented Jul 25, 2024

Hi I am doing it now. I am comparing different methods to filter out dynamic objects in the videos. One potential solution is something like @bhack mentioned above. I am also comparing the off-the-shelf motion segmentation methods. Let's see which will win.

@bhack
Copy link
Author

bhack commented Jul 25, 2024

Yes I've shared other fresh resources and comments in the other issue #24 (comment)

@jytime
Copy link
Contributor

jytime commented Jul 25, 2024

Thanks for sharing these all. A lot of distractions recently. Hope I can do my best to share it as soon as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants