search

balintlaczko / VideoAnalysis

Non-realtime video analysis, exporting motiongrams and various quantitative features of movement in the video file.
https://www.uio.no/ritmo/english/research/labs/fourms/downloads/software/VideoAnalysis/
1 stars 0 forks source link

The motiongrams (and possibly other files) are rendered incomplete? #29

Closed aleksati closed 4 years ago

aleksati commented 4 years ago

For example, the exported horizontal motiongrams tend to leave blank half of the print happening on the x-axis (the axis which corresponds to the framecount), despite the dimensions and general programming seeming correct. The same goes for the vertical. Might be due to an unfortunate signal delay in the system somewhere? Might be something else though.

Could you give a look, Balint?

aleksati commented 4 years ago

Based on how the images look, the problem should be with the [dstdimstart] printing. But the code seems legit.

aleksati commented 4 years ago

I´ve identified that the problem lies with the frame-dumped output of the [jit.qt.movie]. By attaching a simple counter to the main [jit.qt.movie] output, I discovered that the output count is always significantly less than the total amount of frames of the video. Hence the incomplete-ness of the rendered files. These should correspond to enable correct motiongram printing and further analysis "down the line". Might be due to the size and CPU load of the patch?

balintlaczko commented 4 years ago

Could be that the [jit.qt.movie] has a fix FPS (like 30) by default regardless of the source video's FPS? Something something...

aleksati commented 4 years ago

i`ll check

aleksati commented 4 years ago

Jupp, part of the problem was the @unique attribute. When disabled it outputted the right amount of frames. But there´s one final problem now with the jit.op absdiff object in the [mgt.motion%]. It also messes with the fame output (naturally), affecting the motiongram print. I will look more into it later

alexarje commented 4 years ago

Yes, the @unique attribute will lead to not all frames being output. This is good when doing realtime stuff, but not so good when using framedump.

aleksati commented 4 years ago

I had to make some changes to the [mgt.motion%] to enable the absdiff to output the correct fps without causing every other frame to be blank (zero). But this is now fixed and looking good. The commit will come later.

aleksati commented 4 years ago

The motiongrams are now good. Issues with other files-exports are attended to in other issues.