News for hackers. Stuff that matters.

yetithefoot

Re:In-browser RAW Processing: How We Did It on Thursday May 15, 2014 @08:26AM (#7749001)
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.
Re:In-browser RAW Processing: How We Did It on Thursday May 15, 2014 @08:23AM (#7748993)
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 features are the most useful for you?

Re:In-browser RAW Processing: How We Did It on Thursday May 15, 2014 @08:17AM (#7748971)
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 know about more than one pixel per time to do correct demosaic process. Its not the same to create cool WebGL 3D effect and do JPG decompression for example.
Re:In-browser RAW Processing: How We Did It on Thursday May 15, 2014 @08:10AM (#7748950)
What Lightroom features is the most meaningful for you? What do you think?
Re:In-browser RAW Processing: How We Did It on Wednesday May 14, 2014 @03:49PM (#7745904)
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. =))
Re:In-browser RAW Processing: How We Did It on Wednesday May 14, 2014 @03:46PM (#7745883)
The problem is not only with WebGL. Unfortunately we don't support it yet, but working hard on it.
Re:In-browser RAW Processing: How We Did It on Wednesday May 14, 2014 @03:43PM (#7745858)
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.
Re:In-browser RAW Processing: How We Did It on Wednesday May 14, 2014 @03:39PM (#7745831)
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 JavaScript.
Re:In-browser RAW Processing: How We Did It on Wednesday May 14, 2014 @03:35PM (#7745802)
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/quality. Sure, we think about AHD, gradient and other algos, but we should deal with performance first.