ravazquez

Suggested fix only applies to 3-channel images, would not cover many cases still. I will look into this.

Wow, thanks for this! I will have a look and get back to you but in general, it looks good. For now though, could you please stick with the naming...

Hello again @dani217s , Apologies for the delayed response, as you can imagine the recent release had people busy on other things for a bit. First of all, thanks for...

Mat and MatExpr are something that has been discussed a few times, sadly some of the type inference/equivalence used by OpenCVSharp is not working in VL (things like Mat to...

@mwjb I tried the same here using VL.OpenCV 1.2.0 and beta 41-7 preview:  No issues, I can switch back and forth between two cameras and I have no red...

I have been thinking this thru, however, having two differently sized images in sequential frames _is_ an invalid scenario to calculate optical flow, and the user probably wants to know...

Just an update on this so it's logged somewhere: - Initial tests were made using UMat a year or two back, showing varied results. In some operations and filters, the...

Hello @mhusinsky, Thanks for this! I finally had the time to give it a closer look and it is all making sense so far, tests included. My only two concerns...

Hey @YanYas , is this still the case? I am finding it hard to get a hold of a 32FC1 image with actual meaningful data.

Hi @circuitb and @wirmachenbunt , VL.OpenCV 1.2.0 has a new set of VideoIn nodes which do not use an enum to select the video device, but rather a direct index....