On 2018-09-05 14:10, Csaba Láng wrote:
Iohannes,
thanks for your advice. However I forgot to add that the 200fps I would like to use is not for displaying, but mostly to analyse fast objects in front of the camera.
i think i covered this use-case in length.
Theoretically, it should use the capacity frame rate of the USB3 cameras, should not it?
relate this to:
On Wed, Sep 5, 2018 at 1:56 PM IOhannes m zmoelnig zmoelnig@iem.at wrote:
most importantly, grabbing image data ([pix_image], [pix_video],...), storing image data ([pix_buffer...]) and manipulating image data ([pix_gain], [pix_kaleidoscope], [pix_multiblob],...) has nothing to do with openGL and is therefore unaffected by sync-to-vblank.
[...]
if (and only if) you have a [gemhead] that is only triggering non-openGL objects (e.g. *only* [pix_...]es), then you can manually trigger *this* gem-chain via a [metro], running at an arbitrary rate. (you should turn off the automatic-triggering of this [gemhead] by sending it a "0")
i think, the keyword here is "arbitrary".
gmfasdr IOhannes