Reactivision + Fiducial Markers

Triglavius's picture

Hi all! I´ve been developing a reacTIVision based application, it works with several different fiducial markers. Every marker has different behavior. The problem i have is "simple" but couldn´t solve it myself. When one fiducial marker is detected, actions and behaviors are just OK. When second fiducial is detected, it still is OK. But, when one of fiducials is taken out, it´s behavior continues operating (just like it was never taken out), unless both markers are taken out.

Did anyone had this issue before? How can this be solved?

Thanks in advance.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

shaker08's picture
Re: Reactivision + Fiducial Markers

maybe is for the kind midi trigger that you are using ... maybe your configuration is something like if i show the fiducial = "note on" and if i show the fiducial again = "note off" .... probably you can reconfigure it in the xml of reactivision .... i hope this help you 08.

Triglavius's picture
Re: Reactivision + Fiducial Markers

Thanks Shaker, but actually i´m not using any kind of "midi element..." This project is all visual, not audio.

gtoledo3's picture
Re: Reactivision + Fiducial Markers

Are you talking about when using the reacTIVision code in a cocoa app, that you're having this problem? Or are you talking about receiving the signals using TUIO into QC and that not working correctly?

Does the stock simulator app have the same problem?

Triglavius's picture
Re: Reactivision + Fiducial Markers

I run ReacTIVision.app; Then i use the TUIO client in QC.

Edit: Example composition

PreviewAttachmentSize
2Fiducials.qtz23.13 KB

dust's picture
Re: Reactivision + Fiducial Markers

i don't have a reactivision set up right now but it looks like your issue is that you are using the c_id as your index value. the component id is complicated and depending on what protocol 1 or 2 your tuio client is using things do change. the qc plugin i think is protocol 1.1 but im not sure. either way you can look at the specifications on tuio.org when dealing with 1.1 protocol the component id seems to act like the session id. i think this is so you can differentiate between two of the same objects. and the id is unique to the life time of the session and the frame sequence. so when if you put up marker 1 before 2 then the c_id for marker 1 is 0 but if you put up marker 2 before marker 1 then its c_id 0. it gets pretty confusing but im sure something like that is happening. try the tuio distributer plugin it may help.

http://kineme.net/Discussion/DevelopingCompositions/Tuioclientreactivisi...