Live data from Hacker News

OpenCV 5 Is Here: The Biggest Leap in Years for Computer Vision

opencv.org

111–120 of 160 posts

Re: OpenCV 5 Is Here: The Biggest Leap in Years for Computer Vision

#111

The thing I love about OpenCV is that it remains hands down the best library for simply loading images and video. I've never even used any of its fancy computer vision features, but if I need to load a video file and look at the pixels - which I did need to do recently for an art project - OpenCV does it in about four lines of code.

Done a few projects with OpenCV over the years, and I agree it can be fun. However, it has a few issues: 1. Patented algorithms that are effectively impossible to license in a commercial setting. 2. Permuted API that change how identically named functions behave over versions. 3. Hardware CUDA version coupling deprecating support every major release. 4. Inconsistent and contradictory documentation in the constant sub…

If this is a fact:

> 1. Patented algorithms that are effectively impossible to license in a commercial setting.

then does anyone know how "OpenCV has been the foundation of countless production systems" is possible, as the OP article claims?

Re: OpenCV 5 Is Here: The Biggest Leap in Years for Computer Vision

#112

The thing I love about OpenCV is that it remains hands down the best library for simply loading images and video. I've never even used any of its fancy computer vision features, but if I need to load a video file and look at the pixels - which I did need to do recently for an art project - OpenCV does it in about four lines of code.

What are you looking for in the pixels?

truth

Re: OpenCV 5 Is Here: The Biggest Leap in Years for Computer Vision

#113

The thing I love about OpenCV is that it remains hands down the best library for simply loading images and video. I've never even used any of its fancy computer vision features, but if I need to load a video file and look at the pixels - which I did need to do recently for an art project - OpenCV does it in about four lines of code.

What are you looking for in the pixels?

To see if it’s a ‘shop.

Re: OpenCV 5 Is Here: The Biggest Leap in Years for Computer Vision

#114
post #111

Earlier quoted context omitted.

Done a few projects with OpenCV over the years, and I agree it can be fun. However, it has a few issues: 1. Patented algorithms that are effectively impossible to license in a commercial setting. 2. Permuted API that change how identically named functions behave over versions. 3. Hardware CUDA version coupling deprecating support every major release. 4. Inconsistent and contradictory documentation in the constant sub…

If this is a fact: > 1. Patented algorithms that are effectively impossible to license in a commercial setting. then does anyone know how "OpenCV has been the foundation of countless production systems" is possible, as the OP article claims?

Well I've deployed OpenCV based pipelines in academic contexts for site surveys and photogrammetry.

Re: OpenCV 5 Is Here: The Biggest Leap in Years for Computer Vision

#115
post #10

> One practical detail is worth knowing. The new engine is CPU-only at the moment, so if you select a non-CPU backend and target (for example CUDA or OpenVINO through setPreferableBackend and setPreferableTarget), you will want the classic engine. So there's room for even better performance!

No one uses ONNXRuntime (nor the new engine in OpenCV 5) in production. For anything performance-sensitive, one would run models under TensorRT, as an example.

OpenTrack uses it for its AI headtracking, which works extremely well.

Re: OpenCV 5 Is Here: The Biggest Leap in Years for Computer Vision

#117
post #63
post #58

Earlier quoted context omitted.

The diagrams definitely look like LLM output as well

The diagrams were generated with Nano Banana Pro (most probably, or alternatively with ChatGPT Image 2), if you look closely in high contrast areas you'll see artifacts in the background that give it away. I personally don't mind AI generated content when it's properly reviewed, but unfortunately more often than not the author just glances at the result and decides it's good enough. Example: https://opencv.org/wp-con…

[deleted]

Re: OpenCV 5 Is Here: The Biggest Leap in Years for Computer Vision

#118

How can I learn the practical side of computer vision in 2026? I'm not interested in understanding papers or the math behind it, but rather in how to put a system into production, whether it's object detection, running 20 cameras in parallel on a single computer, like sizing hardware for a specific task, and so on. Any tips?

By doing it. Decide on a small project, like tracking your cat, detecting food items in your fridge, then take it step by step. Then do a slightly more ambitious project. Start with something very simple. It also heavily depends on what you already know regarding programming, image processing etc.

Just start cooking , python is easy and the bindings are not that hard

Re: OpenCV 5 Is Here: The Biggest Leap in Years for Computer Vision

#119
post #114
post #111

Earlier quoted context omitted.

If this is a fact: > 1. Patented algorithms that are effectively impossible to license in a commercial setting. then does anyone know how "OpenCV has been the foundation of countless production systems" is possible, as the OP article claims?

Well I've deployed OpenCV based pipelines in academic contexts for site surveys and photogrammetry.

There is a CLI photogrammetry OSS project with rather litigious faculty members behind the code. However, at least that group was upfront about what was expected of the library users, and didn't do something dodgy like quietly merge it into another community library like OpenCV.

I discovered that while porting it to a Pi ARM platform years ago (yes it was slow... lol.) Forgot when the IP becomes public domain, but you might want to check that out. If I recall it was unrelated to the COLMAP project design. =3

Re: OpenCV 5 Is Here: The Biggest Leap in Years for Computer Vision

#120
post #111

Earlier quoted context omitted.

Done a few projects with OpenCV over the years, and I agree it can be fun. However, it has a few issues: 1. Patented algorithms that are effectively impossible to license in a commercial setting. 2. Permuted API that change how identically named functions behave over versions. 3. Hardware CUDA version coupling deprecating support every major release. 4. Inconsistent and contradictory documentation in the constant sub…

If this is a fact: > 1. Patented algorithms that are effectively impossible to license in a commercial setting. then does anyone know how "OpenCV has been the foundation of countless production systems" is possible, as the OP article claims?

One can legally use/static-link OpenCV in most commercial projects, and there were only a few legal landmines people still try to document when possible.

However, until each code area turns 17/21 no one knows for sure. It just looks normal at first, and $12k cheaper than MatLab server host licenses. =3

Post reply on HN