pylonsrc: How to handle corrupted frames

[joshdoe]

Issue originated on an issue over at gst-pylonsrc, where this plugin originated, but is still a problem with the current merged source.

Currently, any corrupted frames cause the source to error out, bringing down the pipeline.

I'm thinking the best way to handle this is to have a property that will continue grabbing frames even if one is corrupted, and maybe another property that determines whether to pass or drop the corrupted frame. Input appreciated.

[AB-Eskild]

I also noticed that getting error messages is quite common occurrence in the Pylon viewer. Adjusting frame-rate resolution etc. (bandwidth optimization) helps reducing the frequency of these occurrences.

I think perhaps the plugin should only fail when the frequency of error messages gets too high, and be configurable as a parameter.

[joshdoe]

I should say this should be fixed once #51 is merged, which should be within a day or so.

[thortom]

The changes have been merged, so this issue should be closed.