yetithefoot

5 ms·

1.
by yetithefoot 12y ago
Sure, you can test and compare it: http://raw.pics.io http://people.mozilla.org/~vladimir/demos/webraw/ http://dev.tag.is/rawson.js/rawson.html
2.
by yetithefoot 12y ago
We love DNG and I personally always recommend it. Unfortunately there are lot of manufacturers doesn't support DNG, thats why we support CR2/NEF.
3.
by yetithefoot 12y ago
If you talking about lossless DNG compression — yes we support it. If you talking about lossy DNG compression — no. We already added Exposure Compensation to http://raw.pics.io , and we think about upcoming features. What feature
4.
by yetithefoot 12y ago
AFAIK these 3D-engines was specially prepared to be ported to JS. We have abit another specific than just moving 3D objects, creating scenes and blend textures. Sure, its very similar, but our "textures" is bigger and we should kn
5.
by yetithefoot 12y ago
What Lightroom features is the most meaningful for you? What do you think?
6.
by yetithefoot 12y ago
Images like this are created due to bug in our JPG decompression algorithm — I like this one and put it as a post title photo. =))
7.
by yetithefoot 12y ago
The problem is not only with WebGL. Unfortunately we don't support it yet, but working hard on it.
8.
by yetithefoot 12y ago
Come-rad is right — emscriptened code is not very maintainable, so we cant rely on it. More than that we use alot of JS-specific performance optimisations that allows us to run faster than any of those autogenerated libs.
9.
by yetithefoot 12y ago
We also played with dcraw running on asm.js. It actually a blackbox with no control. Our current implementation is more fast because uses platform specific optimisations code. I personally spend alot of time optimising it for running in Jav
10.
by yetithefoot 12y ago
Before start, we investigated and learned tons of theory and alot of libs. Rawspeed is my personal best and we compared our results with it. Now in raw.pics.io we implement simple bicubic interpolation algorithm which optimal in speed/