News for hackers. Stuff that matters.
Re:Realtime encoding - over 150x faster by sophacles on Monday December 20, 2010 @03:16PM (#2025624)
I demand you address the OP question of why you haven't fixed the physical constraints of crappy upload bandwidth? Seriously, wtf would we pay your for otherwise? </snark>
Re:Realtime encoding - over 150x faster by felixge on Monday December 20, 2010 @03:22PM (#2025638)
As funny as this sounds, fixing the upload bandwidth problem is also something we will work on. Getting a good route between your users and servers can make a real difference.

So at some point in the future we'll offer upload servers in all major geographic areas.

Re:Realtime encoding - over 150x faster by nitrogen on Tuesday December 21, 2010 @02:34AM (#2027242)
It's interesting how difficult this can be. I was recently evaluating Linode locations for a new virtual server, and though I'm geographically much closer to California, the Texas location gave me almost 20x the download speed. To be precise, I was able to download from a California node at 300K/s, while I got close to 6MB/s from Texas.

Comcast used to route my traffic to California through Seattle, Washington, then down to San Jose and then Fremont, but now, it's going to Texas first, then across to San Diego, then up to Fremont, across a saturated link.

Re:Realtime encoding - over 150x faster by jodrellblank on Monday December 20, 2010 @03:21PM (#2025637)
Yeah, why don't they make a 150x faster javascript encoder, then I only have to upload much less data! </derp>
Re:Realtime encoding - over 150x faster by randallsquared on Monday December 20, 2010 @03:33PM (#2025674)
You're derping, but a browser plugin seems like it might actually be a good idea for this. Even if JS is too slow, someone who uploads lots of video through a site might well be willing to install a little plugin to make it faster, especially if it comes with other simple things like queuing a directory of videos, etc.
Re:Realtime encoding - over 150x faster by robryan on Monday December 20, 2010 @07:09PM (#2026328)
Wonder if something like the Google Native Client would be good for this in the future? (Don't know a whole heap about it so may be off the mark)
Re:Realtime encoding - over 150x faster by barrkel on Monday December 20, 2010 @07:42PM (#2026419)
NaCl might be good for doing the transcoding on the client side before uploading - and would be especially helpful if the transcoding is a downsampling (i.e. reducing stream length), and if the client machine is beefy enough to do it without adversely affecting performance when pumping out bits at the rate of the upload connection.

However, it wouldn't be particularly useful for things like queuing uploads from a directory. The point of NaCl is running native machine code in a provably secure sandbox. It's about making possible web app features faster on the client side, rather than adding new capability, per se.