Re: Re: Re: Re: Re: Re: Re: [libcvd-members] DV Camera Access (E. Rosten)

[Dewayne]

I have modified libdc1394 in the following way:

in dc1394/macosx/capture.c:

if ((buffer->pkts[i].status & 0x1F) != 0x11) {
            //dc1394_log_warning ("packet %d had error status %x",
            //        i, buffer->pkts[i].status);
            // corrupt = 1;
        }

So it no longer reports any corrupt packets. After compiling and
installing this library my application no longer reports any corrupt
packets or exits. It now just displays a single (sometimes broken up)
frame from the camera indefinately. It seems like it is still running
at some level but maybe having some sort of performance issue? I am
linking against libcvd_debug.dylib (in XCode). Is there some sort of
performance issue grabbing frames with the debug library? When I try to
link against the normal version of the library my program exits
immediately and xcode says 'Program received signal: "SIGABRT"' and the
following output is given:

libCVDTinkering(884) malloc: *** error for object 0x1000dda00: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug

What is going on with the normal version of libcvd vs the debug version?

Here is the code I am working with:

#include <cvd/videosource.h>
#include <cvd/videodisplay.h>
#include <cvd/gl_helpers.h>

using namespace CVD;
using namespace std;

int main()
{
    try {
        
        VideoBuffer<Rgb<byte> > * video_buffer = open_video_source<Rgb<byte> >("dc1394://0");
        VideoDisplay disp(video_buffer->size());
    
        while(1)
        {
            VideoFrame<Rgb<byte> > *frame = video_buffer->get_frame();
            glDrawPixels(*frame);
            video_buffer->put_frame(frame);            
        }
    }
    catch(Exceptions::All e)
    {
        cerr << "Error: " << e.what << endl;
    }
}

On Tue, Dec 15, 2009 at 9:02 AM, <address@hidden> wrote:

Send libcvd-members mailing list submissions to
       address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
       http://lists.nongnu.org/mailman/listinfo/libcvd-members
or, via email, send a message with subject or body 'help' to
       address@hidden

You can reach the person managing the list at
       address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of libcvd-members digest..."


Today's Topics:

  1. Re: Re: Re: Re: Re: Re: Re: [libcvd-members] DV Camera Access
     (E. Rosten)


----------------------------------------------------------------------

Message: 1
Date: Tue, 15 Dec 2009 10:11:34 +0000 (GMT)
From: "E. Rosten" <address@hidden>
Subject: Re: Re: Re: Re: Re: Re: Re: [libcvd-members] DV Camera Access
To: address@hidden
Cc: address@hidden
Message-ID:
       <address@hidden>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Mon, 14 Dec 2009, address@hidden wrote:

> Yeah, this issue is confusing. I see a posting about it in an earlier
> version of libdc1394 relating specifically to the Fire-i camera. It's
> strange, When I run the application it gives me the warning 3 times:
>
> libdc1394 warning: packet 479 had error status 0
> libdc1394 warning: packet 479 had error status 0
> libdc1394 warning: packet 479 had error status 0

As far as I can tell, this is a problem with libdc1394 on the mac:

http://article.gmane.org/gmane.comp.multimedia.libdc1394.devel/


> It does capture a single frame from the camera and display it. It gives
> me 3 warnings even if I run the code with no loop as follows:

As far as I know this is harmless, as long as video seems to be captured
successfully.

-Ed





------------------------------

_______________________________________________
libcvd-members mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/libcvd-members


End of libcvd-members Digest, Vol 44, Issue 6
*********************************************