25 ms·
Sure, basically other encode video second by second, we can do this in parallel on salable cloud infrastructure. We also released a blog-post on this, based on
by slederer 11y ago
Sure, basically other encode video second by second, we can do this in parallel on salable cloud infrastructure.
We also released a blog-post on this, based on a writeup from our infrastructure partner Google Compute Engine here: https://www.bitcodin.com/blog/2015/08/how-bitcodin-utilizes-google-compute-engine/ https://www.bitcodin.com/blog/2015/08/how-bitcodin-utilizes-...
- mkagenius 11y agoHi Stefan, Glad to see someone doing this. I am assuming the process goes like this: 1. Segment the video first - upload them to cloud. 2. Let Map-Reduce do the transcoding on the individual segments. 3. Fetch the segments back at a place. 4. Create the manifest file listing the individual segment. Is that roughly correct? Since you are doing this on GCE, I am assuming you are not using GPUs, only CPUs, right? Transcoding aside, how are you serving the video, where do you store it and which CDN do you use?
- slederer 11y agoyes, it's more or less how you described it, we just added some tweaks here and there to make it work in practice :-) ad 1.) no, we first grab the video from the user and then segment it in the cloud Yes, we just run CPU instances. Typically the user transfers the file back, e.g. via our FTP-transfer, S3, GCS, or simple download as zip.
- mkagenius 11y agoThanks for the reply. I tried it. Just the resource allocation took 2 min and the transcoding was done in 15 seconds for a 4 min video, so looks good. Regarding selling this thing, I don't know if there could be any good use case for normal people. New enterprises could be better target. Old enterprises too can benefit if their current price is more than what you are providing.