Line 119: imagee
https://github.com/mkalten/reacTIVision/blob/master/README.txt

Is there a way to let tuioClient listen to a remote IP address and port?
For example like:
TuioProcessing tuioClient = new TuioProcessing (this, "192.168.0.109", 3333)

The angle for a fiducial marker is seemingly only updated after a certain minimum angle delta is reached.
The verbose output suggests that reacTIVision is capable of detecting a more accurate angle as the angle values reported are not in fixed intervals. Sometimes after rotating a marker back and forth a few times, the angle values sometimes lie between previous values, suggesting marker recognition is able to determine a more accurate angle.

Is there any way to improve angle accuracy by myself or this an issue with reacTIVion/marker recognition itself?

Hi
I have another problem:
I am on Mac OS X 13.3 and I use reacTIVision 1.5 (the last released version).

It works alright with the built in laptop webcam, but if I want to use an external logitech 1080p cam, I can't get a proper input image.

I tried to work with the camera.xml:

<?xml version="1.0" encoding="ISO-8859-1" ?>
<portvideo>
    <camera id="0">
        <capture width="640" height="480" fps="max" compress="false" />
        <settings brightness="default" contrast="default" gain="default" shutter="default" exposure="default" sharpness="default" gamma="default" focus="default" />
        <frame width="max" height="max" xoff="0" yoff="0" />
    </camera>
</portvideo>

Results in this:
4* the camera input, squeezed in y-axis and leaving a lot of black space. (you can see my hand)

I tried the -l startup option to list all cameras:

./reacTIVision -l             
reacTIVision 1.5.1 (Oct 22 2016)

no DC1394 cameras found
no PS3Eye cameras found
3 AVFoundation cameras found:
	0: HD Pro Webcam C920
		format: YUYV (yuvs)
			160x90 30 fps
		format: YUV420 (420v)
			160x90 30 fps
		format: YUYV (yuvs)
			160x120 30 fps
		format: YUV420 (420v)
			160x120 30 fps
		format: YUYV (yuvs)
			176x144 30 fps
		format: YUV420 (420v)
			176x144 30 fps
		format: YUYV (yuvs)
			320x180 30 fps
		format: YUV420 (420v)
			320x180 30 fps
		format: YUYV (yuvs)
			320x240 30 fps
		format: YUV420 (420v)
			320x240 30 fps
		format: YUYV (yuvs)
			352x288 30 fps
		format: YUV420 (420v)
			352x288 30 fps
		format: YUYV (yuvs)
			432x240 30 fps
		format: YUV420 (420v)
			432x240 30 fps
			640x360 30 fps
		format: YUYV (yuvs)
			640x480 30 fps
		format: YUV420 (420v)
			640x480 30 fps
		format: YUYV (yuvs)
			800x448 30 fps
		format: YUV420 (420v)
			800x448 30 fps
			800x600 30 fps
		format: YUYV (yuvs)
			800x600 24 fps
		format: YUV420 (420v)
			864x480 30 fps
		format: YUYV (yuvs)
			864x480 24 fps
		format: YUV420 (420v)
			960x720 30 fps
		format: YUYV (yuvs)
			960x720 15 fps
		format: YUV420 (420v)
			1024x576 30 fps
		format: YUYV (yuvs)
			1024x576 15 fps
		format: YUV420 (420v)
			1280x720 30 fps
		format: YUYV (yuvs)
			1280x720 10 fps
		format: YUV420 (420v)
			1600x896 30 fps
		format: YUYV (yuvs)
			1600x896 7.5 fps
		format: YUV420 (420v)
			1920x1080 30 fps
		format: YUYV (yuvs)
			1920x1080 5 fps
	1: FaceTime HD Camera
		format: YUV420 (420v)
			1920x1080 30 fps
			1280x720 30 fps
			1080x1920 30 fps
			1760x1328 30 fps
			640x480 30 fps
			1328x1760 30 fps
			1552x1552 30 fps

But even if I adjust the settings to this:

<?xml version="1.0" encoding="ISO-8859-1" ?>
<portvideo>
    <camera id="0">
        <capture width="1920" height="1080" fps="max" compress="false" />
        <settings brightness="default" contrast="default" gain="default" shutter="default" exposure="default" sharpness="default" gamma="default" focus="default" />
        <frame width="max" height="max" xoff="0" yoff="0" />
    </camera>
</portvideo>

I get an even weirder image:

When running hitting the o shortcut, which should bring up the camera options does not work either.

If there was anybody who has experience something similar or has another hint, I would be very glad to hear that.
Cheers

___ Edit: ____

Oh also I get this information when starting via Terminal:

$ cd reacTIVision.app/Contents/MacOS 
$ ./reacTIVision  

reacTIVision 1.5.1 (Oct 22 2016)

no DC1394 cameras found
no PS3Eye cameras found
3 AVFoundation cameras found
2023-11-20 15:41:06.590 reacTIVision[27942:8202306] CameraControl Error: IOCreatePlugInInterfaceForService returned 0xe00002be.
2023-11-20 15:41:06.591 reacTIVision[27942:8202306] 		ERR: couldn't create VVUVCController with locationID 288358400, 11300000
camera: HD Pro Webcam C920
format: 1920x1080, 5fps
render: opengl

But I don't understand this either...

as discussed at https://sourceforge.net/p/reactivision/discussion/user/thread/9504717b/#32be
it would be super to have a basic multi-cam input option.
i will start with the porting of the things mostly already done by cmayer0087 to the simpler approach based on the current master branch. Pull request will follow.

This Feature request is meant as discussion platform for 'what should work in which way'.

Current Approach from my side would be:

• Getting v4l2loopback to work with portvideo to have a stable test-setup (more info)
• port/copy MultiCamera Driver (mainly done)
• document usage

configuration would be done in camera.xml something like this:

<portvideo>
    <camera driver="multicam" id="0">
        <capture format="mjpeg" width="600" height="360" fps="30" color="true" flip_h="false" flip_v="false"/>
        <settings/>
        <frame width="600" height="360" xoff="0" yoff="0" mode="-1"/>
        <childcamera driver="default" id="0">
            <capture format="mjpeg" width="320" height="240" fps="30" color="true" flip_h="false" flip_v="false"/>
            <settings/>
            <frame x="100" y="0" width="200" height="200" xoff="110" yoff="30" mode="-1"/>
        </childcamera>
        <childcamera driver="default" id="19">
            <capture format="mjpeg" width="320" height="240" fps="30" color="true" flip_h="false" flip_v="false"/>
            <settings exposure="auto"/>
            <frame x="300" y="0" width="300" height="200" xoff="10" yoff="30" mode="-1"/>
        </childcamera>
        <childcamera driver="default" id="20">
            <capture format="mjpeg" width="320" height="240" fps="30" color="true" flip_h="false" flip_v="false"/>
            <settings exposure="auto"/>
            <frame x="100" y="200" width="240" height="140" xoff="20" yoff="50" mode="-1"/>
        </childcamera>
    </camera>
</portvideo>

the idea is you have a canvas defined by the first <capture width="600" height="360" /> tag (green border).
than for every camera you want to show you create one <childcamera> tag. in this element the <capture> tag defines the hardware camera config/format. then there is a <frame x="100" y="200" width="240" height="140" xoff="20" yoff="50" mode="-1" /> tag to define the position and visible portion of the camera image.

If you have ideas how to change this for easier understanding pleas let me know.

hello, i am on Linux, Manjaro, and use ReacTIVision (this works good).
And then i start Pd (Pd-L2ork)and when i load a sketch it says: couldn't create,
so Pd can not create the tuioclient object,
i used the 1.1.5 zip and the later 1.3 zip and still no succes.
I just load the things from the unpacked zip folder.
Can someone help me out here please, i searched a lot but still the same.
the tuioclient object will not create.
Do i miss something; a library or is it just a Pd thing, where do i have to put the files.
Many thanks, Dian

Good evening at all. I need help for my processing project; i'll explain: when i start the sketch in processing the laptop's webcam works but how i open reactivision the laptop's webcam does not work anymore and reactivision tells me it does not find any webcam. i hope you can will help me.

Testing the new Yamaarashi symbols, they are detected, but give 0, 0 position, so their numbers appear together at top left corner of the screen.

this is the verbose output:

set obj 0 (80) 0 0 3.89442 0 0 0.117961 0 3.3703
set obj 0 (80) 0 0 3.89442 0 0 0 0 -3.18812
set obj 0 (80) 0 0 3.91981 0 0 0.0985694 0 2.40413

Hey Martin,

we wanted to use reacTIVision on a Samsung Sur40. The problem is that the touch screen (which is the current camera) ist not found by the application. Multitouch is working on Linux though. We disabled touch for the system enviroment so it was only possible to use mouse and not your actual hands and touches. This step didn't solve our problem. We know that because we used VLC Media Player to capture the grayscale video output of the touch surface when it was enabled and after disabling touch in Terminal it did not record anything at all. Do you have any idea how to enable the camera for reacTIVision?

Hi, I'm currently working with a SUR40 with Windows 10. The objective is to develop a small Unity application where you can control virtual object using real ones with fiducial markers. I thought about using reacTIVision to get the TUIO informations to my application. So I downloaded reacTIVision 1.5.1 and try to get it running but everytime I start it, it quits without any message.
I also tried to make it work using the sources. But when trying to start the compiled program, it crashes with an error message saying (translated from french so maybe innacurate) "Application couldn't start properly (0xc000007b). Presse ok to quit.".
I've seen the issue #34 and tried to use SurfaceToTuio but I got to admit I may have not quite underestand how all of this works.
Has anyone any clues about why it won't work and how to run it ?

reacTIVision 1.5 (Nov 6 2014)

no DC1394 cameras found
1 AVFoundation camera found
2015-04-02 22:53:10.846 reacTIVision[2775:42460] CameraControl Error: IOCreatePlugInInterfaceForService returned 0xe00002be.
fish: Job 1, './reacTIVision' terminated by signal SIGSEGV (Address boundary error)

I tried building the application myself and this seems to be happening on line 468 of VVUVCController.m - EXC_BAD_ACCESS. I assume that the problem lies with https://github.com/mrRay/VVUVCKit? By the way, could you please add that dependency to the readme?

Hello, my first question here! I am a Student, new to programming I would like to use reactivision+ Tuio with Processing.org. I understand I need to use Processing 2.0 (is is correct?) but cannot get Processing to recognise the presence of the reactivision library. Would you please firstly walk me through the install process then the set up process, laypersons language please....appriciated

Is there a way to include custom fiducial markers? How are they implemented and why do the current ones look like they do right now.
I know this project is kinda not maintained, but maybe somebody is still keen to answer.

system:

• kubuntu 16.10 64bit
• pulled repository at commit 10744ef; make all

expected behavior:

1. if camera is set to absolute exposure (done with guvcview -device="/dev/video0" --control)
2. this value should be written in the camera.xml config file
3. on next start the values from camera.xml should be used to set the actual parameters.
4. on exit save the same value as read - or if modified save new value.

current behavior:
1 + 2 same as expected
3 on restart of reacTIVision camera again start in exposure auto mode.
4 on next exit exposure is saved as auto

Is there a possibilty to swap X & Y Input? I want to use the Samsumg S40 in Portrait mode and therefore I need flipped coordinates

in floatpoint.h, DoublePoint define as follows:
typedef struct DoublePoint{ short x, y; }DoublePoint;

shouldn't it be double x，y? or there are some other considerations？

Hi everyone.

How about changing VisualStudo2017 to be the official compiler used to build the Windows version?
VisualStudio 2012 is old and there is no community version, which limits the number of people who can build it.

When compiling the master branch with VS2017, the following error occurs, but I was able to solve the error by rebuilding libusb with VS2017.

``''
Error LNK2001 unresolved external symbol ___iob_func reacTIVision reacTIVision\cTIVisionwindowslibusb-1.0.lib(core.obj) 1
Error LNK2001 unresolved external symbol _sscanf reacTIVision reacTIVision
Error LNK1120 2 unresolved externals reacTIVision reacTIVision reacTIVision reacTIVision Windows\blur32DebugreacTIVision.exe 1.

