MiraPlay Web (Beta) Rebuilt β€” A New Browser-Based Platform for OSR Devices

Hi guys,

We have just launched the rebuilt MiraPlay Web (Beta).

MiraPlay Web is a PC browser-based app designed for multi-axis device playback, control, and interaction.

For this rebuilt beta, we redesigned the UI and rebuilt the app structure from the previous version, making it easier for us to add new features and improve the desktop/browser-based experience over time.

Unlike MiraPlay AiO, which is built around a mobile app workflow, MiraPlay Web focuses on a desktop/browser-based experience.

For this beta, we are making MiraPlay Web available not only to MiraBot users, but also to users of OSR / TCode-compatible devices.

Our goal is simple: let more users try it, give feedback, report issues, and help us improve the software together.

:star: Main Features

1. Video Sync Player

Load a local video together with one or more funscripts and play them in sync.
The player also includes built-in motion smoothing / interpolation, designed to make multi-axis playback feel more natural and consistent.

2. YouTube Sync Player

Play YouTube videos together with local funscripts.
Due to YouTube and browser platform limitations, this feature is intended for regular YouTube content rather than adult sites. It can still be useful for dance videos, music videos, previews, and other YouTube-based content.

3. Custom Motions

The current beta keeps the Custom Motions from the previous MiraPlay Web version.
It includes 10 preset motion patterns, with adjustable parameters for changing the motion style.
A completely redesigned Custom Motion system is also in development. Our goal is to make custom motion creation much easier and more flexible than before.

4. Remote Play

Remote Play allows users to create a temporary remote room for remote interaction/control.
Please note that this feature is still in beta. Since the current server infrastructure is limited, some users may experience latency depending on location and network conditions.
We will continue monitoring real usage and feedback, and plan to improve the infrastructure as demand grows.

5. USB Serial and Wireless Connection

MiraPlay Web supports both:

  • USB serial connection
  • Wireless connection, including Bluetooth LE and WebSocket

For MiraBot devices, wireless connection is optimized for the official MiraBot firmware v1.2 or later. If you are using an older firmware version, we recommend updating the firmware first.

For other OSR / TCode-compatible devices, USB serial connection should generally be the most broadly compatible option. Wireless support may vary depending on the firmware and how BLE / WebSocket is implemented.

:new_button: Update Plan

MiraPlay Web will continue to receive active updates, just like MiraPlay AiO.

We are currently working on:

VR playback support for Video Sync Player

We are working on VR headset playback support, including immersive VR mode and direct multi-axis device connection.

Target: late May, if testing goes well.

New Custom Motion system

We are rebuilding Custom Motions from the ground up.

The new system is designed to create more complex loopable motions using adjustable parameters.
It will also support a scene-based mode, where multiple independent motions can be connected together to build a longer motion sequence.
Compared with traditional funscript editing, this approach should be simpler, more stable, and easier to reuse. It is not meant to replace funscripts, but to provide another practical way to create and trigger reusable motion patterns.

Created motions can also be called directly by other MiraPlay applications.

Target: mid-June, if development and testing go smoothly.

About MiraBot and other OSR devices

MiraPlay Web Beta does not currently have a MiraBot-only connection lock.

We want more OSR users to be able to try it, test it, and give feedback. The OSR community has always been very important to this type of project, and we believe better tools can help the whole ecosystem grow.

That said, MiraPlay Web is still part of the MiraBot ecosystem.
MiraBot users will continue to get the most optimized and integrated experience, especially when using MiraBot firmware v1.2 or later, wireless connection, MiraPlay AiO, and future MiraBot-specific features.

:link: Related MiraBot / MiraPlay links

For anyone interested, here are the related posts and pages:

Feedback, bug reports, compatibility reports, and feature requests are very welcome.

If you try it with a MiraBot or another OSR / TCode-compatible device, please feel free to share your setup and results in this thread.

2 Likes

