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

Blank (gray) event frames in the output video #58

Open
mohsij opened this issue Oct 23, 2023 · 2 comments
Open

Blank (gray) event frames in the output video #58

mohsij opened this issue Oct 23, 2023 · 2 comments

Comments

@mohsij
Copy link

mohsij commented Oct 23, 2023

Hi,

I've been using the latest version of v2e and it seems that some frames are either blank (gray) or the event pixels are all less intense than the last frame. The object in the input video is moving consistently. The last good commit for me is 1edd9e3 where the event frames look consistent and I get no blank frames.

My run command is:
v2e -i frames --overwrite --input_frame_rate=10
--timestamp_resolution=0.1 --disable_slomo --auto_timestamp_resolution=False
--dvs_exposure duration 0.1 --output_folder=event_data --overwrite --pos_thres=.15 --neg_thres=.15
--sigma_thres=0.3 --dvs_text events.csv --output_width=1280 --output_height=720 --cutoff_hz=30 --avi_frame_rate=10
--refractory_period 0 --dvs_aedat2 None

What was changed after that commit that I could get blank frames?

Thanks

@mohsij
Copy link
Author

mohsij commented Oct 24, 2023

The only problem with commit 1edd9e3 is that I get 717 event frames output from an input of 720 frames. With the commits after that I do get 718 but then run into the issue outlined i.e some blank frames and some with less bright pixels even though the movement is consistent.

It looks like the renderer outputs batches of 7 frames at a time and the first frame in each batch can either be blank or with 'muted' event pixel intensities. See attached side-by-side below of frame 00006.png and frame 00007.png.
image

@tobidelbruck
Copy link
Collaborator

Thanks for providing commit number. That commit only pushed changes to some synthetic input examples.

Did you check that you are using correct switch:

--dvs_exposure DVS_EXPOSURE [DVS_EXPOSURE ...]
                        Mode to finish DVS frame event integration:
                        	duration time: Use fixed accumulation time in seconds, e.g. 
                        		--dvs_exposure duration .005; 
                        	count n: Count n events per frame,e.g.
                        		--dvs_exposure count 5000;
                        	area_count M N: frame ends when any area of N x N pixels fills with M events, e.g.
                        		-dvs_exposure area_count 500 64
                        	source: each DVS frame is from one source frame (slomo or original, depending on if slomo is used)

In your case did you use --dvs_exposure source option?

Also, if you really disabled slomo upsampling, then

 --batch_size BATCH_SIZE
                        Batch size in frames for SuperSloMo. Batch size 8-16
                        is recommended if your GPU has sufficient memory.

should not have any effect.

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

2 participants