Activity for Martin Kaltenbrunner
-
Martin Kaltenbrunner posted a comment on discussion reacTIVision User Forum
as your screenshot shows, the available midi devices are 3,4,5 though
-
3rd time: you can find out your midi device number with the list_devices script
-
so did you try to edit the file with the actual number of your midi device? as I wrote earlier, you can retrieve the device ids with the list_devices script.
-
apparently the midi.xml is missing in the application bundle, therefore just copy this one as "midi.xml" into your Resources folder inside: https://github.com/mkalten/reacTIVision/blob/1.5.x/midi/demo.xml hint: right-click on reacTIVision.app and "Show Package Contents"
-
place this file as midi.xml into the Resources folder inside the application bundle https://github.com/mkalten/reacTIVision/blob/1.5.x/midi/demo.xml and/or edit the reacTIVision.xml file there pointing to an alternative path of your actual configuration file
-
... and you can list the available midi device number with the included script
-
the default midi configuration file is now inside the application bundle in the Resources folder
-
try these two: <capture width="640" height="480" fps="60" compress="true"/> <capture width="800" height="600" fps="max" compress="true"/>
-
is this the camera you are using? https://en.ids-imaging.com/store/ui-1220le.html if so, it seems that it reports an incorrect camera format somehow. so maybe you could try this configuration, according to its specification: <capture width="752" height="480" fps="max" format="rgb" force="true"/>
-
btw, you could also try the force option for your camera.xml config: <camera driver="default" id="2"> <capture width="968" height="480" fps="max" format="rgb" force="true"/>
-
well, that debug output is not really helpful :S maybe you could try to see yourself at which point in the code it actually crashes ... visual studio should jump to that code position in a debug build, when select the according option after the crash, no?
-
also if the K selection crashes, you could try a debug build and see where that happens, so maybe we can find a fix there to allow you to select the camera formats properly
-
well, I wouldn't give up that quickly, I'd try the following: 1) edit camera.xml with the following attributes: <camera driver="default" id="2"> <capture width="968" height="480" fps="119.9" format="rgb"/> (also try fps="max") or <capture width="968" height="480" fps="146.2" format="rgba"/> or 2) disconnect your logitech camera and try the K selection again
-
well, that's really hard to tell from here ... but I guess the problem may either be the failed format enumeration of the uEye device 1: or the ghost appearance of the secondary UI122xLE device 2: which potentially could point to the same device somehow? UI122xLE is the model name of your actual uEye, no? maybe you could try to uninstall all camera drivers and installe the latest version after reconnecting your camera?
-
looking at your recent output I now can see the second UI122xLE camera device. did you try to set to camera ID #2 with one of the available formats in camera.xml? btw, you can also select one of the available cameras and formats interactively by pressing the K key after running reacTIVision. Due to the lenghty list this may be a bit cumbersome in the current sequential list, but could work ...
-
wow, that logitech camera produces quite some output ;) The uEye seems to show up twice there, I guess that may be the problem. reacTIVision 1.6 tries to emumerate all available cameras and formats, and since the uEye 1: does not enumerate at all it may hang there. why is it showing up twice by the way, are you maybe using two different drivers? And if you are able to send me such a camera I could have a look at it, since I unfortunaty don't have one at hand.
-
Could you post the output from "reacTIVision -l" for both versions? And could you check if you are using a 32bit driver with a 64bit version or vice-versa?
-
Could you post the output from "reacTIVision -l" for both versions?
-
yes, this kind of elliptic distortion is the problem, since yamaarashis need to be decoded based on their precise geometry. I have already partitially resolved this, there is just one more step left to fix that ...
-
well, finalizing the yamaarashis are the last major feature to fix before an official 1.6 release. since their decoding is more error prone on distorted images, fixing and testing the calibration feature for these is still on the todo list. please keep in mind that 1.6 is still work in progress ...
-
Hi Michael, I'll add the files in the next intermediate 1.5.2 release before 1.6 Regarding 1.6 there are still a few minor issues to resolve, but I hope it will follow soon after I hope.
-
you'll need to place the small.trees file into the Resources folder inside the application bundle if you refer to it like that ... I'll include that for the next intermediate 1.5.2 release
-
Did you try to set the frame rate to "max" when using 640x480?
-
Did you try to set the frame rate to "max" when using 640x480?
-
Hi Stefan, this is great news! I'd be really keen to include this feature after the 1.6 release! (at this point an inclusion would just further delay it). But in order to integrate everything better, I'd like to ask you if you would see the possibility to keep everything within a separate MultiCamera driver, which basically leaves the rest of the portvideo code, and most importantly the other driver modules mostly untouched? looking forward! Martin
-
mmh, I am confused .. can you point me somewhere to the particular pyTUIO code? TUIO generally transmits velocity and acceleration already, so there should be no need to calculate that on the client side. Moreover, if you don't need those values you could just simply ignore them ...
-
well weird, but maybe you could also try first with one of our standard TUIO clients for Java/Processing or C++, and see if you experience the same problem ...
-
Hello Andrea, as usual it would be helpful if you could provide more details about your operating system and reactivision version you are actually using ...
-
Hi Andrew, this kind of latencies are obviously not normal and most likely not caused by reacTIVision. Which TUIO client implementation are you using, and are you running the client on a local or remote machine? Regarding the compilation of reacTIVision 1.6, your machine apparently only works with a 32bit build, so you need to change to a 32bit target when compiling the VS2012 project.
-
great, if you upload your video to vimeo, I can add it to the reacTIVision channel:...
-
Assuming you are using Raspian Jessie on your Raspberry Pi, you'll need the following...
-
reacTIVision should compile without problems on the Raspberry Pi, just make sure...
-
OK, apparently you don't have write permissions in your Program Files folder ......
-
I just tried again, and everything seems to work fine though. The calibration should...
-
Hello Robin, the calibration is supposed to be saved automatically ... On which platform/version...
-
regarding camera stitching for portvideo/reactivision you may want to have a look...
-
the 'o' option is for adjusting the camera parameters and not for selection ... if...
-
There is no need for the macam driver, since reacTIVision has internal ps3eye support....
-
I'd take the smallest ... but you should choose a 850nm filter (you link to the 950nm...
-
I'd take the smallest ... but you should choose a 850nm filter
-
Dear Eugene, reacTIVision 1.6 is still in development, therefore you can only access...
-
Hello, reacTIVIsion is quite CPU efficient, and can also run on older/slower and...
-
another useful hint may be to turn off the display (typing N, then S or T to turn...
-
another useful hint may be to turn off the display (typing N, then S or T to turn...
-
another useful hint may be to turn off the display (typing N, then S or T to turn...
-
another useful hint may be to turn off the display (typing N, then S or T to turn...
-
on the other hand, the creation of a FPGA based smart-camera would be definitely...
-
how about your actual CPU usage, when running at 40fps? did you also check your camera...
-
Hello, reacTIVIsion is quite CPU efficient, and can also run on older/slower and...
-
as usual, it would be helpful to know which version of reactivision and operating...
-
you are welcome! just one more remark regarding your camera settings: maybe you could...
-
oh, should be fixed now ...
-
OK, that helped ... I just submitted a patch which should solve your problem. Also...
-
I'll have a look at it, this is not the expected behavior ... can you create a sequence...
-
wow, you must be really quick flipping your pages ... the "cache" you are mentioning,...
-
hi, I just checked the release package and it seems to be badly signed indeed, causing...
-
hi, I just checked the release package and it seems to be badly signed indeed, causing...
-
hi, I just checked the release package and it seems to be badly signed indeed, causing...
-
hi, I just checked the release package and it seems to be badly signed indeed, causing...
-
hi, I just checked the release package and it seems to be badly signed indeed, causing...
-
yes, you may need to set the mirror="true" option to the fiducial configuration in...
-
OK, I checked the CL driver on a 64bit system, and since the driver is 32bit only...
-
OK, I tested everything with the CL-Eye driver and pushed and according fix to the...
-
Dear Ran, reacTIVision 1.6 is still in development ... I will document the relevant...
-
Three questions: Which driver are you using for your PS3Eye? Which OS version are...
-
Your CPU most probably doesn't support the 64bit AVX extensions, therefore just compile...
-
Yes, reacTIVision 1.5 supports MIDI, maybe that space in "demo .xml" could be the...
-
yes, the current development code for reacTIVision 1.6 on Github already includes...
-
I guess you own already a computer, so maybe you give it a try with your existing...
-
the minimum CPU requirements for reacTIVision basically depend on your camera resolution...
-
reacTIVision relies on a correctly installed and configured SDL2 library (either...
-
reacTIVision relies on a correctly installed and configured SDL2 library (either...
-
BTW, regarding latency: which platform are you using reacTIVision on?
-
you always can try the current development code from github: http://github.com/m...
-
check out your sensor or more likely the bottom of your lens. an IR cut filter reflects...
-
check out your sensor or more likely the bottom of your lens. an IR cut filter reflects...
-
OK, I see you tested things before ... Reactivision 1.6 will provide smoother finger...
-
Hi Gisle, I didn't notice such a thing before, but did you check the problem at the...
-
Hello Ran, making an interactive whiteboard with IR pens already has been possible...
-
Dear Samed, it seems that you asked this before in another thread, the answer is...
-
Dear Samed, it seems that you asked this before in another thread, the answer is...
-
this error message can appear for two reasons: 1) the MIDI device ID is less than...
-
this error message can appear for two reasons: 1) the MIDI device ID is less than...
-
this error message can appear for two reasons: 1) the MIDI device ID is less than...
-
this error message can appear for two reasons: 1) the MIDI device ID is less than...
-
this error message can appear for two reasons: 1) the MIDI device ID is less than...
-
I just tried again, and everything works fine on my side, which version of reacTIVision...
-
Hi Ryan, you can retrieve your actual MIDI device IDs by executing the included list_devices...
-
I'd also say that getting a different camera saves work for both of us, since I wouldn't...
-
I'd also say that getting a different camera saves work for both of us, since I wouldn't...
-
OK, it seems that the camera enumeration is a bit overwhelmed by the mancam and kinect...
-
which driver are you using for the PS3Eye? but if it works, I'd advise to use the...
-
which driver are you using for the PS3Eye? but if it works, I'd advise to use the...
-
this is the place to post some infos about your projects powered by reacTIVision,...
-
Hi Keith, since you mention a Mac Mini, I guess you are planning to use MacOS. Can...
-
thanks, but the command option I meant was -l (small L) in any case, this probably...
-
thanks, but the command option I meant was -l (small L) in any case, this probably...
-
thanks, but the command option I meant was -l (small L) in any case, this probably...
1 >