Do not require IAMStreamConfig

[GoogleCodeExporter]

I've been working with PointGrey cameras recently, but right now you can't use 
them with AForge because their DirectShow filters don't implement 
IAMStreamConfig.

I was wondering if you could modify AForge in future releases so that it 
doesn't require this interface to be supported, this would then mean that we 
can use AForge with PointGrey cameras and so widen AForge's userbase (PointGrey 
are one of the largest scientific/research camera MFGs right now, so it makes 
good sense).

I had a discussion with their support department and they're going to get their 
developers on the case and hopefully implement it in the next revision (which 
won't be for at least a few months, if not another year), so anything you can 
get going I'd appreciate.

Original issue reported on code.google.com by w3...@w3bbo.com on 20 Aug 2010 at 1:31

Attachments:

• Untitled.png

[GoogleCodeExporter]

It may be a bit hard to fix the issue, since I don't have any PointGrey cameras 
available to me for now. So I am a bit blind fixing it ...

Is this message box displayed by your code? Or is it displayed automatically, 
when you try starting video source configured to use PointGrey camera.

Original comment by andrew.k...@gmail.com on 20 Aug 2010 at 1:52

• Added labels: Project-Video

[GoogleCodeExporter]

My project has two forms: DeviceSelectForm and MainForm. The DeviceSelectForm 
works fine and proceeds on to the MainForm.

MainForm has a method "Setup" which is called from the Form.Load event handler 
that sets the "VideoSourceError" and "NewFrame" event handlers for the 
IVideoSource.

There's a button "Start Source" that when clicked calls videoSource.Start() and 
that's when the message appears.

The messagebox is displayed from the videoSource.VideoSourceError event 
handler. I'll post stack traces in a follow-up posting.

Original comment by w3...@w3bbo.com on 20 Aug 2010 at 2:33