Record PS3 Eye DirectShow capture path

This commit is contained in:
Meta Vens 2026-05-18 15:26:30 +01:00
commit 53ccd079ca
10 changed files with 4363 additions and 20 deletions

View file

@ -71,14 +71,15 @@ Observed video access:
- `dshow:0` / `msmf:0`: LeapUVC raw stereo IR image, visible as green/magenta packed output.
- `dshow:1` / `msmf:1`: Razer Kiyo-class RGB camera.
- `dshow:2`: second Razer Kiyo-class RGB camera, likely Kiyo Pro.
- PS3 Eye video interfaces are attached but not usable yet. Both `USB\VID_1415&PID_2000&MI_00` devices report Windows problem code `28`, meaning the video-side driver is missing. Their audio interfaces are working through generic USB audio.
- `dshow:2` / `msmf:2`: second Razer Kiyo-class RGB camera, likely Kiyo Pro.
- `dshow:3`: first PS3 Eye through PS3 Eye Universal Driver / PS3EyeDirectShow.
- `dshow:4`: second PS3 Eye through PS3 Eye Universal Driver / PS3EyeDirectShow.
Mode probe notes:
- `msmf:0` LeapUVC accepts a `320x240x120` request and reports about 115 fps, with rough OpenCV measured capture around 52 fps in the first short probe. Treat that as "tracking mode is plausible," not calibrated throughput.
- Kiyo RGB devices produce snapshots, but initial isolated mode probes against Kiyo indices timed out. Do not trust FPS configuration for Kiyos until a backend-specific capture path is chosen.
- PS3 Eye tracking modes cannot be tested until the open driver is installed for `MI_00`.
- PS3 Eye default DirectShow capture works at `640x480` near 30 fps. High-FPS tracking modes are not proven yet; mode probes against the DirectShow filter can hang or collide with another open handle, so test them sequentially.
Observed audio access over WASAPI at 48 kHz:
@ -132,7 +133,7 @@ Do not install the driver over `MI_01`; that is the working generic USB audio in
CL Eye / Code Laboratories is historical reference material only. Do not make this repo depend on a paid, stale, or redistributed proprietary driver. Reverse engineering should stay inside interoperability research boundaries; the live machine should prefer the open driver.
Current post-install status:
opentrack/libusb status:
- Both PS3 Eye `MI_00` video interfaces are now bound as `libusb-win32 devices` and show `OK` in PnP.
- `E:\Tools\opentrack\modules\ps3eye-mode-test.exe` sees the cameras well enough to enumerate good modes up to `320x240@205Hz` and `640x480@83Hz`.
@ -156,11 +157,41 @@ Fallback results so far:
- `WinUSB` with both live `MI_00` instances: opentrack mode test still reports all modes `GOOD`, but one camera open reports `Access is denied` and frame streaming still repeats `payload error, data[1]=78/79`.
- `libusb-win32`, `libusbK`, and `WinUSB` have all failed frame reads through opentrack on this machine.
Next escalation is no longer "try the other Zadig driver." It is either:
That path is currently rejected for frame capture on this machine. Keep it as a mode-enumeration reference, not the live capture path.
- test opentrack with exactly one PS3 Eye direct to motherboard and every other high-bandwidth camera unplugged
- test a different PS3 Eye backend/library, such as PS3EYEDriver/PSMoveService-style access
- abandon PS3 Eye video for v1 and use LeapUVC plus Kiyos for initial calibration/tracking while preserving the PS3 Eye driver notes as a rejected path until a cleaner backend is found
Working DirectShow path:
- Installed AllanCat `PS3 Eye Universal Driver` / `PS3EyeDirectShow` from `PS3EyeInstaller1.1.msi`.
- Installed source filters:
- `C:\Program Files\PS3 Eye Universal Driver\PS3EyeSourceFilter64.dll`
- `C:\Program Files (x86)\PS3 Eye Universal Driver\PS3EyeSourceFilter.dll`
- The filter's camera count is controlled by `ChangeCameraNumber.bat`, which unregisters/registers the source filter with `/i:<count>`.
- With two cameras connected, register both filters for two cameras from an elevated shell:
```powershell
$dll32 = 'C:\Program Files (x86)\PS3 Eye Universal Driver\PS3EyeSourceFilter.dll'
$dll64 = 'C:\Program Files\PS3 Eye Universal Driver\PS3EyeSourceFilter64.dll'
Start-Process regsvr32.exe -ArgumentList "/n /i:2 `"$dll32`"" -Verb RunAs -Wait
Start-Process regsvr32.exe -ArgumentList "/n /i:2 `"$dll64`"" -Verb RunAs -Wait
```
After registration, this machine exposes:
- `dshow:3`: PS3 Eye, default `640x480`, about 30 fps.
- `dshow:4`: PS3 Eye, default `640x480`, about 30 fps.
- Simultaneous three-second capture from indices 3 and 4 produced 90 frames each, about 29.8-30.0 fps.
Known caveats:
- OpenCV `mode-probe` calls that set width/height/fps may time out against the PS3EyeDirectShow filter.
- Parallel probes can race the same libusb/backend state and produce `Access is denied`; test PS3 Eye mode changes one handle at a time.
- High-rate modes such as `320x240@60` or `320x240@120` remain unproven through the DirectShow path.
Next escalation is no longer "find any video path." It is:
- capture ChArUco intrinsics for `dshow:3` and `dshow:4` at the working default mode
- test PS3 Eye high-rate mode negotiation sequentially, with no other process holding either Eye
- keep Leap/Kiyos/PS3 Eyes split across USB root paths where possible
Also test with one PS3 Eye unplugged and each camera connected directly to a motherboard USB 2.0/3.x port, not through a hub. A libusb issue report shows PS3 Eye/opentrack access can break when certain USB-C hubs are present, even when the camera itself is not plugged into that hub.

File diff suppressed because one or more lines are too long

View file

