Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

opencv.org

Post reply on HN
Print view View original

131–140 of 160 posts

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

#131

Post by nextaccountic »

ranit wrote: post #111
Joel_Mckay wrote: post #70

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?

Software patents aren't a thing in most of the world

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

#132

Post by jrk »

Joel_Mckay wrote: post #101
Sesse__ wrote: post #85

Earlier quoted context omitted.

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

It's not that you need to turn on some extra library backends and rebuild, it's that the abstractions themselves are fundamentally at odds with hitting peak performance on many things so you have to rewrite your code.

Individual image processing operations are often very low arithmetic intensity. If you don't combine them into much larger subroutines—which are necessarily less generic and orthogonal—you spend all your time waiting on memory between every little op.

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

#133

Post by charcircuit »

ceejayoz wrote: post #129
charcircuit wrote: post #125

Earlier quoted context omitted.

The GPUs were doing video transcoding instead of GenAI.

You can run OpenCV on a GPU-less Raspberry Pi or other IoT device just fine. And most IoT devices aren't doing video transcoding at all. You're making some very odd assertions in this thread.

>And most IoT devices aren't doing video transcoding at all.

The data gets streamed to the cloud where servers with GPUs transcode it. I'm pointing out that IoT devices historically have reached out to servers with GPUs even before GenAI.

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

#135

Post by akssri »

Joel_Mckay wrote: post #70
plasticeagle wrote: post #37

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…

Yup, it's basically the ROS of computer-vision.

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

#136

Post by TZubiri »

sorenjan wrote: post #40
TZubiri wrote: post #31

Earlier quoted context omitted.

That's not helpful my brother. If you have details share them, if not, don't pretend you are more illuminated than me. Is the image(text) function reversible? Or are they brute force searching a nearest neighbor like word2vec/hash brute forcing.

Google recently released their paper "Image Generators are Generalist Vision Learners" about exactly this. They fine tuned Nano Banana pro into what they call Vision Banana which can do segmentation etc. https://arxiv.org/abs/2604.20329

very interesting, it seems that they use image(image,text) functions to process/filter images, effectively generating arbitrary bitmap(image), where bitmap is of the same dimension as image.

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

#138

Post by smt88 »

jampekka wrote: post #86
smt88 wrote: post #79

Earlier quoted context omitted.

The problem is that we don’t know if a human fact-checked it before release or if we’re the first humans reading it closely.

We don't really know that about human written text either.

Yes we do because a human literally had to write it. That’s at least one human pass and fact-check.

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

#140

Post by fzysingularity »

plasticeagle wrote: post #37

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.

That’s a pretty large binary for simply loading images.

In all honesty, opencv has stood the test of time and I’m certain newer LLMs will likely not attempt to rewrite it from scratch.

P.S. I’ve been a user since the IplImage days, circa 2007, and I’d still consider using it over most CV libraries today.

Post reply on HN