5
9 Comments

Stuck on a technical issue. Can anyone lend a hand?

Realize this isn't stackoverflow but I'm stuck on a technical problem - if any of you guys can lend a hand or an upvote, would be much appreciated: I've a bounty open too, so if anyone knows the answer, might as well go to an indiehacker.

https://stackoverflow.com/questions/65602021/corrupt-video-uploads-when-chunking-mediarecorder-to-google-cloud-platform

on January 9, 2021
  1. 1

    I don't think I can really help but I did generating files in the past, then sending them to Google cloud, and faced a similar problem.

    What I found - I did the bytes transformation wrong. You do it when you upload, and the second time - when you send to Google from your app. "Corrupt" often doesn't mean really corrupt, it may mean wrong decoding. So, the best way is to get the file as is (download it to your computer) and then you need to check the uploaded file, what is the difference (in size), and maybe the inner content was decoded wrong.

  2. 1

    Looks like you have some feedback. But I just wanted to say I feel your pain. Stack not getting the love it used to. Wonder why?

  3. 1

    I ran into something similar uploading backup ZIPs to an OpenStack object store with Laravel, and it turned out that the chunks of the ZIP file were being reordered when they were sent to the object store.

    Can you upload a "video" that's a text file that's just a bunch of lines that start with sequential numbers? Then you can download it and see if the numbers are in the expected order. I did this, then was able to eliminate things that could be reordering the chunks until I found the culprit.

    1. 2

      Great idea will give that a shot and see if I can write some ordering code. Couple other devs seem to think that might be the problem

  4. 1

    Can't answer personally, but I can invite you to a slack community for video developers (6k members) where you might be able to find someone to help. They really really know their stuff about video on there.

    1. 1

      That would be fab, more eyeballs the better chance I have to resolve.

  5. 1

    I threw up an answer there. It should give you a good start on where to begin your debugging.

    1. 1

      Gentleman thanks. Something to work with.