@ -0,0 +1,15 @@
PS3EYE Driver
========
Some driver like routines to connect and work with Sony PS3 EYE Camera.
The driver is using [libusb](https://github.com/libusbx/libusbx) to handle USB communications.
Most of the code was ported from Linux kernel source.
You can find example code for [Cinder](https://github.com/cinder/Cinder) and [openFrameworks](https://github.com/openframeworks/openFrameworks) in corresponding folders.
---
![alt text](https://raw.github.com/inspirit/PS3EYEDriver/master/shot1.png "PS3EYE Running with Cinder")
![alt text](https://raw.github.com/inspirit/PS3EYEDriver/master/shot2.png "PS3EYE Running with Cinder")

View file

@ -0,0 +1,194 @@
<!DOCTYPE html>
<html lang="en" data-content_root="./">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Tracking and Camera &#8212; PS Move API 4.0.12 documentation</title>
<link rel="stylesheet" type="text/css" href="_static/pygments.css?v=03e43079" />
<link rel="stylesheet" type="text/css" href="_static/classic.css?v=2bf1fcf8" />
<script src="_static/documentation_options.js?v=2b25b4f2"></script>
<script src="_static/doctools.js?v=fd6eb6e6"></script>
<script src="_static/sphinx_highlight.js?v=6ffebe34"></script>
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="next" title="Networking (Move Daemon)" href="moved.html" />
<link rel="prev" title="Pairing the Controller to your PC" href="pairing.html" />
<script async type="text/javascript" src="/_/static/javascript/readthedocs-addons.js"></script><meta name="readthedocs-project-slug" content="psmoveapi" /><meta name="readthedocs-version-slug" content="latest" /><meta name="readthedocs-resolver-filename" content="/camera.html" /><meta name="readthedocs-http-status" content="200" /></head><body>
<div class="related" role="navigation" aria-label="Related">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
accesskey="I">index</a></li>
<li class="right" >
<a href="moved.html" title="Networking (Move Daemon)"
accesskey="N">next</a> |</li>
<li class="right" >
<a href="pairing.html" title="Pairing the Controller to your PC"
accesskey="P">previous</a> |</li>
<li class="nav-item nav-item-0"><a href="index.html">PS Move API 4.0.12 documentation</a> &#187;</li>
<li class="nav-item nav-item-this"><a href="">Tracking and Camera</a></li>
</ul>
</div>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body" role="main">
<section id="tracking-and-camera">
<h1>Tracking and Camera<a class="headerlink" href="#tracking-and-camera" title="Link to this heading"></a></h1>
<p>This page contains information about the camera integration, especially
as it relates to tracking and the different variants for different OSes.</p>
<section id="ps3-camera">
<h2>PS3 Camera<a class="headerlink" href="#ps3-camera" title="Link to this heading"></a></h2>
<p>This camera is always supported on Linux, and supported on macOS and Windows
when using the PS3EYEDriver camera control driver.</p>
<p>On Linux, the kernel includes built-in support for the camera using the
<code class="docutils literal notranslate"><span class="pre">ov534</span></code> driver, so the V4L2 camera control driver also support the PS3 Eye.</p>
<p>The camera needs a USB 2.0 port.</p>
<p>On Windows, you need to install <a class="reference external" href="https://zadig.akeo.ie/">Zadig</a> (WinUSB driver) for the
“USBCamera-B4.09.24.1” (or similar) device so that the PS3EYEDriver
can access the camera using <code class="docutils literal notranslate"><span class="pre">libusb</span></code>. This has been tested with the
“WinUSB (v6.1.7600.16385)” driver and Zadig 2.7.</p>
<ul class="simple">
<li><p>Tested models: SLEH-00448</p></li>
<li><p>No firmware upload necessary</p></li>
</ul>
<p>Supported resolutions:</p>
<ul class="simple">
<li><p><strong>640x480 &#64; 60 Hz</strong> (default)</p></li>
<li><p>320x240 &#64; 187 Hz</p></li>
</ul>
</section>
<section id="ps4-camera">
<h2>PS4 Camera<a class="headerlink" href="#ps4-camera" title="Link to this heading"></a></h2>
<p>This camera is currently supported on Linux when using the V4L2 camera control
driver, and macOS when using the AVFoundation camera control driver.</p>
<p>You need to upload a firmware binary blob using the <code class="docutils literal notranslate"><span class="pre">psmove</span> <span class="pre">camera-firmware</span></code> command.</p>
<p>The camera needs a USB 3.0 port.</p>
<p>If you have a PSVR kit, you can order the <a class="reference external" href="https://camera-adaptor.support.playstation.com/">Camera Adaptor</a> (to convert
PS4 AUX to USB 3.0) from Sony for free. You only need to enter the serial
number of your PSVR kit during the ordering process, no need for a PS5.
If you only have the camera but no PSVR, you can look to buy the
adaptor online. The official Sony one is CFI-ZAA1.</p>
<p>The official PSVR camera adaptor for PS5 (CFI-ZAA1) will be detected
automatically. If you are using a homemade PS4 AUX-to-USB adapter, use
<code class="docutils literal notranslate"><span class="pre">psmove</span> <span class="pre">camera-firmware</span> <span class="pre">--force-ps4</span></code> to detect any OV580 in boot mode
as PS4 (otherwise it’s assumed that the camera is a PS5 camera, as there
is no way yet to distinguish the PS4 and PS5 cameras from the USB
descriptor in boot mode only, which is probably why the CFI-ZAA1 appears
as USB parent device during enumeration).</p>
<p>After the firmware upload the camera is supported using
the <code class="docutils literal notranslate"><span class="pre">uvcvideo</span></code> kernel driver in OpenCV/V4L2 (Linux)
and <code class="docutils literal notranslate"><span class="pre">UVCService</span></code> on OpenCV/AVFoundation (macOS).</p>
<ul class="simple">
<li><p>Tested models: CUH-ZEY2 (“round model v2”)</p></li>
<li><p>Tested firmware SHA-1: <code class="docutils literal notranslate"><span class="pre">fe86162309518a0ffe267075a2fcf728c5856b3e</span></code></p></li>
<li><p>Firmware search path: <code class="docutils literal notranslate"><span class="pre">/etc/psmoveapi/camera-firmware-ps4.bin</span></code>, <code class="docutils literal notranslate"><span class="pre">$HOME/.psmoveapi/camera-firmware-ps4.bin</span></code></p></li>
</ul>
<p>Supported resolutions:</p>
<ul class="simple">
<li><p><strong>1280x800 &#64; 60 Hz</strong> (default)</p></li>
<li><p>640x400 &#64; 120 Hz</p></li>
<li><p>320x192 &#64; 240 Hz</p></li>
</ul>
</section>
<section id="ps5-camera">
<h2>PS5 Camera<a class="headerlink" href="#ps5-camera" title="Link to this heading"></a></h2>
<p>This camera is currently supported on Linux when using the V4L2 camera control
driver, and macOS when using the AVFoundation camera control driver.</p>
<p>You need to upload a firmware binary blob using the <code class="docutils literal notranslate"><span class="pre">psmove</span> <span class="pre">camera-firmware</span></code> command.</p>
<p>The camera needs a USB 3.0 port.</p>
<p>After the firmware upload the camera is supported using
the <code class="docutils literal notranslate"><span class="pre">uvcvideo</span></code> kernel driver in OpenCV/V4L2 (Linux)
and <code class="docutils literal notranslate"><span class="pre">UVCService</span></code> on OpenCV/AVFoundation (macOS).</p>
<ul class="simple">
<li><p>Tested models: CFI-ZEY1</p></li>
<li><p>Tested firmware SHA-1: <code class="docutils literal notranslate"><span class="pre">0fa4da31a12b662a9a80abc8b84932770df8f7e1</span></code></p></li>
<li><p>Firmware search path: <code class="docutils literal notranslate"><span class="pre">/etc/psmoveapi/camera-firmware-ps5.bin</span></code>, <code class="docutils literal notranslate"><span class="pre">$HOME/.psmoveapi/camera-firmware-ps5.bin</span></code></p></li>
</ul>
<p>Supported resolutions:</p>
<ul class="simple">
<li><p>1920x1080 &#64; 30 Hz</p></li>
<li><p><strong>1280x800 &#64; 60 Hz</strong> (default)</p></li>
<li><p>960x520 &#64; 60 Hz</p></li>
<li><p>640x376 &#64; 120 Hz</p></li>
<li><p>448x256 &#64; 120 Hz</p></li>
<li><p>320x184 &#64; 240 Hz</p></li>
</ul>
</section>
</section>
<div class="clearer"></div>
</div>
</div>
</div>
<div class="sphinxsidebar" role="navigation" aria-label="Main">
<div class="sphinxsidebarwrapper">
<h3><a href="index.html">Table of Contents</a></h3>
<ul class="current">
<li class="toctree-l1"><a class="reference internal" href="build.html">Building from Source</a></li>
<li class="toctree-l1"><a class="reference internal" href="pairing.html">Pairing</a></li>
<li class="toctree-l1 current"><a class="current reference internal" href="#">Camera</a><ul>
<li class="toctree-l2"><a class="reference internal" href="#ps3-camera">PS3 Camera</a></li>
<li class="toctree-l2"><a class="reference internal" href="#ps4-camera">PS4 Camera</a></li>
<li class="toctree-l2"><a class="reference internal" href="#ps5-camera">PS5 Camera</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="moved.html">Network (Move Daemon)</a></li>
<li class="toctree-l1"><a class="reference internal" href="config.html">Configuration</a></li>
<li class="toctree-l1"><a class="reference internal" href="navcon.html">Navigation Controller</a></li>
</ul>
<div>
<h4>Previous topic</h4>
<p class="topless"><a href="pairing.html"
title="previous chapter">Pairing the Controller to your PC</a></p>
</div>
<div>
<h4>Next topic</h4>
<p class="topless"><a href="moved.html"
title="next chapter">Networking (Move Daemon)</a></p>
</div>
<search id="searchbox" style="display: none" role="search">
<h3 id="searchlabel">Quick search</h3>
<div class="searchformwrapper">
<form class="search" action="search.html" method="get">
<input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
<input type="submit" value="Go" />
</form>
</div>
</search>
<script>document.getElementById('searchbox').style.display = "block"</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="related" role="navigation" aria-label="Related">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
>index</a></li>
<li class="right" >
<a href="moved.html" title="Networking (Move Daemon)"
>next</a> |</li>
<li class="right" >
<a href="pairing.html" title="Pairing the Controller to your PC"
>previous</a> |</li>
<li class="nav-item nav-item-0"><a href="index.html">PS Move API 4.0.12 documentation</a> &#187;</li>
<li class="nav-item nav-item-this"><a href="">Tracking and Camera</a></li>
</ul>
</div>
<div class="footer" role="contentinfo">
&#169; Copyright 2020, Thomas Perl.
Created using <a href="https://www.sphinx-doc.org/">Sphinx</a> 9.1.0.
</div>
</body>
</html>

File diff suppressed because one or more lines are too long

View file

@ -0,0 +1,325 @@
<html>
<head>
<title> PSEye Software Setup (Windows) - psmoveservice/PSMoveService GitHub Wiki </title>
<style>
#main {
max-width: 38rem;
margin: auto;
overflow-wrap: break-word;
min-width: 0;
background-color: white;
}
body {
background-image: url('/callToAction.svg');
}
img {
max-width: 100%;
height: auto;
}
#header_button {
position: sticky;
top: 0;
padding: 10px;
border-style: ridge;
border-color: lightgrey;
border-width: thin;
color: red;
font-weight: bold;
background-color: honeydew;
font-size: large;
}
#header_button p {
margin-bottom: 0;
margin-top: 10px;
}
#header_info {
padding: 10px;
border-style: ridge;
border-color: lightgrey;
border-width: thin;
color: red;
font-weight: bold;
background-color: honeydew;
font-size: large;
}
#content,
#index {
padding-left: 10px;
padding-right: 10px;
}
#footer_info {
position: sticky;
bottom: 0;
padding: 10px;
border-style: ridge;
border-color: lightgrey;
border-width: thin;
color: red;
font-weight: bold;
background-color: honeydew;
}
#footer_info .blocks {
background: black;
color: white;
/* outline: 1px solid blue; */
padding: .1em .2em;
}
/* Hide useless-parts of transcluded HTML */
.width-full.input-group {
display: none;
}
h5:nth-last-child(2) {
display: none;
}
.Box-row.wiki-more-pages-link {
display: none;
}
.filter-bar {
display: none;
}
.Box-title>.octicon {
display: none;
}
.anchor {
display: none;
}
pre {
overflow: auto;
}
#main {
word-wrap: break-word;
}
.Counter {
background-color: lightgray;
border-radius: 20px;
padding: 0 10px;
}
table {
max-width: 100%;
overflow: auto;
width: 100%;
display: block;
}
.js-wiki-sidebar-toc-toggle-chevron-button {
display: none;
}
a.visit_url_original {
white-space: nowrap;
overflow: hidden;
text-overflow: ellipsis;
line-height: 1.2em; /* adjust as needed */
max-height: 1.2em; /* should match line-height */
display: block;
}
/* White background for span */
/* Rounded corners */
/* Black border */
.visit_url_pillbar {
background-color: white;
border-radius: 10px;
padding: 5px;
margin: 5px;
display: block;
border: 1px solid black;
white-space: nowrap;
overflow: hidden;
text-overflow: ellipsis;
}
/* Broken Images */
img:before {
content: "⚠️ MISSING OR BROKEN IMAGE RENDERING ERROR: PLEASE VIEW ORIGINAL PAGE ON GITHUB.COM ⚠️";
display: block;
margin-bottom: 10px;
}
@font-face {
font-family: "color-emoji";
src: local("Apple Color Emoji"),
local("Segoe UI Emoji"),
local("Segoe UI Symbol"),
local("Noto Color Emoji");
}
.emoji {
font-family: "color-emoji";
}
table,
th,
td {
border: 1px solid black;
}
.visit_url_link {
font-size: xx-large;
}
.why_exist {
position: relative;
text-align: center;
/* italics */
font-style: italic;
}
</style>
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- Not used, did not want to risk non-indexing. -->
<!-- <meta property="og:url" content="https://github.com/psmoveservice/PSMoveService/wiki/PSEye-Software-Setup-%28Windows%29"> -->
<!-- Did not want to risk contaminating content to be indexed. -->
<!-- <meta property="og:description" content="not used"> -->
<meta property="og:type" content="website">
<meta property="og:title" content="PSEye Software Setup (Windows) - psmoveservice/PSMoveService GitHub Wiki">
</head>
<body>
<div id="main">
<nav id="header_button">
<p>Content mirrored for search engine indexing from:</p>
<div>
<span class="visit_url_pillbar">
<a href="https://github.com/psmoveservice/PSMoveService/wiki/PSEye-Software-Setup-%28Windows%29" class="visit_url_original">https://github.com/psmoveservice/PSMoveService/wiki/PSEye-Software-Setup-%28Windows%29</a>
</span>
</div>
<div class="why_exist">
<a href="/">Why does this service exist?</a>
</div>
</nav>
<aside id="header_info">
<!-- Last Modified Date added around here from redirect checker-->
<p>📅 Last Modified: Thu, 08 Aug 2019 14:42:55 GMT</p></aside>
<article id="content">
<h1>PSEye Software Setup (Windows) - psmoveservice/PSMoveService GitHub Wiki</h1>
<div id="mirrored"> <h1><a href="#overview" aria-hidden="true" class="anchor" id="overview"></a>Overview</h1>
<p>There are many different ways to get the PS Eye working on a Windows PC. This is pretty confusing, so expect to be confused.</p>
<table>
<thead>
<tr>
<th>Driver</th>
<th>Cost</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>IPISoft PS3EYEDriver</strong></td>
<td>Free</td>
<td>Supports multiple cameras. Applications like ex. skype cant see the cameras. The most easy PSEYE driver setup !</td>
</tr>
<tr>
<td><strong>PS3EYEDriver</strong></td>
<td>Free</td>
<td>Wraps libusb. Open source and continues to be worked on so sometimes can be flaky. Supports as many cameras as there is bandwidth for. Instructions are below.</td>
</tr>
<tr>
<td><strong>CL Eye Platform Driver</strong></td>
<td>$2.99 USD</td>
<td>Exposes the camera as a DirectShow object so can be used easily by this and other software (e.g. Skype, I think, no guarantees). Only supports one camera.</td>
</tr>
<tr>
<td><strong>CL Eye Platform SDK</strong></td>
<td>$4.99 USD</td>
<td>Supports multiple cameras. Only works if you use your own (non-redistributable, developer version) CLEyeMulticam.dll. Delete the dll that comes with PSMoveService to use the DLL that gets installed with the SDK.</td>
</tr>
<tr>
<td><strong>CL Eye redistributable + registered camera</strong></td>
<td>$?? USD * n_cameras</td>
<td>Apparently, after you register your cameras, the redistributable CLEyeMulticam.dll that we supply works. I don't think I ever correctly registered my camera so I don't know if it actually works.</td>
</tr>
<tr>
<td><strong>PS3EyeDirectShow</strong></td>
<td>Free</td>
<td>Exposes the camera as a DirectShow object so can be used easily by this and other software (e.g. Skype, I think, no guarantees). <a href="https://github.com/jkevin/PS3EyeDirectShow" rel="nofollow ugc">https://github.com/jkevin/PS3EyeDirectShow</a></td>
</tr>
</tbody>
</table>
<h1><a href="#setup-the-camera-drivers" aria-hidden="true" class="anchor" id="setup-the-camera-drivers"></a>Setup the camera drivers</h1>
<h2><a href="#option-a-ipisoft-pseye-driver-installation" aria-hidden="true" class="anchor" id="option-a-ipisoft-pseye-driver-installation"></a>Option A) IPIsoft PSEYE Driver Installation</h2>
<p><strong>NOTE: If you have already install libusb based drivers, please uninstall those drivers first in Windows device manager</strong></p>
<p>This installation option is very simple. Just download the driver for your Windows OS architecture and all PSEYE Cameras should be recognized. IPISoft is software for Motion Capture Full Body system. This PS3Eye driver was not originally intended to be used with PSMoveService (opensource software), though it does appear to work. Therefore, please do not spam the support of IPISoft with questions about this driver. Use at your own risk.</p>
<p>Downloads:</p>
<p>64-bit OS:</p>
<p><a href="http://files.ipisoft.com/drivers/PlayStation3_Eye_iPi-x64.msi" rel="nofollow ugc">http://files.ipisoft.com/drivers/PlayStation3_Eye_iPi-x64.msi</a></p>
<p>32-bit OS:</p>
<p><a href="http://files.ipisoft.com/drivers/PlayStation3_Eye_iPi-x86.msi" rel="nofollow ugc">http://files.ipisoft.com/drivers/PlayStation3_Eye_iPi-x86.msi</a></p>
<p>Result in 'Device Manager', tested successfully in Windows 10 x64:</p>
<p><img src="http://i.imgur.com/4Kdyp96.jpg" alt="" /></p>
<p>Source info:
<a href="http://docs.ipisoft.com/User_Guide_for_Multiple_PS_Eye_Cameras_Configuration" rel="nofollow ugc">http://docs.ipisoft.com/User_Guide_for_Multiple_PS_Eye_Cameras_Configuration</a></p>
<h2><a href="#option-b-libusb-pseye-driver-installation" aria-hidden="true" class="anchor" id="option-b-libusb-pseye-driver-installation"></a>Option B) Libusb PSEYE Driver Installation</h2>
<p>The instructions below apply to our customized version of the <a href="https://github.com/HipsterSloth/PS3EYEDriver/tree/psmoveservice" rel="nofollow ugc">PS3EYEDriver wrapper</a> around <a href="http://libusb.info/" rel="nofollow ugc">libusb</a>.</p>
<h3><a href="#libusb-driver-pre-install" aria-hidden="true" class="anchor" id="libusb-driver-pre-install"></a>Libusb Driver Pre-Install</h3>
<p>Download UsbDeview from <a href="http://www.nirsoft.net/utils/usbdeview-x64.zip" rel="nofollow ugc">Nirsoft.net</a>. This is a handy utility for showing all connected usb devices attached to your system and what drivers they are running. Once downloaded, launch <code>usbdeview.exe</code>.</p>
<ol>
<li>After you have plugged in the PS Eye camera you should see entries for the camera and the microphone of the ps3 eye.
<ul>
<li>The cameras take a lot of USB bandwidth. This is especially a concern if using more than one camera. We have some tips <a href="https://github.com/cboulay/PSMoveService/wiki/Troubleshooting-(Windows)#general-weird-camera-behavior-clean-camera-driver-reinstall" rel="nofollow ugc">here</a> on how to manage your camera-connections. Also see <a href="https://www.oculus.com/blog/oculus-roomscale-balancing-bandwidth-on-usb/" rel="nofollow ugc">what Oculus has to say</a> on the matter.</li>
</ul>
</li>
<li>Under the &quot;service name&quot; column for the camera you should see &quot;usbccgp&quot; for the camera device and &quot;usbaudio&quot; for the audio device.
a. If you don't see &quot;usbccgp&quot; for the camera, right-click on the entry with the purple dot and select &quot;uninstall selected devices&quot;, after which, unplug the ps3eye camera, and then plug it back in.</li>
<li>Close usbdeview</li>
</ol>
<p><a href="/m/psmoveservice/PSMoveService/wiki/images/USBCameraPreInstall.jpg">images/USBCameraPreInstall.jpg</a></p>
<h3><a href="#libusb-driver-install" aria-hidden="true" class="anchor" id="libusb-driver-install"></a>Libusb Driver Install</h3>
<p>Download the Zadig usb utility from <a href="http://zadig.akeo.ie/" rel="nofollow ugc">here</a>. This is another handy usb utility for installing custom usb drivers. In our case we're going to use it to install the libusb driver over the top of the default Windows driver for the PS Eye camera. Once downloaded, Launch <code>zadig_2.2.exe</code>.</p>
<ol>
<li>From the options menu launch select &quot;List all devices&quot;</li>
<li>From the device list drop down select &quot;USB Camera-B4.09.24.1 (Interface 0)&quot;</li>
<li>From the driver drop down select &quot;libusb-win32 (v 1.2.6.0)&quot;</li>
<li>Click the Install Driver option</li>
<li>There should be a few second delay and then it should say &quot;driver installed successfully&quot;</li>
</ol>
<p>Note: Computer reboot might be require to complete installation.
Note 2: Having an error message from the timeout expiration might not mean the driver was not install properly.</p>
<p><a href="/m/psmoveservice/PSMoveService/wiki/images/ZadigInstall.jpg">images/ZadigInstall.jpg</a></p>
<h3><a href="#libusb-driver-post-install" aria-hidden="true" class="anchor" id="libusb-driver-post-install"></a>Libusb Driver Post-Install</h3>
<ol>
<li>Launch <code>usbdeview.exe</code> again.</li>
<li>You should now see an entry in the &quot;service name&quot; column for the PS3Eye camera that says &quot;libusb0&quot;
a. If you don't see &quot;libusb0&quot; for the camera, right-click on the entry with the purple dot and select &quot;uninstall selected devices&quot;, then unplug the ps3eye camera, then plug it back in, and try reinstalling the lib usb driver.</li>
<li>Close usbdeview</li>
</ol>
<p><a href="/m/psmoveservice/PSMoveService/wiki/images/USBCameraPostInstall.jpg">images/USBCameraPostInstall.jpg</a></p>
<h2><a href="#testing" aria-hidden="true" class="anchor" id="testing"></a>Testing</h2>
<p>Now that the camera drivers are installed you should be able to run <code>test_camera.exe</code> and see a video feed (640x480/60Hz) for each camera you have plugged in (up to 3 cameras max).</p>
<p>If <code>test_camera.exe</code> closes immediately, or the video feed is stuck on a solid color, don't panic. This is sadly a common occurrence, especially on a initial setup. It's quite likely that you have to <a href="https://github.com/cboulay/PSMoveService/wiki/Troubleshooting-%28Windows%29#cameras-arent-showing-up-using-libusb-driver" rel="nofollow ugc">do some driver shenanigans in zadig</a> to make this work.</p>
<p>If that worked the first time, please take a moment to celebrate your good fortune. Then launch <code>PSMoveService.exe</code>. You should see messages about any attached cameras getting opened in the log window.</p>
<p>Then launch the <code>PSMoveConfigTool.exe</code> and open the &quot;Tracker Settings&quot; and &quot;Test Video Feed&quot; sub menu. If your camera is set up properly then this should show you the images from the camera at 640x480/60Hz. While you have the video feed up, it's also a good time to grab the move controller and see if the frame encompasses enough of your intended interaction area with the controller.</p>
<p>Also when the PS Eye camera is recording you should see the red LED turn on. Sometimes this light will get stuck on in the event of an application crash. Most of the time it won't matter, but you can reset the camera simply by unplugging it and then plugging it back in again.</p>
<p><a href="/m/psmoveservice/PSMoveService/wiki/images/Recording.jpg">images/Recording.jpg</a></p>
<h1><a href="#proceed-to-the-next-step" aria-hidden="true" class="anchor" id="proceed-to-the-next-step"></a>Proceed to the next step</h1>
<p><a href="/m/psmoveservice/PSMoveService/wiki/PSMove-Bluetooth-Pairing">PSMove-Bluetooth-Pairing</a></p>
</div>
</article>
<nav id="index">
<a href="/m/psmoveservice/PSMoveService/wiki_index">🗂️ Page Index for this GitHub Wiki</a>
</nav>
</div>
<script defer src="https://static.cloudflareinsights.com/beacon.min.js/v833ccba57c9e4d2798f2e76cebdd09a11778172276447" integrity="sha512-57MDmcccJXYtNnH+ZiBwzC4jb2rvgVCEokYN+L/nLlmO8rfYT/gIpW2A569iJ/3b+0UEasghjuZH/ma3wIs/EQ==" data-cf-beacon='{"version":"2024.11.0","token":"4645764ca8384bfc86034b71f1dafd76","r":1,"server_timing":{"name":{"cfCacheStatus":true,"cfEdge":true,"cfExtPri":true,"cfL4":true,"cfOrigin":true,"cfSpeedBrain":true},"location_startswith":null}}' crossorigin="anonymous"></script>
</body>
</html>

