oak-examples

Example projects we've done with OAK cameras

Explore on GitHub Read Hacker News discussions

2Distinct people

3Mentions

0Explicit recommenders

983GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Example projects we've done with OAK cameras

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year3 dated mentions

Observed mentions: 2020-07-08 14:41:12 UTC to 2024-04-02 12:49:43 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	1
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	0	0
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	2	2

What Hacker News says

3 sources

r2_pilot·Apr 2, 2024

I happen to use a few of their cameras, and they generally work as advertised (satisfied Kickstarter backer for OAK D and OAK D lite, probably going to buy the OAK D pro at some point). But, while I did indeed pay less than 250 for them individually, their current active depth offerings are $350(and while my oak d is fine for my lit, varied environment, I do often wish it was a little more accurate). I thought the Lite was also around $200 but it's actually $150 as you said. It's a pretty good little platform for the price. Be sure to check out the experimental repo too : https://github.com/luxonis/depthai-experiments/tree/master/

In Low Cost Robot Arm

r2_pilot·Mar 26, 2024

I use DepthAI cameras for a bunch of CV/ML stuff [https://shop.luxonis.com/] (the models run on-camera the most part) with a Jetson Nano Orin as the microcontroller. I used to use just the Jetson Nano but Nvidia is trying hard to get people on the new Orin, so I finally paid the Nvidia tax and developing for it became exciting again. But in your case, any raspberry pi would work since the detection events are not processed on the raspberry pi and the camera processor is relatively beefy. Check out their gen 2 examples for some of the models related to your task. Although looking at crowd counting example [https://github.com/luxonis/depthai-experiments] it may not run fast enough for your needs. But if you had the processing power freed up on the raspberry pi, possibly you could just display the 30fps frames and loosely sync the person bou

Read the rest

nding box detection once a second or so, which would look sorta normal for anyone watching. Anyway, sorry to ramble, I've just been working on those code samples a lot lately and I think this may be helpful for you or someone else in this problem space.

In Supervision: Reusable Computer Vision

Luxonis-Brandon·Jul 8, 2020

Thanks for the kind words. Brandon the founder here. :-) So although I could see how that quote could appear like that, the quote is not kissing the ring. We scoured the whole semiconductor start up scene to find a chip that could be used for this. There are only 2 chips (as I'm aware, as of this writing) that can be used in such a way: 1. Intel Movidius Myriad X 2. Inuitive NU4000AI. And the Inuitive, until super recently (i.e. 1.5 years after we have already built hardware off the Myriad X) was not ready to be used (had tape-out issues at the fab). So this made the Myriad X the only chip that (1) had the capabilities needed and (2) was actually available and in production. In terms of our open-source nature, the latter is what we've implemented - where we have closed source binaries running on the Myriad X - which then have a slew of

Read the rest

open-source counterparts on the host. Sorry if this came off disingenuous. Do you have advice on how to phrase it in a better way? https://github.com/luxonis/depthai-hardware - DepthAI hardware designs themselves. https://github.com/luxonis/depthai - Python Interface and Examples https://github.com/luxonis/depthai-api - C++ Core and C++ API https://github.com/luxonis/depthai-ml-training - Online AI/ML training leveraging Google Colab (so it’s free) https://github.com/luxonis/depthai-experiments - Experiments showing how to use DepthAI. The above includes open source hardware, core capabilities in C++ which can be cross-compiled for various hosts, and open-source training notebooks and use-case examples. So the goal of open-sourcing all that we can (including hardware) is to enable folks who have their own applications to leverage this, modify it, use it, etc. w/out having to even talk to us. We cannot open-source the code that runs on the Myriad X however, as then we wouldn't have a way to monetize, and would have to give up on the mission. (That, and we're also not allowed to.) Thoughts? Thanks, Brandon

In Luxonis wants to use computer vision to protect cyclists