Just in case I send you a new Segmentation Fault log.

Here I have already no method for Gemstate.

I send you the patches to have a better idea what I am trying to do.

trackerping.pd is the main patch, containing filecontrol.

after gemwin is rendered, open languagechoice.pd

there are 2 cameras placed in the main window sending to the pd ping1 and pd ping2 to languagechoice.

Basically the 2 cameras are creating one touch surface by placing them one above the wall facing down, the other one facing to the wall. When camera1 gets the wall hit tells the event to camera 2 which gets the position x y from pix_blob. Now when the 2 cameras send to each other info about the presence of an object, I get the segmentation fault.

On Thu, Aug 30, 2018 at 6:11 PM Csaba Láng <langcsaba@gmail.com> wrote:

I will try to rewrite my patches from scratch as the patch which was simple and contained 2 pix_video with both of my usb3 cameras using 227fps, but I added pix_gain, pix_background and pix_blob, looks good and smoothly works. check the attachment

My original idea was to send gemlist from one patch to an other via the send object, in this case closing the patch and opening a new one does not have to switch of pix_video, and does not have to restart the device as it does not work.

I hope i explained it clearly :)

On Thu, Aug 30, 2018 at 5:31 PM Csaba Láng <langcsaba@gmail.com> wrote:

it is much more stable with a simple patch, however can be crashed only clicking on a [device 1( message.

The crash in the log what I sent you happenes when I want to use it with pix_blob and changing the trashold in the pix_background object.

On Thu, Aug 30, 2018 at 5:12 PM IOhannes m zmoelnig <zmoelnig@iem.at> wrote:

On 2018-08-30 16:48, Csaba Láng wrote:
> here you are :)
>

cool.

does it also crash if you only use a very simplistic patch without any
image processing?
(basically just [gemwin], [gemhead], [pix_video]; if you want add
[pix_texture] + [square])


gmasdr
IOhannes