View file

@ -0,0 +1,279 @@
<html>
<head>
<title> Setting up the PlayStation 3 Eye Camera - Timocop/PSMoveServiceEx GitHub Wiki </title>
<style>
#main {
max-width: 38rem;
margin: auto;
overflow-wrap: break-word;
min-width: 0;
background-color: white;
}
body {
background-image: url('/callToAction.svg');
}
img {
max-width: 100%;
height: auto;
}
#header_button {
position: sticky;
top: 0;
padding: 10px;
border-style: ridge;
border-color: lightgrey;
border-width: thin;
color: red;
font-weight: bold;
background-color: honeydew;
font-size: large;
}
#header_button p {
margin-bottom: 0;
margin-top: 10px;
}
#header_info {
padding: 10px;
border-style: ridge;
border-color: lightgrey;
border-width: thin;
color: red;
font-weight: bold;
background-color: honeydew;
font-size: large;
}
#content,
#index {
padding-left: 10px;
padding-right: 10px;
}
#footer_info {
position: sticky;
bottom: 0;
padding: 10px;
border-style: ridge;
border-color: lightgrey;
border-width: thin;
color: red;
font-weight: bold;
background-color: honeydew;
}
#footer_info .blocks {
background: black;
color: white;
/* outline: 1px solid blue; */
padding: .1em .2em;
}
/* Hide useless-parts of transcluded HTML */
.width-full.input-group {
display: none;
}
h5:nth-last-child(2) {
display: none;
}
.Box-row.wiki-more-pages-link {
display: none;
}
.filter-bar {
display: none;
}
.Box-title>.octicon {
display: none;
}
.anchor {
display: none;
}
pre {
overflow: auto;
}
#main {
word-wrap: break-word;
}
.Counter {
background-color: lightgray;
border-radius: 20px;
padding: 0 10px;
}
table {
max-width: 100%;
overflow: auto;
width: 100%;
display: block;
}
.js-wiki-sidebar-toc-toggle-chevron-button {
display: none;
}
a.visit_url_original {
white-space: nowrap;
overflow: hidden;
text-overflow: ellipsis;
line-height: 1.2em; /* adjust as needed */
max-height: 1.2em; /* should match line-height */
display: block;
}
/* White background for span */
/* Rounded corners */
/* Black border */
.visit_url_pillbar {
background-color: white;
border-radius: 10px;
padding: 5px;
margin: 5px;
display: block;
border: 1px solid black;
white-space: nowrap;
overflow: hidden;
text-overflow: ellipsis;
}
/* Broken Images */
img:before {
content: "⚠️ MISSING OR BROKEN IMAGE RENDERING ERROR: PLEASE VIEW ORIGINAL PAGE ON GITHUB.COM ⚠️";
display: block;
margin-bottom: 10px;
}
@font-face {
font-family: "color-emoji";
src: local("Apple Color Emoji"),
local("Segoe UI Emoji"),
local("Segoe UI Symbol"),
local("Noto Color Emoji");
}
.emoji {
font-family: "color-emoji";
}
table,
th,
td {
border: 1px solid black;
}
.visit_url_link {
font-size: xx-large;
}
.why_exist {
position: relative;
text-align: center;
/* italics */
font-style: italic;
}
</style>
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- Not used, did not want to risk non-indexing. -->
<!-- <meta property="og:url" content="https://github.com/Timocop/PSMoveServiceEx/wiki/Setting-up-the-PlayStation-3-Eye-Camera"> -->
<!-- Did not want to risk contaminating content to be indexed. -->
<!-- <meta property="og:description" content="not used"> -->
<meta property="og:type" content="website">
<meta property="og:title" content="Setting up the PlayStation 3 Eye Camera - Timocop/PSMoveServiceEx GitHub Wiki">
</head>
<body>
<div id="main">
<nav id="header_button">
<p>Content mirrored for search engine indexing from:</p>
<div>
<span class="visit_url_pillbar">
<a href="https://github.com/Timocop/PSMoveServiceEx/wiki/Setting-up-the-PlayStation-3-Eye-Camera" class="visit_url_original">https://github.com/Timocop/PSMoveServiceEx/wiki/Setting-up-the-PlayStation-3-Eye-Camera</a>
</span>
</div>
<div class="why_exist">
<a href="/">Why does this service exist?</a>
</div>
</nav>
<aside id="header_info">
<!-- Last Modified Date added around here from redirect checker-->
<p>📅 Last Modified: Thu, 07 May 2026 22:16:43 GMT</p></aside>
<article id="content">
<h1>Setting up the PlayStation 3 Eye Camera - Timocop/PSMoveServiceEx GitHub Wiki</h1>
<div id="mirrored"> <blockquote>
<p>[!WARNING]
Before connecting or acquiring PlayStation 3 Eye cameras, first take a look at <a href="https://github.com/Timocop/PSMoveServiceEx/wiki/Compatible-Devices" rel="nofollow ugc">Compatible Devices</a> and <a href="https://github.com/Timocop/PSMoveServiceEx/wiki/Hardware-Requirements" rel="nofollow ugc">Hardware Requirements</a>!</p>
</blockquote>
<h1><a href="#-playstation-3-eye" aria-hidden="true" class="anchor" id="-playstation-3-eye"></a>📷 PlayStation 3 Eye</h1>
<p><img src="https://github.com/user-attachments/assets/ec9a8cef-30d4-4b9e-9ec8-48bf7d70a98e" alt="ps3eye" /></p>
<h1><a href="#-connection" aria-hidden="true" class="anchor" id="-connection"></a>🔌 Connection</h1>
<p>Simply connect the PlayStation 3 Eye with any USB port on your Computer.</p>
<p>Do not exceed 5 meters of total cable length (including the 1 meter USB cable of the PlayStation 3 Eye camera), if you are using passive USB extensions cables. If you need to lay out cables over longer distances, its required to get active repeater USB cables or place USB Hub between them to repeat the data signals to avoid signal loss. Externally powered active USB repeater cables are not required as PlayStation 3 Eye cameras can still run at a very low USB voltage (<code>~3.3v</code>).</p>
<h1><a href="#-installation" aria-hidden="true" class="anchor" id="-installation"></a>💿 Installation</h1>
<p>To use the PlayStation 3 Eye camera, you will need LibUSB drivers in order for <strong>PSMoveServiceEx</strong> to receive image streams and change settings from the camera. You can use <strong><a href="https://github.com/Timocop/PSMoveServiceEx-Virtual-Device-Manager" rel="nofollow ugc">PSMoveServiceEx - Virtual Device Manager</a></strong> to install all necessary camera drivers.</p>
<p>Navigate to <code>VDM - Service Management</code> and click <code>Install PlayStation Eye Drivers</code> to install the drivers for the PlayStation 3 Eye camera.</p>
<blockquote>
<p>[!NOTE]
Those drivers are not compatible with DirectShow and PlayStation 3 Eye cameras will not show as Webcams in Microsoft Windows. Decreasing the risk of other applications accessing them.</p>
</blockquote>
<p><img src="https://github.com/Timocop/PSMoveServiceEx/assets/22834512/831ca78a-8a2a-4b0a-89c1-4355d9b2ea81" alt="" /></p>
<h1><a href="#️-configuration" aria-hidden="true" class="anchor" id="️-configuration"></a>⚙️ Configuration</h1>
<p>Use <strong>PSMoveServiceEx Config Tool</strong> to configure the PlayStation 3 Eye camera. You can find all camera settings when calibrating controller or head-mounted display colors in <code>Config Tool &gt; Tracker Settings &gt; Color Calibration</code></p>
<table>
<thead>
<tr>
<th>Steps</th>
</tr>
</thead>
<tbody>
<tr>
<td><img src="https://github.com/Timocop/PSMoveServiceEx/assets/22834512/6d18eff6-aa38-467c-bed5-14deceb7a36a" alt="" /></td>
</tr>
<tr>
<td><img src="https://github.com/Timocop/PSMoveServiceEx/assets/22834512/3b1f11e0-36ee-493f-befa-1077382cd775" alt="" /></td>
</tr>
<tr>
<td><img src="https://github.com/Timocop/PSMoveServiceEx/assets/22834512/478f5ad9-393a-4ef6-923b-0938e7a98897" alt="" /></td>
</tr>
</tbody>
</table>
<h1><a href="#-troubleshooting" aria-hidden="true" class="anchor" id="-troubleshooting"></a>🧰 Troubleshooting</h1>
<h3><a href="#-psmoveserviceex-config-tool-stream-shows-tracker-timed-out-or-has-a-unstable-framerate" aria-hidden="true" class="anchor" id="-psmoveserviceex-config-tool-stream-shows-tracker-timed-out-or-has-a-unstable-framerate"></a>📌 PSMoveServiceEx Config Tool stream shows 'Tracker timed out.' or has a unstable framerate.</h3>
<p>This means PSMoveServiceEx did not receive any image from the camera in a while or the image could not be received in time from the camera.
This can be caused by the following reasons:</p>
<ul>
<li>USB cable too long (signal loss).</li>
<li>Too many heavy-duty devices connected (such as cameras) to one USB Host Controller causing insufficient bandwidth.</li>
<li>Device disconnected.</li>
<li>Improper configuration (such as too high framerate).</li>
<li>Bad or broken cable.</li>
</ul>
<blockquote>
<p>[!NOTE]
Please check <a href="https://github.com/Timocop/PSMoveServiceEx/wiki/Compatible-Devices" rel="nofollow ugc">Compatible Devices</a> and <a href="https://github.com/Timocop/PSMoveServiceEx/wiki/Hardware-Requirements" rel="nofollow ugc">Hardware Requirements</a> to properly connect your PlayStation 3 Eye camera.</p>
</blockquote>
<h3><a href="#-playstation-eye-3-cameras-do-not-show-in-psmoveserviceex-config-tool" aria-hidden="true" class="anchor" id="-playstation-eye-3-cameras-do-not-show-in-psmoveserviceex-config-tool"></a>📌 PlayStation Eye 3 Cameras do not show in PSMoveServiceEx Config Tool.</h3>
<p>Check if all camera drivers are installed properly as seen in <a href="https://github.com/Timocop/PSMoveServiceEx/wiki/Setting-up-the-PlayStation-3-Eye-Camera#-installation" rel="nofollow ugc"><strong>💿 Installation</strong></a> section of this page or restart PSMoveServiceEx. If they are installed properly and they still wont show up, check troubleshooting section <a href="https://github.com/Timocop/PSMoveServiceEx/wiki/Setting-up-the-PlayStation-3-Eye-Camera#-psmoveserviceex-config-tool-stream-shows-tracker-timed-out-or-has-a-unstable-framerate" rel="nofollow ugc"><strong>📌 PlayStation Eye 3 Cameras do not show in PSMoveServiceEx Config Tool.</strong></a>.</p>
</div>
</article>
<nav id="index">
<a href="/m/Timocop/PSMoveServiceEx/wiki_index">🗂️ Page Index for this GitHub Wiki</a>
</nav>
</div>
<script defer src="https://static.cloudflareinsights.com/beacon.min.js/v833ccba57c9e4d2798f2e76cebdd09a11778172276447" integrity="sha512-57MDmcccJXYtNnH+ZiBwzC4jb2rvgVCEokYN+L/nLlmO8rfYT/gIpW2A569iJ/3b+0UEasghjuZH/ma3wIs/EQ==" data-cf-beacon='{"version":"2024.11.0","token":"4645764ca8384bfc86034b71f1dafd76","r":1,"server_timing":{"name":{"cfCacheStatus":true,"cfEdge":true,"cfExtPri":true,"cfL4":true,"cfOrigin":true,"cfSpeedBrain":true},"location_startswith":null}}' crossorigin="anonymous"></script>
</body>
</html>

View file

@ -12,13 +12,18 @@ RUNS = ROOT / "calibration" / "runs"
def utc_stamp() -> str:
return datetime.now(timezone.utc).strftime("%Y%m%dT%H%M%SZ")
return datetime.now(timezone.utc).strftime("%Y%m%dT%H%M%S.%fZ")
def run_dir(kind: str) -> Path:
path = RUNS / f"{utc_stamp()}-{kind}"
path.mkdir(parents=True, exist_ok=False)
return path
for suffix in ["", *[f"-{i}" for i in range(1, 100)]]:
path = RUNS / f"{utc_stamp()}-{kind}{suffix}"
try:
path.mkdir(parents=True, exist_ok=False)
return path
except FileExistsError:
continue
raise RuntimeError(f"Could not create unique calibration run directory for {kind}")
def write_json(path: Path, data) -> None:

View file

@ -25,3 +25,4 @@
{"ts": "2026-05-18T14:02:51+00:00", "type": "verification", "status": "partial", "note": "Both PS3 Eyes direct to motherboard and live MI_00 instances bound as libusbK: opentrack mode-test now reports all listed modes GOOD including 320x240@30, but frame-test still fails with payload error data[1]=78/79 and bad headers. Stale Unknown PS3 Eye instances from previous hub path remain in PnP."}
{"ts": "2026-05-18T14:05:40+00:00", "type": "verification", "status": "failed", "note": "WinUSB on the two live PS3 Eye MI_00 instances still enumerates high-rate modes but frame streaming fails: one device open hit Access is denied, the other repeated payload error data[1]=78/79 until killed. libusb0, libusbK, and WinUSB have all failed frame reads via opentrack on this machine."}
{"ts": "2026-05-18T14:22:36+00:00", "type": "verification", "status": "partial", "note": "Audio-field sidecar added and offline FOA encode verified; current PortAudio enumeration shows no matching six-channel WASAPI input device, so live Ambisonic capture needs a shared six-input interface/profile or a separately proven adaptive sync path before using independent USB microphones."}
{"ts": "2026-05-18T14:25:36+00:00", "type": "verification", "status": "ok", "note": "PS3 Eye video path found: AllanCat PS3 Eye Universal Driver / PS3EyeDirectShow exposes both Eyes as DirectShow indices 3 and 4 after registering the source filter for two cameras; simultaneous default 640x480 capture produced about 30 fps from both. High-FPS DirectShow mode negotiation remains unproven."}

