Seb's profile - activity

There's not much you can do then. Convulution is time-consuming.

You still need to read the entire binary file. But you can alter the part where OpenCV build a Mat object. You can just read your ROI from memory and create a smaller Mat object.

Awesome, that is working!

First thing first, did you break into your code and are you 100% sure that you program freeze at the cvDestroyWindow?

Usually I do

unsigned char *input = (unsigned char*)(oOut.data);
for (int i = 0; i < oOut.rows; i++)
{
  for (int j = 0; j < oOut.cols; j++)
  {    
    input[oOut.step[0]*i + oOut.step[1]*j] = 255;
  }
}

This is with a typical 8UC1 mat. Now, I want to store values that can range from -1500 to 1500. So I'm using a CV_32F mat. But I can't figure out how to store values inside. I always end up with corruption with incoherent values.

Can someone help me?

Edit, I mean 32F, not 32S, my mistake

Thanks Seb

Thanks! I really appreciate your work

Wow, I like how flexible you guys are. That's awesome.

Hi

I'm using the org.opencv.android.NativeCameraView with layout set at fill_parent

In my Java, I have set this

mOpenCvCameraView.setMaxFrameSize(320, 240);

Actually, when I'm running my app, it shows the camera images but at 320x240.

I want to "stretch" it to go full screen without changing the camera resolution.

OpenCV 2.4.4-beta

Thanks Seb