-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Writing video from bytes produces corrupted video with Dropzone #2223
Comments
Same issue here. Some files are uploaded ok. But usually Video files is not uploaded ok. MP4Box say it is truncated on server. And the each md5 hash values are different. In my case, files which size is more than 200MB makes problem. I guess it is because Before I try dropzonejs, I made multithreading uploader with web workers by myself but It failed with same issue. Need help. |
Hi @magic-thomas and @tengerdata , I tried multi-part upload for large files using web-workers, but i see that it still freezes the UI interactions somehow (the ui shouldn't freeze since i'm using webworkers). |
My goal is to chunk client-side video uploads to separate .mp4 files that are under 100MB in size. I came across an open source library Dropzone.js that can accomplish the task I want to achieve.
Bits and pieces of my current code.
templates/upload.html
:flask_app.py
:Directory structure:
My goal:
My current problem is that the chunked video clips that are outputted become corrupted video files. I cannot play them in VLC or Windows Media Player, they either raise an error message, or just freeze.
I can see that they are chunked properly, since a 145MB video gets split into two .mp4 videos with the first chunk being just under 100MB, and the second chunk being the other 45MB. What gives me hope is that when I used an online corrupted video fixer (https://fix.video/), I can see that the broken contents of the video are recovered as what I expected; however, I don't know how to fix it in my code.
Any help appreciated. Thanks very much.
The text was updated successfully, but these errors were encountered: