I've been working with your software for about a month, and its working really well.  I'll be publishing some interfaces in the next week or so for everyone to check out. 

I have found a bug on my system, though, and I'm wondering if its just me, or if others are experiencing the same thing.

I noticed early in working that certain elements would stop working after a while (i.e. a fader or button that responded to TUIO would suddenly stop working after a while of use).  I realized that what is happening is that that add messages that are stored inside the #1-mmf-polytouch 1 coll are not being removed successfully sometimes, even though Max is receiving the remove message from the TUIO client.  I'm using W2TIO on Windows7 with a Dell Latitude. 

I've written a hack to periodically poll the colls everytime a touch is added to see if there are duplicates inside the coll and clear it if one exists (which is why they no longer function…. for each touch, there will be numerous first touches on a broken element, e.g.:  element name, 10 10 10 10 10 10) and this works ok, but of course sometimes there is a touch that is dropped before the clear happens.  Also, I'm sure this constant polling is creating a performance hit for my interfaces. 

I haven't completely had time to unravel your system for MMF enough to see where the actual problem is.  I am operating with overdrive turned off, as the reaction time with overdrive on is FAR greater.  I'm wondering if this is perhaps the reason why this is happening.  Anyway, if someone could give me some insight, that would be great. 

Again, let me congratulate Mathieu on this astounding framework, I can't believe how well it functions in so many regards.  I have created interfaces emulating the novation Remote SL25, Nocturn, Mackie Control Universal and XT, and Monome 256.  My demo of Max on Windows will expire in 4 days, so my development will be halting for a little while.  I'll publish my patches when I get a chance to compile them in a more encapsulated manner.  Cheers

amounra

–Maybe some tuio messages are “corrupt”, or missing ?

As far as I can tell, all the data that should be there IS THERE.  Its very strange.  Maybe my screen calibration is messing with something (I just thought of this, I'll have to check it out).

–wich version of max are you using ? mac / win ?

most current max on win7.

–I'm always working with overdrive ON in max (Scheduller in overdrive, but NOT in audio interupt). I've never noticed any latency difference between overdrive on & off ; and I don't think this could cause message lost.. but.. who knows… :-s

yeah, I've not noticed it while running on a Mac, but there is a definite difference in Win7 between overdrive on (higher latency…..go figure?) and overdrive off.  It seems like messages are getting lost completely, or reordered perhaps.  Unfortunately I'm not going to have time to figure this out before my demo expires, so I'll have to just fly the way it is.  Is anyone else using this configuration? (Win7, Dell Latitude XT, W2TUIO, MaxMSP current version)

–Maybe you could try to increase “poll throttle” and “queue throttle” in max preferences / Scheduler.

I'll try this tonight or tomorrow if I have time and get back to you with the results.

–by the way… how is MMF going on a multitouch Dell Latitude ? I would love to see a demo video .

It's going exceedingly well, except for the aforementioned bug.  I've been surprised, I wasn't sure if it would be usable when I invested in the laptop.  The W2TUIO app does bug out every once in a while and has to be restarted, or sometimes I need to logout/login (the cursor sometimes disappears and doesn't come back until you logout or restart the computer).  Also, there is a lot of beta involved in this setup.  WinBeta7, as well as Beta NTRIG drivers for the screens multitouch capabilities.  The NTRIG drivers disable touch capability when using Vista, DONT support pen functionality at all in Win7 or Vista, and at times, completely stop working until an OS restart happens (the last bit, though, doesn't usually happen unless the laptop has been on for at least several hours, and usually after 8-12 hours).

I have one portion of one interface to finish, and then some code optimization and encapsulation to complete, and I'll be ready to start sharing some of this stuff.  Hopefully someday soon I'll be able to start making music again instead of coding control surfaces .  I'm working on opening a theatre this week, but hopefully next week I'll have some time to sit down and document and video some of this stuff.

Cheers

ok, let's try to debug this thing…

please download this debug patch.
(copy & paste it in your main mmf patch, and connect it to « p tuio »)
(+ double click on loadmess objects if needed to connect the cellblocks to the colls) 

amounra : you said in your fisrt post   »for each touch, there will be numerous first touches on a broken element, e.g.:  element name, 10 10 10 10 10 10″
that would mean that several cursors with the same id have been mapped to the same object. strange :-s 

as I said, I don't have this problem here, so it's not easy for me to find a solution…

please make sure you don't have several objects with the same name in your interfaces.

one more thing you could test :
replace the content of your « p tuio » patcher with this patch that uses the « real » tuioclient object. (download the lattest version here : http://www.tuio.org/?software (version 1.4rc1) and let's see if it make a diference with the abstraction version..

sorry guys, I'm out of time for a couple of days, and my demo of Max expires today….I'm going to try to compile this stuff to an app and then then do a fresh OS install on the Win7, but I won't have time to do anything else until next week probably.  I'll give this a go in a couple of days when I have more time.  Grand Opening of the Theatre last night, things went well, I should have more time very soon I think.

Allright….don't know if anyone else is using my setup, but here's the update….

Apparently Matrixctrl is kicking my Win7/Intel 1.2's butt.  It is using a lot of resources anytime this part of my patch is working.  I've made some modifications to my environment, and have a dependably working patch right now (mostly, lowering all values within MaxMSP's scheduler preferences to 1, e.g. event interval, scheduler interval, scheduler slop, and raising poll throttle and que throttle quite a bit (100 and 200 respectively, I think).  This has dropped latency to an acceptable degree, and the problems with the coll I began this thread about have  been reduced considerably (I would say the issues are only occurring about 10 – 20% as often, and the patch I created takes care of these issues well enough).

I am testing these patches currently, and hopefully will have videos and some public domain shares of my patches  this week.  Cheers

BUMP!

Every Time I use MMF, with TUIO through W2TUIO, I have gui objects that become unresponsive to TUIO. How do I debug this? I'm having trouble understanding the above conversation. I need clear indications.

@Amounra, did you ever fix this problem?

all of you who have this problem are using windows 7 + W2TUIO, right ?