Menu ▾ ▴

reacTIVision 1.5 released

2014-10-21
2014-11-08
  • Martin Kaltenbrunner

    Surprise, surprise! After an extended time of inactivity there is a new reacTIVision release available! While I initially only planned some minor updates in order to recompile on more recent systems, this eventually resulted in a major infrastructure update that includes much improved camera support and configuration options on all platforms as well as some internal tweaks which should improve the overall performance. Apart from that this release does not yet include any changes to the core fiducial and finger tracking, which will be included in a future 1.6 release!

    Here is a complete list of changes, the binaries and source code is available as usual for Windows, Mac OS X and Linux systems. Please let me know of you encounter any unexpected problems, but also post a report of successful tests including some information about your setup, such as system, cameras and table configurations.

    • new AVFoundation camera driver for MacOS X (including controls)
    • new videoInput camera driver for Windows (including controls)
    • improved Video4Linux2 camera driver for Linux (including controls)
    • list all available cameras and formats (via -l startup argument)
    • support MJPEG decompression for higher USB camera frame rates
    • support IIDC-over-USB cameras through libdc1394
    • added frame cropping configuration (xoffset,yoffset,xwidth,yheight)
    • multithreaded thresholder for reduced latency on multicore CPUs
    • allow the adjustment of the threshold tile size
    • updated FrameEqualizer for faster background subtraction
    • sending correct TUIO 1.1 source messages
    • added a quicker and less tedious calibration mode
    • migrated the user interface to SDL 2.0 (less CPU overhead)
    • fixed a MIDI configuration file location bug on MacOS X
    • added fullscreen toggle (via F1 key)
    • added a headless mode (via -n startup argument)
    • improved Linux desktop integration
    • updated oscpack, tinyxml, portmidi and dc1394 libraries
    • added x86_64 and dropped PPC architecture on MacOS X
    • provide x86_64 and i686 binaries for Mac OS X and Linux
    • updated XCode and Visual Studio 2012 projects
    • added a project for the Codeblocks IDE on Linux
    • removed the dtouch fiducial tracker
    • removed the now outdated VdigGrab, DSVideolib and Video4Linux drivers
    • new application icon

    have fun, Martin.K

    PS: The 32bit binary for Mac OS X is a legacy build for Intel 32bit processors on Mac OS X 10.5 or later. I recommend to use the 64bit build for Mac OS X 10.7 or later, which provides better performance and camera support.

     

    Last edit: Martin Kaltenbrunner 2014-10-24
  • kodamapixel

    kodamapixel - 2014-10-27

    I can't get 1.5 to launch when my Microsoft LifeCam Cinema is connected (crash on launch); if it's disconnected, 1.5 launches with the FaceTime camera, no problems. Running the list_devices.app shows 2 AVFoundation cameras: 0: (null), 1: FaceTime HD.

    System: reacTIVision 1.5 64bit, OS X 10.10, MacBook Pro Retina, 2.5 GHz Intel Core i7, 16 GB RAM, NVIDIA GeForce GT 750M.

     
  • Martin Kaltenbrunner

    thanks for the feedback! does the Microsoft LifeCam Cinema work properly in other applications, such as photo booth?

    it seems that the Microsoft LifeCam Cinema only works with the macam quicktime driver. unfortunately this is very outdated software, therefore it won't work with the 64bit version. you may have limited results with the 32bit version though which still uses the older quicktime camera driver ...

     

    Last edit: Martin Kaltenbrunner 2014-10-27
  • kodamapixel

    kodamapixel - 2014-10-28

    Thanks for the reply, Martin. Yes, the LifeCam Cinema works in OS X 10.10 Photo Booth, Quicktime, etc. It also seems to work fine in the 32bit version of 1.5.

     
  • Martin Kaltenbrunner

    Good to know that the 32bit version works as expected in this case ...
    Could you do me the favour and post the console output of the failing 64bit version?
    Open a Terminal and 'cd' to your reacTIVision installation directory and then type:

    ./reacTIVision.app/Contents/MacOS/reacTIVision
    and also
    ./reacTIVision.app/Contents/MacOS/reacTIVision -l

    This should provide some more information ...

     

    Last edit: Martin Kaltenbrunner 2014-10-28
  • kodamapixel

    kodamapixel - 2014-10-29

    When I run the first line, this is what I see in Terminal (when LifeCam attached I also get a "reacTIVision quit unexpectedly" OS X message):


    reacTIVision 1.5 (Oct 23 2014)

    no DC1394 cameras found
    2 AVFoundation cameras found
    Segmentation fault: 11


    And the second line gives me this:


    reacTIVision 1.5 (Oct 23 2014)

    no DC1394 cameras found
    2 AVFoundation cameras found:
    0: (null)
    format: JPEG (dmb1)
    160x120 30|20|15|10|7.5 fps
    176x144 30|20|15|10|7.5 fps
    320x240 30|20|15|10|7.5 fps
    416x240 30|20|15|10|7.5 fps
    352x288 30|20|15|10|7.5 fps
    640x360 30|20|15|10|7.5 fps
    640x480 30|20|15|10|7.5 fps
    800x448 30|20|15|10|7.5 fps
    800x600 30|20|15|10|7.5 fps
    960x544 30|20|15|10|7.5 fps
    1280x720 30|20|15|10|7.5 fps
    format: YUYV (yuvs)
    160x120 30|20|15|10|7.5 fps
    176x144 30|20|15|10|7.5 fps
    320x240 30|20|15|10|7.5 fps
    352x288 30|20|15|10|7.5 fps
    424x240 30|20|15|10|7.5 fps
    640x360 30|20|15|10|7.5 fps
    640x480 30|20|15|10|7.5 fps
    800x448 20|15|10|7.5 fps
    800x600 15|10|7.5 fps
    960x544 15|10|7.5 fps
    1280x800 10 fps
    1: FaceTime HD Camera
    format: YUYV (yuvs)
    1280x720 30 fps
    format: YUYV (2vuy)
    1280x720 30 fps
    format: other (420v)
    1280x720 30 fps
    format: YUYV (yuvs)
    640x480 30 fps
    format: YUYV (2vuy)
    640x480 30 fps
    format: other (420v)
    640x480 30 fps
    format: YUYV (yuvs)
    320x240 30 fps
    format: YUYV (2vuy)
    320x240 30 fps
    format: other (420v)
    320x240 30 fps
    2 MIDI out devices found:
    2: to Max 1
    3: to Max 2


     
  • Martin Kaltenbrunner

    I finally found that bug and just updated the mac 64bit release files accordingly, let me know if it works now ...

     

Log in to post a comment.