[libavg-devel] OpenGL Error in OGLSurface::createBitmap() / branch
libavg-v4l2
Ulrich von Zadow
uzadow at libavg.de
Wed Jun 20 12:00:52 CEST 2007
Hi,
it's kind of hard to determine what's going on from here, but I'll try
to explain some things.
OXullo Intersecans schrieb:
[...]
> [07-06-20 01:44:31.945] CONFIG: Using pixel buffer objects.
> [07-06-20 01:44:31.945] ERROR: OpenGL error in OGLSurface::createBitmap:
> glBufferData(): invalid value (#1281)
glBufferData allocates gl memory for the bitmap that the camera node
will use. The memory allocated can be accessed directly by the graphics
card. In OGLSurface::lockBmp(), that memory is mapped into the process
memory space as well and a pointer to it is returned. (Actually, what
exactly happens depends a lot on the graphics card involved, whether
it's AGP or PCI-X or motherboard, etc., but you get the idea.)
Have you checked the parameters for glBufferData? Something like this:
cerr << Size << ", " Bitmap::getPixelFormatString(pf) << ", " << i <<
endl;
Are Size and pf correct? If Size isn't correct, what is
pCamera->getSize() returning?
> VideoBase::open() (which spawns V4LCamera::open())
> addDirtyRect(getVisibleRect())
>
> At this point it's quite hard to understand what happens: dirty regions
> are polished by event driven doFrame() ?
Actually, dirty regions are only used when doing software rendering
using DirectFB (not OpenGL), and that's broken at the moment. So you can
safely ignore them.
But anyway, addDirtyRect() is never reached, right?
> What is the bitmap taken?
> Camera interface is not queried at all (via getImage())
Sorry, I don't understand the question :-(.
Good luck,
Uli
More information about the libavg-devel
mailing list