Project description:
Name: Touch Tracer
Version: 0.2
Purpose: To display recognized blob’s and for debugging purpose

Changelist:
- Added tracelines
- Added funky blob colours
- Made the source linux compatible
- General code cleanup

Touch Tracer v0.2 video

> Touch Tracer v0.2 example video

Install instructions:
(windows)
1. Put all files (touch_tracer.exe and *.bat files) in the same dir as touchlib.dll
2. Either run the bat files or edit them.
touch_tracer.exe requires 4 arguments: width height bitdepth refreshrate
example: touch_tracer.exe 1024 768 32 60

(linux)
1. I guess linux users are smart enough to compile it with the included
Makefile. (Change touchlib home dir)
2. Don’t forget to run the applications with the 4 arguments for
display.

General note, as the readme.txt states, this application needs libraries of visual studio 2005.
If you don’t have those, you will be prompt with an error message.

When running the following shortcuts are available:
ESC = exit
g = enable/disable grid
s = enable/disable antialias for lines (nicer)

Todo:
1. Nothing? Suggestions? PM me.

Download:
I’ve included a windows binary and the source code of touch tracer for linux users.
By using the included Makefile you should be able to get it up running in notime.

Touch Tracer v0.2
Touch Tracer v0.2 source code

Optional downloads
msvcr80.dll and msvcp80.rar - Required if no vs2k5 runtime dlls are installed
Visual Studio 2005 sp1 redist. package - Entire package if the one above fails

very nice work!

edit: when you send the framerate to the exe, does it force the webcam to run at that rate?

Falcon that’s beautiful! Nice work. I also ask the same question as above (how you achieved the framerate specification). But this is nice! Thanks for this.

Looks great falcon, yeah it seems you have some light leaking, thus triggering a touch event, but still looks damn smooth.

cmoore - 13 May 2007 04:24 AM

Looks great falcon, yeah it seems you have some light leaking, thus triggering a touch event, but still looks damn smooth.

Yea you’re right cmoore. I’m not sure how much I need to extend the baffles though.

quote from my blog:

In the video below you will notice a few glitches. These are not caused by touch tracer (really :D)!. My FTIR panel seems to ‘leak’ light on the edges. After creating some demo movies I noticed that not only my finger tips where reflecting the light. Also other parts seems to reflect (just enough) IR light to fool touchlib. It’s even possible to create blobs when you hover your hand near the edges. A possible solution is to extend the baffles just a bit.

About the framerate:
I set my camera to 320x240 @ 60 fps, however I don’t know how to check if its really running at 60fps. This is prob. opencv/touchlib related (and it might run in a different thread).

The fps which is displayed in the application is the fps of touch tracer itself.

nice video, looks smooth

Nice work Falcon, and thank you for the fgreat testing app. 

Since i’m still testing with a very small screen and very old camera, i always need to set up touchlib to do a propper background supression, ajust the levels and stuff.  The problem is that since your app starts right away, i do have a lot of background light noise which i don’t get surpress.  In the ConfigApp i can immediatly do this by pressing the ‘b’-key. But this doesnt seemt o happen here.  So when touchTracer shows up, i do get a lot of blobs (200 something) and they don’t clear like a fingerd blob would do.  Is there any way for me to clear the old blobs that are no longer there.

The other thing i could do is set up my screen definatly, without having to break it appart every time and setting up every time when i want to do some testing.

Thank you again.  The app is great!!

sidje - 15 May 2007 06:10 AM

Nice work Falcon, and thank you for the fgreat testing app. 

Since i’m still testing with a very small screen and very old camera, i always need to set up touchlib to do a propper background supression, ajust the levels and stuff.  The problem is that since your app starts right away, i do have a lot of background light noise which i don’t get surpress.  In the ConfigApp i can immediatly do this by pressing the ‘b’-key. But this doesnt seemt o happen here.  So when touchTracer shows up, i do get a lot of blobs (200 something) and they don’t clear like a fingerd blob would do.  Is there any way for me to clear the old blobs that are no longer there.

The other thing i could do is set up my screen definatly, without having to break it appart every time and setting up every time when i want to do some testing.

Thank you again.  The app is great!!

There are a few options you could considerer here.
(1)
You could use a different application like smoke or the config tool to calibrate your system (be sure to save the config.xml)

(2)
Another option is ignore the zillion blobs the first time you start Touch Tracer, press alt-tab and change all the pre-processing windows until you have some satisfying result. Now switch back to touch tracer and press q. It should quit touch tracer and save the config.xml. If you run touch tracer again it should give the desired results.

About the ‘b’ key, that’s something whitenoise added to his applications. If you compiled/checked the source code you will see that the ‘b’ key has been commented at this moment due some unknown reason I’m not able to clear the

I must be having outdated precompiled touchlibbins (i donwloaded the bins, not the source code) and the ‘b’-key still works for me.  Restarting TTracer didn’t do the trick. Allthough i just ran the callibration app, but after starting callibrating, nothing happend anymore.  Yes, red crosses do show up, but then no fingerpress is being detected.  I’ll have a look at my setup again, especially the cam. 

again, thx

Sorry!!  All my mistake!  After callibrating and reconfigering the XML file by hand, it all worked well!!  Very Well!!!

TNX

I can’t start tracer on Windows Vista. Using tracer with touchlib beta v1.0. I have copied touchlib and my config file in tracer folder then started it.
Got this:
Touch tracer v0.2

(0, 0) = (0.000000, 0.000000)
(1, 0) = (0.250000, 0.000000)
(2, 0) = (0.500000, 0.000000)
(3, 0) = (0.750000, 0.000000)
(4, 0) = (1.000000, 0.000000)
(0, 1) = (0.000000, 0.333333)
(1, 1) = (0.250000, 0.333333)
(2, 1) = (0.500000, 0.333333)
(3, 1) = (0.750000, 0.333333)
(4, 1) = (1.000000, 0.333333)
(0, 2) = (0.000000, 0.666667)
(1, 2) = (0.250000, 0.666667)
(2, 2) = (0.500000, 0.666667)
(3, 2) = (0.750000, 0.666667)
(4, 2) = (1.000000, 0.666667)
(0, 3) = (0.000000, 1.000000)
(1, 3) = (0.250000, 1.000000)
(2, 3) = (0.500000, 1.000000)
(3, 3) = (0.750000, 1.000000)
(4, 3) = (1.000000, 1.000000)

then:
[Window Title]
Microsoft Windows

[Main Instruction]
touch_tracer.exe has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

[Debug] [Close program]

any suggestions?

I have recompiled with touchlib_beta_1. Now it is working.

Did anyone come across this problem:
Download and compile OK, without problems.
But it doesnt work… I get the screen with the grid, but no capture.
Then when I press Esc, I get an exception:

0x76d4b09e in touch_tracer.exe: Microsoft C++ exception: std::bad_alloc at memory location 0x0012fb20..

And the code at the location is:

if (pfnEncodePointer != NULL)
{
ptr = (*pfnEncodePointer)(ptr); //This is the actual line where the exception occurs…
}

When I run the binaries, it works like a charm...?

Anyone a clue?

Thanks,

Joris

hi all, is this application still supported?

the http://www.lauw.biz/multitouch/tools/msvcr80_msvcp80.rar link seems to be out dated?

icube - 04 September 2008 12:47 AM

hi all, is this application still supported?

the http://www.lauw.biz/multitouch/tools/msvcr80_msvcp80.rar link seems to be out dated?

I didnt renew my domain lauw.biz but moved to multigesture.net

All my applications can be downloaded from: http://www.multigesture.net/downloads/

If you miss specific dll’s, download them from: http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en