Handle too short recordings

[ComradeVanti]

Currently we don't handle the case well when the user stops the recording very quickly. There are two situations which can come up.

Either, when not a single frame was recorded, we just go back home.

Or if just a few frames were recorded we do get to results, but it does not work right because there is not enough data.

What could be some better behavior here?

[ComradeVanti]

We could enforce a minimum recording time. Users need to record at least 1s before the stop button becomes clickable. This would solve this problem

[SantiagoCalvo]

This sounds good to me, Also for the keyframes, I can add some logic to allow the presentation of the results screen without any keyframe (we don't capture keyframes in the first 2 seconds of the recording).

[ukarfs]

You are right, however, I haven't encountered this outside of the emulator - in the app, not enough data leads to the app redirecting back to the start screen (since earlier versions :))

[ukarfs]

Update - you are right^2:
-behaviour when no data --> back to start screen (which is fine)
-behaviour when little data --> visualisation error

another problem is loading the sessions - the faulty sessions still appear in the list of sessions. When selected, the error redirects the user to the start screen

[ComradeVanti]

another problem is loading the sessions - the faulty sessions still appear in the list of sessions. When selected, the error redirects the user to the start screen

Having a min-record time would also fix this