Hey,
I am currently trying to install the reactivision_1.5.1-1_armhf.deb on the raspberry pi 3 running the latest raspbian-lite. There are several packages missing, which I'd have to install. However libjpeg-turbo8 does not exist (anymore?) in raspbian to be installed. Installing, what I think is the replacement package, libjpeg62-turbo-dev does not resolve the issue when installing the .deb.

Do you have any idea how to fix this?

pi@tidreactivision1:~ $ sudo dpkg -i reactivision_1.5.1-1_armhf.deb 
(Reading database ... 43980 files and directories currently installed.)
Preparing to unpack reactivision_1.5.1-1_armhf.deb ...
Unpacking reactivision (1.5.1-1) over (1.5.1-1) ...
dpkg: dependency problems prevent configuration of reactivision:
 reactivision depends on libsdl2-2.0-0 (>= 2.0.4); however:
  Package libsdl2-2.0-0:armhf is not installed.
 reactivision depends on libstdc++6 (>= 5.2); however:
  Version of libstdc++6:armhf on system is 4.9.2-10.
 reactivision depends on libjpeg-turbo8 (>= 1.3); however:
  Package libjpeg-turbo8 is not installed.

dpkg: error processing package reactivision (--install):
 dependency problems - leaving unconfigured
Processing triggers for hicolor-icon-theme (0.13-1) ...
Processing triggers for mime-support (3.58) ...
Errors were encountered while processing:
 reactivision
pi@tidreactivision1:~ $ uname -a
Linux tidreactivision1 4.9.28-v7+ #999 SMP Tue May 16 14:03:19 BST 2017 armv7l GNU/Linux
pi@tidreactivision1:~ $ 

It would be awesome to use mobile devices for fast prototyping purposes. How difficult would it be to port it?

found that the default value for tile size is set to 10.
https://github.com/mkalten/reacTIVision/blob/master/common/Main.cpp#L92

this causes artifacts in the thresholder algorithm - visible as black or white horizontal stripes.
if i use the onscreen option (key g) and change the tile size it locks me to the value 2. i can't change this. but the strips are gone. if i use the xml configuration file and set other values (for example 20) this gives no visible artifacts. (but i don't know if such a high value can make sense... have to read more about how this all works...)

seems this is set / initalized at FrameThresholder.cpp#L144
if i understand this correct it is also dependent on much threads are used - i checked this with setting threads="1" and now i was able to choose 2,3,4,5,6,8,10,12,15,20,24,30,40,60,120.
so eventually at some point it would make sense to allow more threads for big pixel formats?

Hello,

I used the grid calibration option of Reactivision because I'm using a Fisheye camera and I also want to ignore some parts of the picture captured by it. However the positions of the blobs I receive in my client are the same before and after the calibration.

Am I missing an intermediate step?
Thanks in advance!