View file

@ -116,20 +116,24 @@ current_status:
receiver OBS scene has matching Media Sources. Local calibration harness now
has first physical-device access: LeapUVC raw IR video, two Razer Kiyo-class
RGB cameras, all expected microphones, and Scarlett speaker output are
accessible; both PS3 Eye video interfaces are attached but missing their
video-side driver. LeapUVC MSMF mode probing accepts a 320x240x120 request
and reports about 115 fps, though measured OpenCV throughput is lower in the
first rough probe. PS3 Eye video interfaces now bind through libusb-win32
and opentrack enumerates high-rate modes, but frame reads fail while all
cameras sit on one external hub/root path; USB topology is now a live
suspect. Audio-field scaffolding now exists as a separate sidecar:
accessible. LeapUVC MSMF mode probing accepts a 320x240x120 request and
reports about 115 fps, though measured OpenCV throughput is lower in the
first rough probe. The opentrack/libusb PS3 Eye path still enumerates modes
but fails frame reads across libusb-win32, libusbK, and WinUSB. The
AllanCat PS3 Eye Universal Driver / PS3EyeDirectShow path now exposes both
PS3 Eyes as DirectShow indices 3 and 4 after registering the source filter
for two cameras; both streams can run simultaneously at default 640x480
near 30 fps. High-FPS PS3 Eye mode control is not proven yet. Audio-field
scaffolding now exists as a separate sidecar:
six-mic/two-speaker profile, validation, calibration sweep capture/analysis,
raw field recording, and offline FOA AmbiX encoding. Current PortAudio
enumeration does not expose a matching six-channel WASAPI input, so live
field capture requires either a shared six-input device/profile or a
separately proven adaptive sync path for independent USB microphones.
next_action: >
In parallel with the camera driver's next cut, create local
Capture ChArUco intrinsics for DirectShow indices 1-4, then test PS3 Eye
high-rate DirectShow mode negotiation sequentially after the baseline
640x480@30 path is no longer in doubt. In parallel, create local
config/audio-field.json, confirm whether one device exposes six synchronized
mic inputs, replace placeholder mic/speaker geometry with measured world
coordinates, then run the two-speaker calibration sweep.