search

erickmurillo1701 / ubidisplays

Automatically exported from code.google.com/p/ubidisplays
1 stars 0 forks source link

Its impossible sometimes to remove the red screen noise #9

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Setting up the projector and kinect it's a bit of a trial and error experience. 
Sometime it works other times it doesn't. Is there a sweet spot to position the 
kinect and projector
in order to make it work at least most of the time. I'm attaching a picture of 
my setup.
https://www.dropbox.com/s/0s48efowqlffqze/ubidisplays_setup.jpg

Original issue reported on code.google.com by manor...@gmail.com on 1 Feb 2013 at 3:24

GoogleCodeExporter commented 8 years ago 
Hi there,

Thanks for the report (and handy drawing)!  The red noise is data from the 
Kinect which doesn't lie along the plane / flat surface selected for the 
Kinect.  Your setup looks good, but here are a few tips:

1) Try to keep the Kinect around 1.2 meters.  The noise increases as you move 
it further away from the surface, placing it closer will reduce it.  There are 
a few graphs on pages 5 and 6 of this paper which will help:  
http://highwire-dtc.com/url/ubidisplayspaper

2) Sometimes, the corners that you select are anomalous.  You can try holding 
down shift, selecting a corner, and replacing it in a similar place in order to 
get the display to recompute its plane.

3) In the sample displays, you will find a snippit of code which looks like 
this:

`
// Get me some lowest point cloud data.
pMTProcessor = new KinectTouch({
        debug : false,              // Turn on debug points.
        trails : false,             // Turn on finger trails (this shows the Kinect data used to detect the finger).
        point_limit : 200,          // The number of points we are allowed to process.
        surface_zoffset : 0.015,    // The offset from the surface (in meters) at which to start capturing data.
        height : 0.01,              // The distance from the surface offset (in meters) at which to stop capturing data.
});
`

If you increase the `surface_zoffset` parameter (cm), you will make the toolkit 
sense further above the selected surface, and thus hopefuly eliminate more of 
the noise.

In the new version I'm working on, this will hopefully be less of an issue.  
May I ask what you are planning to make? If you are building a foot display, 
there are some other tips and tricks which you can do in the Javascript to make 
it much more responsive and generally better.  :)

All the best,

John

Original comment by asheepca...@gmail.com on 3 Feb 2013 at 12:14