buffering PVector from kinect and controlp5 issues

lukasz

buffering PVector from kinect and controlp5 issues

in Contributed Library Questions • 11 months ago

I'm having two issues:

for some reason controlp5 looks really small in the sketch (assuming I have to set the z-axis somehow? but setPosition doesn't seem to take a Z axis)

I would like to know what to read up on to "buffer" (if thats what you would even call it) 10 frames of PVector. I am not even sure what it is other than what this book is calling a vector. But could I push this to a class? is it an array object? I really don't know what I'm working with so no idea how I would store it :(

import processing.opengl.*;
import SimpleOpenNI.*;
SimpleOpenNI kinect;
import controlP5.*;
ControlP5 cp5;
int sliderValue = 180;
void setup(){
size(1024, 768, OPENGL);
kinect = new SimpleOpenNI(this);
kinect.enableDepth();
cp5 = new ControlP5(this);
cp5.addSlider("sliderValue")
.setPosition(10,10)
.setRange(0,180)
;
}
void draw(){
background(0);
kinect.update();
translate(width/2, height/2, -1000);
rotate(radians(sliderValue));
stroke(255);
PVector[] depthPoints = kinect.depthMapRealWorld();
for(int i = 0; i < depthPoints.length; i++){
PVector currentPoint = depthPoints[i];
point(currentPoint.x, currentPoint.y, currentPoint.z);
}
}

this is what I'm getting:

Replies(3)

andreas.s..

Re: buffering PVector from kinect and controlp5 issues

11 months ago

Hi, when working with 3D transformations or camera movements, these spatial changes will apply to controlP5 elements if not separated by push/popMatrix(). what you can do in your case is to start your drawing routine with a pushMatrix(); and end with a popMatrix(); this should solve the displacement of controllers.

akiersky

Re: buffering PVector from kinect and controlp5 issues

11 months ago

Hi Lukaz,

andreas' suggestion should work, but you can also gain more control of your controlp5 drawing by turning off the auto draw and explicitly drawing it: cp5.draw();

use setAutoDraw(boolean) to toggle the autodraw on and off.

good luck!

lukasz

Re: buffering PVector from kinect and controlp5 issues

11 months ago

what you're saying makes sense, I've come across push and pop but what I am confused about is this is being set in the setup and translate happens in the draw-- so not entirely sure how to handle this. do I have to put controlp5 in draw so it redraws it every time? this seems like it wouldn't be ideal performance wise.

edit: ok it seems to work, but its a bit of black magic to me. I did it in draw() function only, but no idea why it now doesn't affect the controlp5 stuff:

void draw(){
background(0);
kinect.update();
pushMatrix();
translate(width/2, height/2, -1000);
rotateX(radians(180));
translate(0, 0, 1000);
rotateY(radians(rotation));
rotation++;
stroke(255);
PVector[] depthPoints = kinect.depthMapRealWorld();
for(int i = 0; i < depthPoints.length; i+=10){
PVector currentPoint = depthPoints[i];
point(currentPoint.x, currentPoint.y, currentPoint.z);
}
popMatrix();
}

Top Reply