Live data from Hacker News

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

opencv.org

101–110 of 160 posts

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

#101
post #85

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…

Also, performance is generally pretty low; I've been on projects where we rewrote OpenCV code into more-or-less obvious hand-rolled code and won 5x perf. The abstractions are generally a bit too thick and oriented around single pixels (which also makes the API a bit too verbose for my taste).

Machine vision has always been resource intensive... and if you are doing trained ML projects the hardware choices are actually very limited.

To enable Intel TBB, CUDA, and CPU specific compiler optimizations... one will almost certainly need to re-build the library, and customize your application build.

Some tasks degrade in performance on a GPU, and others are 740 times faster... ymmv. =3

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

#103

AI written release post and it shows...

Indeed. Well written, clear, informative and to the point.

As of now, any human effort is still ~= quality. Human-written article signals to me that a certain amount of time was spent on it, which is a proxy for quality. This goes for both text and diagrams.

If someone slapped together an article from an LLM and a few internal documents, that tells me exactly how much they cared about it.

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

#104

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…

Done a few projects with OpenCV myself, and your list of issues reads as if you throw OpenCV and opencv_contrib into the same bucket. Which you shouldnt. And maybe your assessment is outdated here and there and it is time to look again. - OpenCV is Apache license. Yes, it used to be more complicated. - The only patented algorithm I am aware of, SIFT, used to be part of opencv_contrib. And the README in opencv_contrib…

My point was the release numbers are meaningless, as there is always something subtly broken even in the packaged versions. One can't just use the library beyond basic functionality without becoming involved in the code base.

Indeed, if your library dependency constellation works, some will static link to stabilize/freeze their project for more than a few months.

It wasn't that v3 was particularly good, but rather v4 was a mess. I predict v5 inherited that mess, and improved it... lol =3

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

#105
post #77

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…

Agree with this too. OpenCV is functionality great but its constituent parts are written by many different people who all kind of do things a little differently and it shows. But I can’t really complain because it’s open source and added to by contributors.

One can... and should report when stuff is broken, or the project becomes worthless to all but one persons passing interest. =3

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

#106

does this mean im actually able to try object detection in opencv now? i mean i know basic image processing techniques, and i know "in theory" how ML works but ive never really seen a case where i can just say "heres an image now detect all the apples". theres always 1. find a model that has the knowledge, 2. hook it up to an inference engine, 3. do something useful. i always get stuck at 1.

YOLO has basically solved that for my use cases for a couple years now. If you want labels that are not in the pretrained labels it's also easy to fine-tune, provided you're willing to label 200 or so images If you need something less restricted to existing labels (say wanting all the red apples, or all cardboard signs) SAM3 is great, as the sibling comment says

How do you handle object disambiguation with YOLO? All the examples I've played with have the problem where if two "cars" get too close to each other then the tracking IDs keep switching between them, meaning we'd need an additional kinetic model for disambiguation.

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

#110
post #24

Earlier quoted context omitted.

The release post is AI-written with little human oversight and it shows.

I had to stop reading after: "This is not just another incremental release. OpenCV 5 is a major step forward." If a human can't be bothered to write a piece, I can't be bothered to read it.

I felt that this was an indication that OpenCV had finally discovered SemVer.
Post reply on HN