yesterday christian and me did a test run of the multitouch ftir screen with the new security camera and the vvvv patch, which went very well… watch the video i shot with my mobile (bad quality)
Archive for the ‘notde’ Category
the second security camera arrived some days ago.
zoom lens, 0.02 lux sensitivity, 420 TVL resolution… if this isn’t it, then what is?
i guess since i ordered so much surveillance related stuff on ebay lately, i am now on some kind of blacklist. good thing i am not planning on going to the united states.
faster than i thought, i accomplished to adapt the old processing tracking sketch to the new input. the “blobs per second” method doesnt work anymore, but it feels fluent. no lag, so far. the communication between processing and vvvv via OSC seems to be stable, thanks to andreas’ quick help with the code.
I’ll get a new security camera soon, then there will be more testing on the prototype itself.
you can download the new patch for vvvv and processing sketch here.
The last days i was looking for another application for doing the computervision job, since eyesWeb’s “extract regions” block swaps the recognized blobs’ IDs when they change their position, which is problematic when one wants to track, or follow more than one moving object. Christian Iten and Daniel Luethi from the HGKZ told me that there was an Object for Max/MSP/Jitter called 2up.jit.centriods that can already track the spots. But Christian (Riekoff, not Iten) and me agreed to keep the multitouch screen as OpenSource as possible, so i ended up using the powerful freeware tool vvvv.
i have become a true fan in no time, since there are many advantages:
- its’s free
- it’s fast
- its interface, once understood, is the most minimal but effective i’ve ever seen.
- the “Contour” node (thats what Objects or Blocks are called in vvvv) gives us width, height, coordinates, form (sub-coordinates of border points) and orientation plus a Permanent ID of each blob.
right now i am rewriting (since everything is done by vvvv, this means throwing out wannabe-code) the OSCtracker in Processing. may i still call it “tracker”?
i ordered a new camera on ebay, and was quite surprised what arrived… its small!
i guess this camera is equal to this module: S/W-CCD-KAMERA 420TV-LINIEN-MINIATUROBJ (Conrad Electronic)
the problem is that this camera has such a wide angle that the whole screen is on the image in just a 70cm distance. good for tabletop-interfaces in the manner of sonicforms, bad for our setup… possible solutions:
- new lens for the camera
- whole new camera with zoom-lens
anyway, the performance increased significantly together with the BT878 capture board i ordered too…