Profile_bird

Hey there! keytweeter is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving keytweeter's tweets.

Already using Twitter
from your phone? Click here.

keytweeter

  1. ectively changing the target -- still in an arcball fashion↵At any moment you should be able to recover the position and orientation of the about 1 hour ago from API
  2. e camera in the plane orthogonal to it's optical axis↵4 (mabye) some modifier key left click rotates the camera about it's own axis -- eff about 1 hour ago from API
  3. an arcbal would bel fashion↵2 right click translates the camera along it's optical axis↵3 middle click (or left right click) translates th about 1 hour ago from API
  4. actually translates the camera and and rotates rather than the scene.↵The basic behvaior iavi↵1left click orbits around a targetthe eye in about 1 hour ago from API
  5. nd can be wrapped with something like ofxEasy Cam:↵Cam:↵But instead:↵1 Uses quaternions when doing t↵The basic behavior is:↵I'll shar. SBut about 1 hour ago from API
  6. Eoghan! If you've been working with the OpenGL camera, I can tell you a personal wish: something that acts like ofxCamerag osx3dutils↵f↵:↵A about 1 hour ago from API
  7. nent.↵↓c↓↵I'll know by about 7 today which I can do, and I'll write back then.↑Not feeling any toe-stepping ehre :)↵Haven't from you ina bit about 1 hour ago from API
  8. a jitter and how much is USB -- that's what the LED matrix will tell us. I'm guessing it's all US as they pass through the Direct Show compo about 2 hours ago from API
  9. = ↵Most of the time it just looks like jitter, but check out rows 473-478 for some definite dropped frames.↵No how much of this is in-camer about 7 hours ago from API
  10. t recreated some data I used to havewas looking for last time I saw you.↵Attached is a list of the milliseconds between adjacent frames.= ↵ about 7 hours ago from API
  11. 0;↵if(prevTime == 0) {↵}↵pre↵}↵prevTime = ofGetElap↵Millis();↵int curTime = (curTime - prevTime)curTime↵30ted↵ps3eye output timing↵↑ ↑I jus about 7 hours ago from API
  12. ↓↵() << end5↵ofSle↵(1)↵vidGrabber.grab↵();update#include <fstream>↵ofstream file("out.csv");file↵file.close();doc↵of↵↓↵↓↵↓↵↓↵long prevTime = about 8 hours ago from API
  13. TimeMillfGetE↵();↵while(ofGetEl↵() - startTime < testLength) {↵}↵float testLength = 10; // seconds↵if(vidGrabber.is↵()) {↵}↵cout << ofGetEla about 8 hours ago from API
  14. rates, even though it introduces some glitches not present in the other one.↵Kyellis↵↓↑↵↓↑↵↓↵↑↓↑↵↓↑↵ftp↓↵↑↵la↵↑↓↵float startTime = ofElapsed about 8 hours ago from API
  15. n an image was captured.↵Make sure to change the line I mentioned in ofVideoGrabber ;)↵Let me know if this gets you more reasonable capture about 8 hours ago from API
  16. the trick isn't going to be so much manually tweaking the rates and offsets -- but seeing if we can use timing information to determine whe about 8 hours ago from API
  17. ture and saving aren't in their own threads.↵On the other hand, I've been analyzing the dropped frames from the ps3eye recently, and I think about 8 hours ago from API
  18. my graphics card has tears even with vertical sync enabled unless you're running fullscreen.↵The main problem with this app is that the cap about 8 hours ago from API
  19. g and start capturing, then tab again↵7 to bring everything back and stop capturing↵I did it like this instead of across two screens because about 8 hours ago from API
  20. pattern and the camera rate until they look more stable↵4 move the offset←↓←et if necessaryrate ↵5 go fullscreen↵6 hit tab to hide everythin about 8 hours ago from API