i tried to use reacTIVision in combination with the v4l2loopback (https://github.com/umlaeute/v4l2loopback) module - (just to have more options to preprocess the camera image - for example stitching multiple streams / applying other prefiltering / feeding video files or static images...)

but currently reacTIVision fails to open the v4l2loopback stream.
could this be caused by the loopback-device does not offer controls for brightness and such?
is there any compile flag other option to enable more debugging output?
i found / changed the makefile to
reacTIVision/linux/Makefile

# CFLAGS = $(COPTS) $(SDL_CFLAGS) $(INCLUDES) -DLINUX -DOSC_HOST_LITTLE_ENDIAN -DNDEBUG
CFLAGS = $(CDEBUG) $(SDL_CFLAGS) $(INCLUDES) -DLINUX -DOSC_HOST_LITTLE_ENDIAN

but this does not give me more information in the terminal for 'what happens' and 'why it fails to use the cam'
(i asked this question first in the forum at https://sourceforge.net/p/reactivision/discussion/user/thread/db710c28/#)

Legacy XCode project for Mac OSX doesn't compile.

Hi all,
i've an old macbook pro on 10.12.6 and no xcode installed.
Is it possible to download somewhere an already compiled application ?
I don't have xcode and have no idea how it works...
thanks in advance

Hello MK! I have to tell you that i'm using reactivision since 2012 and i love it! Now, my problem is when I try to adjust the wide 16:9 grid the result is all deformed and it looks like a mess.

This is the grid adjusted:
.

And this is the result:

Thanks for all bro! Have a nice week!

Hey everyone, i wanted to use reacTIVision on the SUR40 with Windows 7. Everytime i try to start it, i get an error. I know that there is SurfaceToTuio but it doesn't work. Anyone here using reacTIVision on the SUR40 with Windows?

Hi !
I'm stuck on a strange error... I've installed reacTIVision and all the libs on a Raspberrry pi 3,
I'd clone your github repo and then execute make -d -j6 to compile. Then I got the reacTIVision executable and reacTIVision.desktop (wich doesn't work by the way)
I can run reacTIVision by typing ./reacTIVision
then I get that :

reacTIVision 1.6 (Sep 20 2017)

camera: UVC Camera (...) (...)
driver: default
codec: yuyv
format: 640x480, 30fps
TUIO/UDP ...
TUIO/TCP ...
TUIO/WEB ...
TUIO/FLC ...
tuio/src [email protected]
SDLInterface not available!

commands ...

So everything seems to work as charm but I can't have any GUI ...
Where this message comes from ? : "SDLInterface not available!"

Thanks for this great project and for your time
Best regards !

For some weird reason, the program crashes because the Tangible Interaction Framework stops working, I geniunely have no clue what that even is, is it something related to the NET framework?

Also, I wanna point out that I am using Windows 7.

Would gladly appreciate help :)

if you have a cam that is fixed at a device name with an id higher than 'count' video devices - so the list
from $ ll /dev/video* has spaces in the numbering reacTIVision/portvideo fails to open it as it thinks the devices have to be in order.
i found this in #20.
from a short look there are multiple places in the code that need to be changed.
one point i think is
V4Linux2Camera.cpp#L261
sprintf(v4l2_device,"/dev/video%d",cfg->device);
if i understand it correct currently in the camera.xml the id attribute in <camera driver="default" id="0"> means the portvideo internal camera list id. (that makes sens so you can support other non v4l2 cams also..) but it is also used to generate the v4l2 device name.
i currently don't have a good idea how to fix this in an nice way.

V4Linux2Camera.cpp#L258 is one of the other points where the numbering is directly used that i found..
if ((dev_count == 0) || (cfg->device<0) || (cfg->device>=dev_count)) return false;

I'm opening this issue as a kind of reminder for myself, since we are planning on implementing WebSocket support in a current project. Pull request hopefully coming soon :-)

Hello,

I've downloaded the latest (1.6) version and although it works, I can't change the camera settings in camera.xml like I could before. Any change I make (e.g. camera id, size) gets overwritten once I start reactivision. Any ideas on what the problem there could be?

Some Video4Linux drivers (such as the experimental one for the SUR40 :-) directly provide an 8-bit greyscale image with format code V4L2_PIX_FMT_GREY. It's probably sufficient to just add this in https://github.com/mkalten/reacTIVision/blob/master/linux/V4Linux2Camera.cpp#L56 and https://github.com/mkalten/reacTIVision/blob/master/linux/V4Linux2Camera.cpp#L420 but I'm not familiar enough with portvideo to tell if that is indeed enough...

Hi
I installed http://prdownloads.sourceforge.net/reactivision/reactivision_1.5.1-1_amd64.deb on a debian system.
It"s ok with the default fiducials: I can see the green numbers on each default fiducial when put under the cam, but I'ld like to use the mini set of fiducials.
I updated the reacTIVision.xml file with this line:

