Playstation Move PS3 Move Controller?

"NoxWings" wrote:

"Fredz" wrote:

"NoxWings" wrote:
I'll quote Thomas Perl, the creator of the psmove api, in this subject (from the psmove mail list)

I've tried this (compile without CL Eye support, which is the default anyway IIRC) but the problem lies in OpenCV, it's not able to recognize the PS Move when built in 64 bits. Other apps are able to work with the PS Eye but they're probably compiled in 32 bits.

What do you mean when you say OpenCV is not able to recognize the PS Move when build in 64 bit.

The fact that OpenCV cannot detect the ps eye (because the driver is 32-bit) or the main psmove api cannot detect the psmove connection. I don't see where OpenCV and the psmove itself, the connection or internal data are related aside from the colored bulb tracking.

The thomas quote only says that in theory using other webcam (not the ps-eye) should be doable in a 64-bit build.

Yeah, that's correct - it's just the PS Eye not having a 64-bit driver that prevents using PS Move API in a 64-bit DLL/program.

If you compiled OpenCV 64bit and also PS Move API (kind a pain I found to even get them doing that right) but without CL Eye driver support, and use a regular webcam.

I was hoping to use the Eye because it's cheap and available, and has some nice characteristics compared to a regular webcam (one thing for instance, you can change it to run at 120hz for better tracking).

That's a good idea though. I actually have a regular webcam, but I don't have the build setup handy for doing 64bit OpenCV or PS Move API.

If one of you guys that have OpenCV and PS Move API building in 64bit wouldn't mind uploading the binaries, I'd definitely take a second shot at finishing up my UE4 plugin when I get some time.

Of course, it would only support non-PS Eye cameras.

"NoxWings" wrote:
What do you mean when you say OpenCV is not able to recognize the PS Move when build in 64 bit.

With a 32 bits build OpenCV is able to detect the camera and use it with the C examples, but it's not found and can't be used with a 64 bits build.

My guess is that a 64 bits application can't access a peripheral with a 32 bits driver, but it may be something else (endianness difference only for example).

"NoxWings" wrote:
I don't see where OpenCV and the psmove itself, the connection or internal data are related aside from the colored bulb tracking.

The PS Eye is only used for tracking the orb via OpenCV in the PS Move API, but the init sequence stalls when the camera can't be found. The PS Move is still correctly recognized though via Bluetooth.

"NoxWings" wrote:
The thomas quote only says that in theory using other webcam (not the ps-eye) should be doable in a 64-bit build.

Yes I think so, but there are probably very few webcams that are able to capture at 60 Hz with a 75° field of view.

@Fredz, yeah, whatever generic camera is used, it has to have a 64bit driver for OpenCV 64bit to see it. Same problem as with the PS Eye driver.

That shouldn't be too big a problem, as I know there are cams out there with 64bit drivers.

Suddenly I'm having tons of problems with the magnetometer calibration data :S

I've used the magnetometer_calibration a lot of times and it is always creating the %appdata%/.psmove/<whatevermac>.csv files as it is supposed to do, but for some reason the API cannot detect that my moves are calibrated :(

"NoxWings" wrote:
Suddenly I'm having tons of problems with the magnetometer calibration data :S

I've used the magnetometer_calibration a lot of times and it is always creating the %appdata%/.psmove/<whatevermac>.csv files as it is supposed to do, but for some reason the API cannot detect that my moves are calibrated :(

Lol, connecting the controller with usb solved the issue.

"NoxWings" wrote:

"NoxWings" wrote:
Suddenly I'm having tons of problems with the magnetometer calibration data :S

I've used the magnetometer_calibration a lot of times and it is always creating the %appdata%/.psmove/<whatevermac>.csv files as it is supposed to do, but for some reason the API cannot detect that my moves are calibrated :(

Lol, connecting the controller with usb solved the issue.

Ah right - yeah that's a pecularity of the API I think, you have to have the USB connected to calibrate, but *disconnected* to use positional tracking.

"n00854180t" wrote:

Ah right - yeah that's a pecularity of the API I think, you have to have the USB connected to calibrate, but *disconnected* to use positional tracking.

You can actually do the magnetometer calibration using bluetooth, and the .csv will be added to the %appdata%/.psmove folder but it is not until you connect the move via USB that you get the .calibration file :S

Now that I've got the calibration working I'm having the light bulb dimming problems again and the positional tracking is not working :( :( . So I guess this is not about having the psmoveapi 3.0 precompiled library dll as I was suspecting. I'll end up compiling the latest psmove api source to be sure this is not the problem once for all (I hate compiling on windows... :roll: )

So I've connected the Sony Bloggie 3D on my computer as a webcam and launched the 64 bits test_tracker from the PS Move API :




It worked, but only once. At every other attempt there was either a crash of the application or it ran without blinking the orb, so without tracking.

At least it shows that a webcam with a 64 bits driver can work with the PS Move API in 64 bits, but it doesn't seem very reliable. No idea whose fault is it.

"Fredz" wrote:
So I've connected the Sony Bloggie 3D on my computer as a webcam and launched the 64 bits test_tracker from the PS Move API :




It worked, but only once. At every other attempt there was either a crash of the application or it ran without blinking the orb, so without tracking.

At least it shows that a webcam with a 64 bits driver can work with the PS Move API in 64 bits, but it doesn't seem very reliable. No idea whose fault is it.

Hey good job! At least this is some progress. Have you noticed that neither exposure gain and other camera parameters seem to be automatically tweaked? Ps-eye images look way darker after the exposure is set.

Yes the PS Eye is always almost dark when I use it, I guess the PS Move API is modifying the parameters to get the best results but doesn't know how to do it for other webcams. Perhaps the change of camera is the reason why it doesn't work anymore on my machine (32 bits and 64 bits).

EDIT: just retried today and now it works again correctly with the PS Eye and the 32 bits application.