-
Notifications
You must be signed in to change notification settings - Fork 6
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
[issue] Some device can’t record 15s SHORT by Capture camera. (Not using video uploading.) #2899
Comments
➤ Kenny Hung commented: Sam (cc Scott YanTammy Yang) Suggest arranging into 0717 sprint. |
➤ Kenny Hung commented: Sam (cc Tammy YangScott Yan) As our previous huddle, you said this task needs more discussion, could you provide potential solution? The expectaiton will be
|
➤ Sam commented: Kenny Hung, sure. Potential solution might be upload file in chunks. Currently we use base64 (it just large text) to upload capture. When we capture image/video
When we read image/video as base64 “object” it loads all data to memory and sometimes crash the app. So instead of using base64 we can use File and load file data in small parts and upload this small parts lazyly. (Upload file by chunks). I remember there was a discussiom regarding this before. I will find message and add here as well |
➤ Tammy Yang commented: Sam please involve James Chien and Olga for this discussion as it is related to the file accepted in the backend and their integrity |
➤ Sam commented: Kenny Hung, for this task I have 2 proposals.
The issue: starting from capture app 0.81.2 we limit asset size registration (client side). If asset size is more than 30MB ( https://app.asana.com/0/0/1204495833338689/1204888742400415/f ) we just show dialog and prevent asset registrations. This approach save app from crashing when user pick large video/image from gallery. But it will also prevent users from recording videos more than 3-4 seconds (based on user device camera) but camera can record up to 15 second videos. 1st proposal. as short term solution we can do the following.
Summary of 1st proposal.
2nd proposal might require some changes in backend.
Summary of 2nd proposal.
|
➤ James Chien commented: For 2nd proposal, I think backend could have a endpoint using S3 presigned-url to upload files. This could allow multipart upload and reduce memory footprint, network I/O on backend at the same time. However implementing it requires some efforts including adding checks to check if the upload completes, some refactoring to avoid duplicate code for create/delete assets, detailed doc to describe how the client side should upload the file. In short this is not a trivial task. So maybe in short term use proposal #1, and in long term plan #2 in later sprints? |
➤ Olga commented: Sam I tested streaming uploads to the current storage backend, and it worked fine. Could you attempt not using the base64 object and instead stream the file? This might help resolve the issue. |
➤ Sam commented: Olga can you please share the code or postman that does that (streaming upload)? |
➤ Sam commented: One thing is that with current implementation Not using base64 might require cascade changes because we use filesystem pluging that works with string only (aka base64) |
➤ Olga commented: Sam I wrote a Python ( https://toolbelt.readthedocs.io/en/latest/uploading-data.html#streaming-multipart-data-encoder ) script to accomplish that, but I believe it can be done in other programming languages as well. |
➤ Sam commented: Olga thank you for script. Yes I can rewrite that in javascript context. Thank you |
➤ Sam commented: Kenny Hung after daily sync we decided to go with proposal 1.
Maybe in the future we still need to implement proposal 2 https://docs.google.com/spreadsheets/d/1mKzKcD0LsU_B62kmhuf5RlmtdKMK6NEk2n2dIb-FkNg/edit#gid=1335272736 ( https://docs.google.com/spreadsheets/d/1mKzKcD0LsU_B62kmhuf5RlmtdKMK6NEk2n2dIb-FkNg/edit#gid=1335272736 ). But for now we go with proposal 1. |
➤ Kenny Hung commented: Sam (cc Tammy YangScott Yan) Need to confirm for this release, what is the status for this task? I try redmi note 10s, when user record 15s video by capture camera, app will crash, it doesn't show the File "File size exceeded..." dialog |
➤ Sam commented: Kenny Hung thats correct. If image/video from gallery → show file exceeded if more than 30 Mb if image/video from capture cam → show nothing, long videos might crash the app (since capture app 0.63.1) |
➤ Kenny Hung commented: Sam comment on milestone. (Comment by @kenny Hung on v230725-capture-app-ionic-internal ( https://app.asana.com/0/0/1205066099827825/1205208537505440/f )) |
➤ Kenny Hung commented: Tammy Yang (cc Scott Yan) Regarding this critical issue, needs your confirmation.
|
➤ Tammy Yang commented: Kenny Hung for big files (larger than 25MB), do not support on App but dashboard. |
User story
As a user, I want the ability to record short videos of up to 15 seconds using the Capture Camera feature.
Reproduce step
https://app.claap.io/numbers-protocol/video-upload-limitation-issue-c-O35CsUM4Uy-uxaqbTpMYeky
Expectation
User should be able to record 15s SHORT by capture camera
Additional information:
SamComment by @Sam on [Sprint 2] Upload video(SHORT)
Detail test data on android: Comment by @Kenny Hung on [Sprint 2] Upload video(SHORT)
1. No issue
1. Just accept less than
4
seconds video, over 5 seconds will display over 30 mb pop-up1. record 15s short will crash
1. Just accept less than 5 seconds video, over 6 seconds will display over 30 mb pop-up
1. record 15s short sometimes will crash.
1. No issue
1. No issue
1. Just accept less than
12
seconds video, over 13 seconds will display over 30 mb pop-up┆Issue is synchronized with this Asana task by Unito
┆Created By: Kenny Hung
The text was updated successfully, but these errors were encountered: