I'm one of the developers at Facebook who worked on this library since its conception! Really excited to be able to share this library today! I'll be checking up here periodically and can help answer any technical questions that you have!
> provided Your Software does not consist solely of the Software
Why didn't you guys choose MIT or BSD? It feels like the custom Facebook license is close to the intent of these, but it has that mysterious gotcha.
In any case, thanks for the software! It looks really slick, and I definitely have a use case for using it to replace the sprite sheet I used for Donald Trump on jungle.horse.
[1] https://github.com/facebookincubator/Keyframes/blob/master/L...
[0] https://help.github.com/articles/github-terms-of-service/#f-... Section F.1: "By setting your repositories to be viewed publicly, you agree to allow others to view and fork your repositories."
Software = Keyframes software.
Your Software = Whatever you are releasing.
So basically they are saying you can't redistribute just the Keyframes software library by itself. Which also means, if I understand this right, you can't fork it and modify it either.
I agree however, not a good license.
(in that case, they even used it to distribute a patch to ffmpeg, which is LGPL)
> Word of warning: while I'm not a vampire, I may or may not be a night owl.
That totally sounds absolutely non-suspicious... Also, you may or may not be having a HN-driven traffic spike.
> We actively welcome your pull requests. Fork the repo and create your branch from master.
Thanks.
Presumably, if blender formats the composition in the supported structure and doesn't drift outside what the library recognizes and supports, it should work.
https://github.com/facebookincubator/Keyframes/blob/master/d...
http://www.nytimes.com/2016/11/22/technology/facebook-censor...
The license [1] doesn't look to be as encumbered as some of Facebook's other open source licenses, but does include a clause I found to be strange:
> provided Your Software does not consist solely of the Software
So if I'm reading this correctly, it means only Facebook can redistribute this software? Wat.
[1] https://github.com/facebookincubator/Keyframes/blob/master/L...
I don't mean to be unpleasant (really!), but I don't understand what kind of answer you are expecting to get.
The only non-trivial answer one can give is also the most obvious: Facebook doesn't want to make free software.
Stated differently: why the assumption that Facebook is in the business of Free software? Or are you just expressing the desire for all companies to produce Free (in the Stallmanian sense) software? Or are you reacting to the implication that Facebook's software qualifies as free?
I only bring this up because these kinds of loaded questions have a way of devolving into flame-wars.
Presumably if you added a unique feature it might not "consist solely of the Software". But that clause isn't the troublesome one -- "modify the Software for your own internal use" makes it crystal clear that this is absolutely not Open Source.
Question: I assume you have some corpus of the recorded speeches of DT. How are you mapping those to words? A broader discussion about how you implemented jungle.horse would be interesting...
Thanks!
Huh?
Didn't I just read a whole blog post saying that one of their requirements was fast loading from disk, small bandwidth usage, etc? And that's what justified creating an entirely new image format from scratch, not something the internet is really suffering a shortage of already?
I know JSON is fashionable but that ending just seems kind of ridiculous. What's wrong with a binary format? Use Cap'n'Proto and mmap it! Saying numbers represented as text compresses well was the icing on the cake. No shit!
Also I think you have to pick something human readable here. One of the great things about SVG is that it's in XML so you can read it, tweak it, etc. It's super handy when you want to make small changes that only affect the image. So I see using JSON as pretty handy.
Don't forget there are many types of formats out there that have 2 types: a binary and human readable type. One used typically during debugging and one used for optimal over-the-wire transport. I don't see why this couldn't be possible at a later time.
Edit: I don't understand the downvotes. Over-optimizing is a thing. For a one time download I don't see the handfuls of milliseconds you're saving mattering. In either case of receiving a binary or JSON you will store it in an optimal format on the device...
With gzip sizing is about the same, but processing speed wise it is not.
Fields are serialized to tag numbers instead of field names in the binary format, so it's easy to rename fields. This also saves a ton of space versus JSON.
Proto "messages", analagous to structs in other languages, are typesafe, negating the need for a separate schema definition language. They support optional and sum types too.
So many languages have great protobuf libraries available. (I'm hoping one becomes available for Rust soon--as well as gRPC.) It would be amazing if the browser vendors would come together and standardize it as a first class browser serializarion format. It'd save so much bandwidth to emit protos instead of JSON.
Cap'n'Proto has pretty great support for Rust, from what I hear.
Previous options were exporting SVG animations, rendering to bitmap spritesheets or png sequences - or having to write a spec for the AE animation and recreate it in iOS/Android.
Since Adobe moved quite some effort away from Flash and towards HTML I'm pretty sure that they would now also support exporting keyframe animations from one of their standard tools into a native browser format.
Have you tried font-iconification services like http://fontastic.me/ ?
This should be wrappable by a React Native Component, it really is screaming for somebody to do that...
It means nothing
> A library for converting Adobe AE shape based animations to a data format and play it back on Android and iOS devices.
You still need to be able to produce the animation at first place.
Does it represent a lot of work by skilled technicians? Undoubtedly. Is it interesting in it's own right? Frankly I think not.
The surrounding question of the socialization of the internet is interesting, to be sure, but at the end of the day these are just animated emojis...
You don't think having an easy way to create high quality animations for any purpose that work on multiple platforms is interesting...? You might not find the current application of it interesting but that's like saying React isn't interesting because someone used it to make another Flappy Bird game.
I see neither.
Analogously: TCP is pretty amazing, but I don't expect an app that uses a simple TCP socket to self-aggrandize on the pretext of technological innovation.
It would be more if they'd have created an extension to the SVG standard that they'd just parse out via JS. Then it'd just be a polyfill, and could easily be integrated natively in the future, and gain support on other platforms, too.
This will change the world for a few months, modifying the standard would change it for years.
The purpose of an analog is not to be exactly identical, otherwise it would be called an equality.
I really don't see what there is to write home about. This article reads as a PR announcement (which is okay) disguised as a technical achievement (which it isn't).
They're "just" animations.
still interesting though. gonna check it out.
Just saying.
