felixge

22 ms·

211.
by felixge 16y ago
Sure, but we think it's possible to "prepare" those videos on the client site before uploading.
212.
by felixge 16y ago
Do you have any references for youtube doing this? Youtube is the example I always mention when it comes to long waiting times after an upload : ).
213.
by felixge 16y ago
yes, 2-pass encoding will not be doable in realtime.
214.
by felixge 16y ago
We are feeding raw bytes into a command line ffmpeg process via standard input. Ffmpeg only reads as much from stdin as it can process. Node.js gives us a 'drain' event when this happend, which means we can pump more data into it. So we are
215.
by felixge 16y ago
> if a user has their upload stream redirected to your service, and for some reason this upload is unable to finish, are we now forced to have the user try the upload again? If the upload doesn't finish the user needs to redo it. >
216.
by felixge 16y ago
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
217.
by felixge 16y ago
Thanks for the suggestion, we definitely screwed that up.
218.
by felixge 16y ago
We know we're a little expensive. But we did this so we could lower pricing in the future (which we will), and to attract people who are getting more value out of our service initially. If you have a project and pricing is a deal breaker, j
219.
by felixge 16y ago
The fact that it's not actually faster is the entire beauty of it. While our competitors have been super busy to actually make their encoding faster, we have just taken a huge bite of free launch by making the encoding happen in parallel.
220.
by felixge 16y ago
We have one ffmpeg process for each upload, yes. From our tests with the kind of videos we mostly deal with (user generated content), this seem to work quite well while only requiring reasonable memory allocations. So sure, there could be p
221.
by felixge 16y ago
No, we don't pay the MPEG-LA (yet). The information they provide has given us reason to believe that we don't need a license at this point.
222.
by felixge 16y ago
> Unless you are just measuring the time between the upload finishing and the transcode being done. That is what we are measuring indeed. > But why would a user care about that metric rather than the total elapsed time? Because that
223.
by felixge 16y ago
It only encodes uploaded files.
224.
by felixge 16y ago
Of course. But since most people upload with insanely slow speeds, we can actually handle a spike much better with this feature than we could before : ).
225.
by felixge 16y ago
As you can probably tell, we are super excited about this, feel free to ask me anything : ).
226.
Realtime encoding - over 150x faster(transloadit.com)
128 points by felixge 16y ago|70 comments
227.
by felixge 16y ago
Just a few fun experiences I had with vps.net: * A server reset itself to a 3 month old backup overnight, their support was unable to explain it. * Random disk I/O issues bringing throughput to < 1 MB/sec * My favorite: Some internal ro
228.
by felixge 16y ago
No, in fact this style is a little unusal for isaac. Maybe there was beer involved ; )
229.
by felixge 16y ago
Yes, http://github.com/felixge/node-gently . However, it's still rather minimal and I'll add more stuff to it now that I actually know what I need to do with it frequently.
230.
by felixge 16y ago
> Keep in mind, the degree of TDD insurance I'd pay for is different for every project--for a Mars Rover you bet I'll test my accessors. Sure. If you write Mars Rover software you'll also want somebody to review your tests to make sure
231.
by felixge 16y ago
You can get value out of writing a test after the fact. But the value is higher for a test that you have written before the code because you have seen the test go from failing to passing. This way you know it will also fail if you break the
232.
by felixge 16y ago
I know it's not a ruby library, but I also know I don't know a lot about it. Thanks for the link, I'll try to see if I can extract some usable concepts from it : ).
233.
by felixge 16y ago
Yes, that is an integration test. You need both.
234.
by felixge 16y ago
Yes, plus you'll be doing less rewriting because you spend more time and thoughts on getting it right in the first place.
235.
by felixge 16y ago
Statically checked language have certain advantages and disadvantages. As far as speeding up the process goes, I always have test and code in a vim splitscreen, along with a keybinding that allows me to run a test from within vim. It takes
236.
by felixge 16y ago
The core of our service is a REST API, so we don't have to deal with that much. For browser interaction we would probably use a combination of Selenium (for system tests), and maybe qunit for the frontend testing. But anyway, I am no expert
237.
by felixge 16y ago
I hope I'm not giving you the wrong picture. We did have to cut features when rewriting our software (after node.js changed all APIs) using TDD. It does take more time to write tested code, and you do not get an advantage until you have t
238.
by felixge 16y ago
I think BDD would be a nice addition to our system tests. However, I have not worked much in Ruby, and from the outside it is hard to tell whether those cute DSL's are more poetry or business ; ). (Don't get me wrong, I love cute code - but
239.
by felixge 16y ago
Regarding competitive advantages: We are working on a new feature that will allow us to encode video uploads while they are still uploading. This change will affect the most critical aspects of our code base and it's very easy to introduce
240.
by felixge 16y ago
> Do you find it hard to change directions with a feature or component, because your tests have sort of "locked you in" to the structure you were working on? Do you mean changing the direction of the implementation, or the outcome of th

More ›