Which devices AutoScript Sync plays on
AutoScript Sync plays a funscript on two kinds of device. The Autoblow AI Ultra is driven through Autoblow's cloud, and it is the only device we have tested on real hardware. The Handy, The Handy 2 Pro, Kiiroo Keon/Onyx, Lovense Solace/Solace Pro and OSR2/SR6 connect through Intiface on your own PC; the app has a profile for each, but none has been tested by us on a real unit yet. Beyond strokers, vibrators, rotating toys and air pumps follow the script in the next update.
Checked against the app's code on 21 September 2026.
The compatibility table
Pick the connection in the app's Device panel: Autoblow AI Ultra (cloud) or Intiface / Buttplug (local). The speed and spacing figures are the limits the app's profile for that device sets, not measurements of the device.
| Device | How it connects | How it plays the script | Status | App's speed profile (Intiface devices: from the next update) |
|---|---|---|---|---|
| Autoblow AI Ultra | Autoblow's cloud API; the PC and the device both need internet | Script uploaded once, the device plays it; the app sends start, stop, offset and seek | Tested on real hardware | ~400 u/s · 60 ms |
| The Handy | Bluetooth, through Intiface | Streamed live from the PC, one move per script point | Through Intiface, not yet tested by us | ~490 u/s · 55 ms |
| The Handy 2 Pro | Bluetooth, through Intiface | Streamed live from the PC, one move per script point | Through Intiface, not yet tested by us | ~575 u/s · 50 ms |
| Kiiroo Keon / Onyx | Bluetooth, through Intiface | Streamed live from the PC, one move per script point | Through Intiface, not yet tested by us | ~345 u/s · 70 ms |
| Lovense Solace / Solace Pro | Bluetooth or the serial Lovense USB dongle, through Intiface (the newer HID dongle: next update) | Streamed live from the PC, one move per script point | Through Intiface, not yet tested by us | ~450 u/s · 60 ms |
| OSR2 / SR6 | USB serial, through Buttplug's TCode support in an Intiface server you set up yourself; the app's own COM-port picker comes in the next update | Streamed live from the PC, one move per script point | Through Intiface, not yet tested by us | ~500 u/s · 50 ms |
| Other strokers Intiface lists | Through Intiface | Streamed live from the PC | Through Intiface, not yet tested by us | 350 u/s · 70 ms (generic) |
| Vibrators, rotating toys, air pumps | Through Intiface | Vibrators: by hand from the Vibration panel today. Following the script: next update | Next update | — |
Where the numbers come from. The profiles are published manufacturer figures minus about 10%. The Autoblow (400 u/s) and OSR2/SR6 (500 u/s) values are unverified defaults: Autoblow publishes no speed figure, and an OSR's speed depends on how it was built. In the released app the profile shapes the script sent to the Autoblow; applying these limits, and your Stroke Settings, to Intiface devices comes in the next update.
You can choose the profile yourself under Device model, or leave it on Auto-detect on connect and the app matches the device name Buttplug reports. The match looks for words in the name, so any device whose name contains “lovense” or “max”, a vibrator included, gets the Lovense Solace profile. Choosing the model by hand avoids that.
Two paths, and why they behave differently
Autoblow AI Ultra: through Autoblow's cloud
There is no local connection to the Ultra. The app asks latency.autoblowapi.com which server your device is on, using the device token you paste in, then uploads the fitted .funscript once when you press Send Script to Device. The Ultra plays the script itself. From then on the app sends only start, stop, offset and seek, and adds half the measured round trip to every start.
While it plays, the app reads the device's own script clock every 1.5 to 5 seconds. A gap of 80 to 350 ms is trimmed through the device's offset; a gap over 350 ms restarts playback at the video's position. Only the fitted script goes to Autoblow's cloud, with the analysis data stripped out. The video never leaves your PC. The Autoblow AI Ultra setup page covers tokens, lights and connection problems, and how the drift correction works explains the timing.
Everything else: Intiface on your PC
Other devices go through Buttplug, the open protocol behind Intiface. The app starts its own bundled Intiface engine on ws://127.0.0.1:12345, or uses an Intiface Central you already run. Nothing is uploaded anywhere: each script point becomes one move command sent from your PC, timed to reach the next point.
This path has no latency measurement and no drift correction. The script runs on your PC's clock from each play or seek, shifted by your Offset setting. The Intiface setup guide covers the engine, scanning and what the app sends.
How we test, and what “not yet tested” means
The Autoblow path has been run against Autoblow's live API with a real Ultra. Every other device path was tested against software that stands in for the device: mock Buttplug servers, and in one end-to-end run, fake Lovense toys on the real bundled engine. We have not run a real Handy, Kiiroo, Lovense, OSR2 or SR6, and we have not checked the app against Intiface Central v3.
So “Through Intiface, not yet tested by us” means the code path exists and passes its tests, and the device should work if the Intiface engine recognises it. It does not mean we have felt it play a script. If you try one of these devices, the trial is the way to find out before you pay, and the AutoScript Sync Discord is where to tell us how it went.
One more limit: the bundled engine is intiface-engine v1.4.8, from November 2023. A toy released after it may not be in its device list.
VR: DeoVR on a Meta Quest
For VR the app works with DeoVR's Remote Control. Connect your device first, then the app connects to DeoVR on TCP port 23554 and serves the loaded video to the headset over HTTP on port 8942 on your local network. DeoVR's playback time then drives the device: play, pause and seeks in the headset carry over, and a jump of more than 900 ms counts as a seek.
Two limits to know. DeoVR reports its clock about once a second and the app does not fill in between reports, so timing is coarser than on the desktop. And while the headset session runs, any device on the same network can fetch the open video from port 8942, because that server has no password. The video does not go to the internet. The headset path was tested only against a mock DeoVR, not a real Quest.
Using the saved file with other players
On the desktop the app plays video in its own window with embedded VLC. It does not sync with HereSphere, MPC-HC, an external VLC, MultiFunPlayer, XBVR or any other player. What it does leave you is an ordinary file: every finished generation is saved beside the video as <video>.funscript, with sorted, whole-number actions from 0 to 100, which programs such as OpenFunscripter and MultiFunPlayer can open.
That file is the route to any device the app does not drive itself. The funscript format reference explains what is in it, and the free funscript validator checks a file against a device's speed limit before you load it elsewhere.
Read next
- Using AutoScript Sync with IntifaceThe bundled engine, scanning, and what every Intiface device receives.
- The Handy over BluetoothWhy it is Bluetooth only, and the two Handy profiles.
- How to make a funscriptFrom a video on your PC to a script your device can play.
- The funscript generatorWhat the app does with a video, and what you get back.
Try it with your own device
The free trial lasts one day with every feature unlocked. It uses the same installer buyers get, and it starts when you click Start free 1-day trial in the app, which needs an internet connection.