Can I use my Miraplay AIO account (without registering), or do I need to create a new account on the web?

Yes, you can use the same account.
MiraPlay AiO and MiraPlay Web share the same account system, so you don’t need to register a separate account for MiraPlay Web. Just log in with your existing MiraPlay AiO account.

1 Like

Just want to check something about the upcoming VR playback feature. Does this mean I’ll be able to open Miraplay web in the quest3 browser and connect directly to my Mirabot? And would that connection be through wifi or Bluetooth?

Yes, that’s the plan.
You should be able to open MiraPlay Web directly in the default Quest browser and use it to play 180Β° VR videos.
For the device connection, Quest can connect directly to MiraBot through Wi-Fi / WebSocket.
Bluetooth is not supported in this case, because browser-based apps on Quest currently do not have the required Bluetooth access.

Will we be able to create more than one room per day eventually. I think just one a day is a bit unfair because there aren’t many sites that allow you to use t-code devices and have people control them from that site.

The current limit is mainly due to limited server resources.
But you are right β€” one room per day is probably a bit too restrictive. We will increase the free usage limit so more users can properly try the feature.
Remote Play is still in beta, and we know there is still room to improve the experience, especially around stability and latency. Continued improvements to Remote Play are already part of our development plan.

MiraPlay Web Update β€” VR Immersive Mode for Video Sync Player

Hi guys,

A new VR Immersive Mode has been added to the Video Sync Player in MiraPlay Web.

With this update, you can use MiraPlay Web in Quest Browser to play local VR videos with matching funscripts, and control MiraBot through MiraPlay AiO Device Bridge.

The basic workflow is:

MiraPlay Web β†’ MiraPlay AiO Device Bridge β†’ MiraBot Device

MiraPlay Web handles the VR video and funscript playback, then sends the synced motion commands to MiraPlay AiO.
MiraPlay AiO forwards those commands to the connected MiraBot device.

This is useful because some VR browser environments, including Quest Browser, may restrict direct local connections to devices. Device Bridge provides another connection path for these cases.


Setup video

I also recorded a short setup video showing the basic workflow:

The video shows how to open MiraPlay Web in Quest Browser, connect through MiraPlay AiO Device Bridge, select a VR video and funscript, and enter VR Immersive Mode.


How to use it

1. Connect through Device Bridge

In Quest Browser, log in to MiraPlay Web.

Then connect MiraPlay Web to MiraPlay AiO through Device Bridge.

Please make sure:

  • MiraPlay AiO is updated to v1.7.5 or later
  • Device Bridge is enabled in MiraPlay AiO
    *Use the same account for MiraPlay Web and MiraPlay AiO. The bridge connection will be handled automatically.
  • Both devices are on the same Wi-Fi network
  • MiraBot is connected through MiraPlay AiO

2. Enter VR Immersive Mode

Open Video Sync Player in MiraPlay Web.

Select your VR video file and the corresponding funscript file.

Then choose the correct VR video format:

  • 180Β° / 360Β°
  • Left-Right / Top-Bottom

Click Enter VR Mode to start immersive VR playback with funscript sync.


MiraPlay AiO v1.7.5

This workflow requires MiraPlay AiO v1.7.5 or later.
For the full MiraPlay AiO v1.7.5 update notes, please check here

Besides Device Bridge, v1.7.5 also improves MiraPlay AiO’s own VR playback experience, including the new VR Gaze Menu, video zoom controls, and easier playback control while using a phone-based VR headset.

OSR / TCode Device Compatibility

As mentioned before, MiraPlay Web and MiraPlay AiO are currently open and free for all TCode device users.

However, since third-party devices may vary in firmware, hardware, and implementation, we cannot guarantee full compatibility with every device.

If you encounter any issues while using MiraPlay with your device, please feel free to send us feedback. We will do our best to improve compatibility where possible.


Feedback is welcome, especially from users testing this with Quest Browser and different VR video formats.

1 Like