<fiducial engine="amoeba" tree="mini.trees" />`

or this one:

<fiducial amoeba="mini" />

But it seems reactivision can't detect these mini fiducials.
Is there a special trick to use these mini fiducials ?
Would reactivision 1.6 better work than 1.5 ? (Then I'ld have to compile it).
If 1.5 is really not working with the mini fiducials, can it work with the "small" set ?
Thanks in advance

Reactivision 1.5 armhf when installed on Raspberry Pi is giving 2 to 3 fps.
Reactivision 1.4 when compiled from source gives 30 fps which is good but gets crashed.

Hello,

I need to run the reacTIVision server on windows, but Visual Studio gives me the following compile error:

Error C2371: 'int32_t': redefinition; different basic types

The error comes up in TcpSender.cpp in the first code lines:

#ifdef  WIN32
#ifndef int32_t
typedef DWORD int32_t;
#endif
#endif

Any help?

Hi There,

can you please give some insight into how the OSC structure is built? Perhaps add this to the readme.

kind regards
Tony

continuing the other issue:
sudo modprobe bcm2835-v4l2 on raspberry pi 3 with latest rasbian and picam2 worked. Tested it with the motion tool to capture frames via v4l2.

However when starting reactivision 1.5.1 I get a wrong camera resolution (848x32 with a framerate of 30FPS). Setting any manual width/height in the camera.xml results in this dimension. When doing capture width="max" height="max" it actually works sometimes, sometimes it crashes. It reports 3280x2462.
The maximum width/height might be much for the raspberrypi to handle.

I also tried reducing the framerate to 15fps but the option seems to be ignored and is set back to 90fps.

Is there something I might be missing?

Hi,
I try for a few days to setup reacTIVision with a SUR40 with a fresh installed Ubuntu 20.04 (Kernel: 5.13.0-41-generic
).
But reacTIVision does not find any camera. I figured out that /dev/video0 did not exist but /dev/v4l-touch0 , so I created /dev/video0 as a symlink so that it could be found as a camera by v4l2-ctl (see below).
Touch is working out of the box.

Output reacTIVision 1.5.1 (latest amd64 .deb release from http://reactivision.sourceforge.net/):

$ reacTIVision 
reacTIVision 1.5.1 (May 18 2016)

no DC1394 cameras found
Error loading camera configuration file: default
1 V4Linux2 device found
VIDIOC_REQBUFS: Cannot allocate memory
Error requesting buffers.
could not initialize camera
render: opengl

Output reacTIVision 1.6 (compiled from latest commit on master):

$ ./reacTIVision 
reacTIVision 1.6 (May 12 2022)

VIDIOC_REQBUFS: Cannot allocate memory
Error requesting buffers.
could not initialize selected camera
VIDIOC_REQBUFS: Cannot allocate memory
Error requesting buffers.
could not initialize default camera
TUIO/UDP messages to 127.0.0.1@3333
TUIO/TCP socket created on port 3333
TUIO/WEB socket created on port 8080
TUIO/FLC receiveOscData@_OscDataStream
tuio/src [email protected]
render: opengl

v4l2-ctl info:

$ v4l2-ctl --list-devices
Samsung SUR40 (usb-0000:00:13.2-1):
	/dev/v4l-touch0

Cannot open device /dev/video0, exiting.

$ v4l2-ctl --device=/dev/v4l-touch0 --all
Driver Info:
	Driver name      : sur40
	Card type        : Samsung SUR40
	Bus info         : usb-0000:00:13.2-1
	Driver version   : 5.13.19
	Capabilities     : 0x95200001
		Video Capture
		Touch Device
		Read/Write
		Streaming
		Extended Pix Format
		Device Capabilities
	Device Caps      : 0x15200001
		Video Capture
		Touch Device
		Read/Write
		Streaming
		Extended Pix Format
Priority: 2
Video input : 0 (In-Cell Sensor: ok)
Format Video Capture:
	Width/Height      : 960/540
	Pixel Format      : 'TU08' (8-bit Unsigned Touch Data)
	Field             : None
	Bytes per Line    : 960
	Size Image        : 518400
	Colorspace        : Raw
	Transfer Function : Default (maps to None)
	YCbCr/HSV Encoding: Default (maps to ITU-R 601)
	Quantization      : Default (maps to Full Range)
	Flags             :
Streaming Parameters Video Capture:
	Capabilities     : timeperframe
	Frames per second: 60.000 (60/1)
	Read buffers     : 3

User Controls

                     brightness 0x00980900 (int)    : min=0 max=255 step=1 default=255 value=255 flags=slider
                       contrast 0x00980901 (int)    : min=0 max=15 step=1 default=10 value=10 flags=slider
                           gain 0x00980913 (int)    : min=0 max=9 step=1 default=8 value=8
         backlight_compensation 0x0098091c (int)    : min=0 max=1 step=1 default=1 value=1

The sur40 kernel module is loaded but I'm worried about "Samsung SUR40: device removed":

May 12 17:56:13 livingplace-sur40 kernel: [ 6640.391458] mc: Linux media interface: v0.10
May 12 17:56:13 livingplace-sur40 kernel: [ 6640.400810] videodev: Linux video capture interface: v2.00
May 12 17:56:13 livingplace-sur40 kernel: [ 6640.417271] input: Samsung SUR40 as /devices/pci0000:00/0000:00:13.2/usb2/2-1/2-1:1.0/input/input14
May 12 17:56:14 livingplace-sur40 kernel: [ 6641.219959] usbcore: registered new interface driver sur40
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (II) config/udev: Adding input device Samsung SUR40 (/dev/input/mouse1)
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (II) No input driver specified, ignoring this device.
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (II) This device may have been added with another device file.
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (II) config/udev: Adding input device Samsung SUR40 (/dev/input/event6)
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (**) Samsung SUR40: Applying InputClass "libinput touchscreen catchall"
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (II) Using input driver 'libinput' for 'Samsung SUR40'
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (II) systemd-logind: got fd for /dev/input/event6 13:70 fd 57 paused 0
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (**) Samsung SUR40: always reports core events
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (**) Option "Device" "/dev/input/event6"
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (**) Option "_source" "server/udev"
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (II) event6  - Samsung SUR40: is tagged by udev as: Touchscreen
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (II) event6  - Samsung SUR40: device is a touch device
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (II) event6  - Samsung SUR40: device removed
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:13.2/usb2/2-1/2-1:1.0/input/input14/event6"
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (II) XINPUT: Adding extended input device "Samsung SUR40" (type: TOUCHSCREEN, id 12)
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (**) Option "AccelerationScheme" "none"
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (**) Samsung SUR40: (accel) selected scheme none/0
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (**) Samsung SUR40: (accel) acceleration factor: 2.000
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (**) Samsung SUR40: (accel) acceleration threshold: 4
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (II) event6  - Samsung SUR40: is tagged by udev as: Touchscreen
May 12 17:56:14 livingplace-sur40 /usr/lib/gdm3/gdm-x-session[735]: (II) event6  - Samsung SUR40: device is a touch device

Might the SUR40 support does not work anymore for a newer kernel?

I am using the OSX with the M1 Chip with the version 14.4.1 (23E224).
For xcode: Version 15.3 (15E204a)

The build is successful, but the application stops running while getting the camera configurations.

int32_t codec = CMVideoFormatDescriptionGetCodecType((CMVideoFormatDescriptionRef)[format formatDescription]);

The Error is: Thread 1: EXC_BREAKPOINT (code=1, subcode=0x104d25124)

I would love to be able to run the newer version of reacTIVision. Has anybody an idea how to fix this?

Since that camera seems to be recommended for this kind of tracking application, how hard would it be to add support through something like https://github.com/inspirit/PS3EYEDriver given that the macam drivers are deprecated and no longer work?

ObjectVersion = 47 in the pbxproj file corresponding to 6.3 .

Hi,

I'd like to use the global shutter raspberry pi camera with reacTIVision.

I just managed to compile reacTIVision on latest bookworm raspberry pi OS. libcamera is able to open the video stream of the GS cam, but reacTIVision says "No camera found!".

Earlier I was trying on an older distro. We have an older raspberry pi IR camera which works well on it as long as the legacy support is enabled. I had to disable legacy support to be able to see the video stream of the GS cam with libcamera, but it was in no case recognized by reacTIVision.

So I guess that in order for it to work, the source code should be altered in some way ...

If anybody has any pointer reagrding where this should happen in the code, and which lib this should rely on, I'd be very grateful.

Thanks !
Joseph