Hi everyone,
Major update here. The project has grown a lot since the first announcement, and this post now contains the full current overview.
MAJOR UPDATE (What Changed)
-
Distributed multi-process, multi-language runtime (Python + C++).
-
Real-time process scheduling, cross-service communication, and runtime monitoring.
-
Cross-platform support: Windows and Linux.
-
Fully open source under AGPL-3.0-only.
-
End-to-end real-time graph processing.
-
High-performance C++ nodes for performance-sensitive workloads.
-
C++ 8K player node with VR-to-2D mode and free zoom/pan ROI viewing.
-
PyQt-based visual graph editor for editing all node/service properties.
-
Monaco editor for code fields (LSP integration is not ready yet).
-
Very strong extensibility with existing infrastructure + Python script nodes.
-
Multi-axis signal routing and TCode generation.
-
Intiface / Buttplug integration.
-
Lovense local/mock API workflow integration.
-
theHandy integration is in progress.
-
Active game-MOD integration testing with promising early results.
-
Experimental Lovense traffic interception for some embedded-SDK games, converting packets into stroker-oriented signals (for devices such as theHandy, SR6, etc.).
-
Planned next features: funscript playback and funscript recording.
-
Headless Runner mode: run saved blueprints without opening full Studio UI.
What F8Studio Is
F8Studio is a visual + programmable pipeline framework for real-time interactive signal processing.
You can build node graphs that ingest different media/sensor/game inputs, process them in real time, and map outputs to control protocols/devices.
It supports both:
-
Visual graph workflows for fast iteration.
-
Scripted workflows (Python nodes) for advanced custom logic.
Real-Time Input Coverage
The runtime is designed to work with many content sources in real time, including:
-
Local video files.
-
Live streams.
-
Running games.
-
Screen capture pipelines.
This also includes non-video use cases such as functional/algorithmic pattern generation.
Architecture (Core Design)
F8Studio uses a hybrid communication model:
-
Shared memory for high-throughput frame sharing between services.
-
NATS pub/sub messaging for decoupled signal and control routing.
Benefits:
-
Modular service boundaries.
-
Better fault isolation.
-
Mixed-language service composition.
-
Easier integration of new community algorithms/tools.
Positioning (Important)
To keep expectations realistic, current stage is best for:
-
Developers.
-
Users with coding experience.
-
DIY builders who want custom control pipelines.
For beginners, more packaging/productization is still needed.
But with well-automated blueprints + headless mode, practical one-click style usage is already possible for some workflows.
Showcase Videos
You can get blueprint shown in video from HERE
- [F8Studio] OpenCV Tracker → TCode
- [F8Studio] Game (Skeleton and Spine animation) → TCode
- [F8Studio] Audio Driven TCode
- [F8Studio] Functional TCode Generation
Links
-
GitHub: GitHub - feel8-fun/f8studio
-
Homepage: https://studio.feel8.fun/ (documentation in progress)
-
Join Discord: Feel8.Fun
-
Prebuilt Windows releases: Releases · feel8-fun/f8studio · GitHub
Collaboration Request
We are expanding game-MOD integration and would love help from people with MOD development experience, especially:
-
Unreal Engine
-
Ren’Py
-
RPGMaker
If you are interested in building reusable blueprints (including headless-ready workflows), please join us.