Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jpap
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
61.
▲
by
jpap
13y ago
Thanks! :-) To be honest, none of my formal training prepared me for what went into SnappyCam---only the "how" to go about learning to do so. I'm sure you could pick up a few tricks in the same way by working on a cool pet
62.
▲
by
jpap
13y ago
It's unclear to me, as there's a lot more going on when taking a photo than you might think. :) (I originally thought I could knock together a basic SnappyCam app on top of the JPEG codec within a week or two, it took months.) If
63.
▲
by
jpap
13y ago
ARM actually publishes reference code under the library name "OpenMAX" for their mobile processors. I've read ARM's source code and found they they too use the AAN algorithm for the DCT. (They provide a tonne of code fo
64.
▲
by
jpap
13y ago
Oh, it's a manual flash. Enabling that automatically is an interesting problem in itself: I'd have to estimate the light level based on the camera preview... or perhaps from the preview metadata. Will think about how that might be
65.
▲
by
jpap
13y ago
The possibilities are exciting for sure! :-)
66.
▲
by
jpap
13y ago
The Cinemagram guys started off down that path, an Instagram clone for animated GIF cinemagraphs, then quickly pivoted toward short videos to compete with Vine and Instagram on similar territory. I'm still not convinced. :-)
67.
▲
by
jpap
13y ago
1. It really depends on what you're after: are you looking for a video sequence that plays back, or an individual still? Video is better for the former, SnappyCam for the latter. 2. It's a lot of work, hinted at in another thread
68.
▲
by
jpap
13y ago
haha, no worries. In the app, you need to start with your finger near the thumbnail strip. (But can move it away for fine-grained scrubbing if you wish.) It's no surprise that the learned behavior is transferring to the web viewer.
69.
▲
by
jpap
13y ago
It shudders me to think that IE won over Chrome. :( I saw an issue also reported on here earlier today a few days ago. Sounds to me like a (new) canvas bug in Chrome. There are unfortunately several workarounds for browser bugs in the HTML
70.
▲
by
jpap
13y ago
@gosu, despite what Josh wrote, you can traverse your pointer across any part of the living photo online. :-) Love that you picked up on the expressions! It wasn't until I got the photos out of the app was I fascinated by the same thi
71.
▲
by
jpap
13y ago
Thanks! You can reduce the capture rate in the app settings, down to 1 photo per {1, 5, 10, 30, ... } seconds. Move the slider toward the turtle under "Camera Lens". jpap
72.
▲
by
jpap
13y ago
Fair comments, and much appreciated. I did all of the graphics design myself, in the app and on the web. :-) The infinite sign you see does require an explanation. I'll take your advice and think about how it can be done more simply.
73.
▲
by
jpap
13y ago
That's abs awesome to hear! Thanks for the wonderful complement. I played with price. Until now, most of my sales were word of mouth, and the $1.99 price hindered "growth". It's been an interesting game. Many people wh
74.
▲
by
jpap
13y ago
Oh that's awesome and a lot of fun! While SnappyCam has been the most difficult, complex, piece of software I've written since I started coding in my early teens, it's also been one of the most satisfying technically. I'
75.
▲
by
jpap
13y ago
haha, yes, if only it pays to be lazy. :) Sometimes doing "less work" means more up-front planning and thinking. Not a bad thing necessarily. Interesting on the native camera adjustment. SnappyCam will use the "low light b
76.
▲
by
jpap
13y ago
Good question! Several reasons: * Video codecs are much more complex. * Random access seek is a lot slower, unless you're using all I-frames. (That's now a codec option on iOS, but not when I started.) * "Studio swing"
77.
▲
by
jpap
13y ago
I don't know much about their device (maybe Nokia might send me one?!? hehe)... ... but they must have an awesome JPEG encoder. I'd assume 41Mpx stills would need to be compressed in no more than 1 second for a reasonable UX. Tha
78.
▲
by
jpap
13y ago
There are a lot of similarities actually. In SnappyCam, each photo is compressed to a separate JPEG file. There's no inter-frame compression, no motion vectors, etc. The same as mJPEG. The main differences are: * Each photo is stored
79.
▲
by
jpap
13y ago
Thanks mate---comments like yours make my day. :-) I'm not actually planning on creating a new niche social network. I think, given the vastness of some of the ones that've emerged of late, it would be more fruitful to leverage t
80.
▲
by
jpap
13y ago
I thought the app was pretty cool, just super slow to save out the JPEGs. That's one of the reasons I spent a lot of time to make sure SnappyCam could compress these images, thumbnails and Exif metadata included, at a ridiculous speed.
81.
▲
by
jpap
13y ago
Awesome! Drop me a line, would love to see how you go. :-)
82.
▲
by
jpap
13y ago
Thanks for the download! Let me know if you've got any feedback, I can be easily contacted through the app. :D I'd just like to add that in addition to handcrafted code, choosing the right algorithm and always trying to "do l
83.
▲
by
jpap
13y ago
That's really interesting. I wasn't aware of that. I'll have a look at it once social sharing is out the door. I did consider getting into other aspects of iPhoneography, like HDR, etc. The trouble with HDR in particular i
84.
▲
by
jpap
13y ago
You'd have to ask Ericsson. ;-) I certainly hope so!
85.
▲
by
jpap
13y ago
Thanks Raphael! :D It's been an awesome, surreal experience, very much reminiscent of 2007. Fun times, relived. :-)
86.
▲
by
jpap
13y ago
I saw this a couple of days ago. Are you using Chrome? It might be yet another Chrome canvas bug. :-( Try Safari and let me know if you can? :-)
87.
▲
by
jpap
13y ago
That's how it's done, where on dual core devices, a JPEG encode can be done in parallel to capture. Try it on an iPhone 5 with "infinite shutter" disabled and you will see the dropped frames in the filenames once you imp
88.
▲
by
jpap
13y ago
Yes, Nokia contributed the NEON code for the DCT in libjpeg-turbo. I haven't had a chance to do a side-by-side comparison as yet, but I suspect the SnappyCam encoder is faster for many reasons, including choice of algorithm and the way
89.
▲
by
jpap
13y ago
I can't say, as SnappyCam is my first foray into image signal processing. (Though DSP isn't new to me.) I'd guess that DSLRs use a combination of hardware acceleration on the "tricky" bits (like DCT) with firmware
90.
▲
by
jpap
13y ago
haha, cool. :-) To be honest, I don't often post here because I'm busy working, but am enjoying the discussion on a baby I've nursed for two years now. :-) Thanks for your post!
More ›