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

Computing and storing the motion vectors #10

Open
michaelshiyu opened this issue Jun 20, 2019 · 0 comments
Open

Computing and storing the motion vectors #10

michaelshiyu opened this issue Jun 20, 2019 · 0 comments

Comments

@michaelshiyu
Copy link

Hi Chao-Yuan,

First of all thanks for sharing this great work! I am trying to train on my own videos so I need to extract motion vectors (MVs) first, which I'm trying to do by calling your CoViAR's loadmethod (a big shout out for that work as well!). I have two questions:

  1. The load method, by default, computes the MV w.r.t. the previous frame, correct? So to get the "after" flows as specified in the sample training/eval data, I can call load for a second time on the video with its frames reversed, correct?

  2. By looking at read_bmv, it seems that to convert the int32 MV into uint8, you added 128 to all of its elements and possibly did another clamping to [0, 255]. I'm not very familiar with MV so could you please explain a little bit on why this will not cause loss of information?

Many thanks in advance.

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

1 participant