rwinn
rwinn on Hacker News
Posted by
rwinn on Wednesday May 24, 2017 @05:25AM
from the show-hn dept.
Super cool!
btw, you have a typo in the learn more section, the readme link ends in .mg
Hoping to get some help implementing support for other cameras, this was too much of a niche app for it to make sense for me to do it solo.
I'm planning to break the PTP/IP framework out to a separate module so it can be reused by other apps as well.
Posted by
rwinn on Thursday May 18, 2017 @04:49PM
from the show-hn dept.
Posted by
rwinn on Tuesday May 16, 2017 @11:04AM
from the show-hn dept.
Impressive results! Even where the original is distorted and mixed with other videos it's detected. I take it you use a different technique than spotter?
Posted by
rwinn on Wednesday May 10, 2017 @10:15AM
from the dream.almost.digital dept.
Jumped through the hoops and signed up to submit my own video, still "Queued to analyze..." after 1h.
Posted by
rwinn on Tuesday May 09, 2017 @11:17PM
from the show-hn dept.
Posted by
rwinn on Sunday April 30, 2017 @08:07PM
from the show-hn dept.
Posted by
rwinn on Saturday April 29, 2017 @10:49AM
from the show-hn dept.
This is purely anecdotal, but I live in Florence and know a couple of people from the "old-money" families and they are not rich by todays standard. They make a modest living renting out and managing the properties handed down through the generations and have to be frugal to make it work.
Also, you should be very sceptical of any study made using Italian tax records as a data source :D
First thing I install on any new system, couldn't recommend it more!
And the ability to do per-application captures and open them in wireshark is excellent for debugging.
I'm a bit confused, this is a simple git add or some sort of integration with git lfs they released last year?
https://git-lfs.github.com
Found the problem and pushed a fix, should me much smoother now.
It was Firefox's SVGPathElement::getPointAtLength implementation that was slow, working around it by caching all the calls to it.
Btw, if anyone is wondering why the workers run so slow when in a background tab, it is because most browsers throttle setTimeout's to run max once a second when the browser window looses focus. (web workers does not have this problem but for the demo i figured it would be fun to watch the workers do their thing)
Yep, I can reproduce it on OS X with FF 42.0 as well. Going to see if i can find what's causing the low framerate.
That sucks. I'm using d3.js to animate svg elements, runs smoothly on my machine, what browser/os are you on?
Not exactly, it is a task queue that allows workers to be run in the browser.
If you could break your problem up in to lots of small isolated tasks it could be used like that
Posted by
rwinn on Tuesday December 08, 2015 @07:27AM
from the show-hn dept.
Sorry for the downvote, I meant to hit up and I can't seem to change it
Wow! Higher compression than any other format, full transparency support, progressive/partial loading AND animations?! I can't wait for this to get widespread adoption!
Github repo here btw: https://github.com/jonsneyers/FLIF
It's not imposed.
"But even though there is a structure, you are very welcome to ignore it, keep working while the others take breaks, come and go whenever you want. The structure is there to help us, not to limit us."