Modifying annotation FPS with GCS import

[kelseylmartin]

Is there a config file that we could build or a setting that we could select when uploading videos through the girder? Currently, the default is 10 FPS when uploading videos with no way to change that parameter.

@csbrown-noaa @BrendaTran

[BryonLewis]

Are you talking about the girder interface and asset store importing from GCP, or the standard DIVE interface?

[BryonLewis]

The Client stores this setting locally to a user's browser during upload:

Video FPS will on import calculation the framerate of the video and make the FPS the same as the video FPS.

This setting is saved in the browser so if you upload a new file it should have the same frame-rate. Image-sequences will default to 1fps so that each frame is an image in the sequence.

[kelseylmartin]

I'm talking about the girder assetstore.

But it looks like the dockered detector model is not retaining the fps information contained in the first line of the viame csv. Additionally, it is not populating the second column at all (example below).

@mattdawkins

[BryonLewis]

For the assetStore import it should default to the native video frame rate during import unless it is overrridden by something inside of a annotation file like the VIAME CSV.
If you navigate to the DIVE Dataset Folder in the Girder interface you'll be able to see the native video fps under originalFPS:

[kelseylmartin]

Correct. Right now I'm attempting to view a clip of a video that may have been exported by a third party site at 10 FPS; however, I need the annotation file to display the correct information so that it doesn't default to the video FPS and takes in the annotation FPS.

For example, our normal videos are filmed at 60 FPS but we process the annotations at 5 FPS. I understand that this information is usually stored in the annotation file but currently, the dockered models are not outputting the correct information in the annotation file (see screenshot from previous comment).

[csbrown-noaa]

It sounds like maybe this is an issue for the VIAME/VIAME github? @BryonLewis if the CSV file that the VIAME CLI tool generates has an FPS in the metadata, then the expected behavior of DIVE is that it will respect this when we load the data through Girder import?

[BryonLewis]

@csbrown-noaa : yeah, that is the expected behavior

@kelseylmartin : this is something I've been meaning to do for a while. I think I can make it so the owner of the dataset in the interface can change the annotation FPS. I.E being able to after the fact change it from 60fps of the video to being 5 fps. One thing is that when you change the annotation fps, the interface treats each 'frame' as being at the new fps. I.E instead of each frame moving forward 1/60 of second it will now move forward 1/5 of a second. Playing a video will still work properly just when pausing and using the arrows/frame advancement it will snap to the closest 1/5 of a second.

Another thing to note is that videos that are encoded at 29.97fps (old NTSC broadcast fps for embedded color) or the double of that at 59.94 fps can start to get weird when using a lower framerate, because you are hitting times between frames. This goes for regular frame rates as well, it's best to use a whole number factor of the original frame rate to prevent fractions and times that occur between frames.

[kelseylmartin]

If the dockered models produced the expected output in the viame_csv then I think that would produce the desired result. As of right now, we are missing the FPS information in the metadata row along with all of the data in the second column.