@Yoooi Oh cool! I haven’t been able to figure out streaming the script to MFP from DeoVR, I enabled Remote Control in DeoVR, but I’m not sure how to load the script in MFP. Do I need to do something to the Scipt Librarys or Media Path Modifiers? Or edit something in the script menu like “Open Folder” or “Load”
You need to use the patreon only build, public builds don’t support SLR.
Then under DeoVR you will find “SLR” button where you enter your SLR credentials.
1 Like
MultiFunPlayer v1.25.1:
Download: Release MultiFunPlayer v1.25.1 · Yoooi0/MultiFunPlayer · GitHub
Patreon build:
v1.25.1:
- Fix exception when clearing buttplug device list
- Fix possible buttplug deadlock
- Fix media content expander defaulting to expanded state
v1.25.0:
- Add AB loop support (#112)
- Support latest buttplug version by updating to Buttplug.Net library (#115)
- Add separate bypass toggles for script/motion provider/custom transition (#71)
- Add ability to disable/enable shortcuts (#120)
- Make motion provider gap fill work based on script presence (#67)
- Allow enabling window resize (#9)
- Add ability to limit motion provider speed when updating based on other axis motion
- Start work on help/documentation page (Home | MultiFunPlayer)
- Rework heatmap/chapter/bookmark tooltips
- Add ability to disable sync on auto-home start/end
- Use precise sleep for main script update loop
- Make internal media source playlist items easier to click
- Change default mpv arguments to
--keep-open --pauseto not pause on next playlist file - Change axis settings to enable random motion provider on R0/R1/R2 by default
- Fix TCP output sending data in 1024 byte chunks (#122)
- Fix plex media source getting stuck due to infinite timeout
- Fix internal media source not clearing media state when disconnecting
- Fix exception when using bookmark and chapter actions when none are loaded
- Fix stutter when auto-home delay is longer than sync duration
- Fix smart limit canvas popup
- Fix keyframe heatmap not displaying long slopes correctly
- Fix unable to map multiple buttplug devices with the same name
If you like what I’m doing, please consider supporting me on Patreon
6 Likes
Finally Lovense Gravity support, thank you <3
1 Like
If anyone uses e-stim here I added a proof of concept audio output in this build:
https://nightly.link/Yoooi0/MultiFunPlayer/actions/runs/4835566690
Would like to know if/how usable it is with e-stim, and any suggestions on what to change/add.
MultiFunPlayer v1.25.2:
Download: Release MultiFunPlayer v1.25.2 · Yoooi0/MultiFunPlayer · GitHub
Patreon build: https://www.patreon.com/posts/82509959
v1.25.2:
- Add support for upcoming SLR multi-axis funscript
- Fix exception when trying to create output target using missing type
- Fix crash after removing/disabling an axis from device settings
v1.25.1:
- Fix exception when clearing buttplug device list
- Fix possible buttplug deadlock
- Fix media content expander defaulting to expanded state
v1.25.0:
- Add AB loop support (#112)
- Support latest buttplug version by updating to Buttplug.Net library (#115)
- Add separate bypass toggles for script/motion provider/custom transition (#71)
- Add ability to disable/enable shortcuts (#120)
- Make motion provider gap fill work based on script presence (#67)
- Allow enabling window resize (#9)
- Add ability to limit motion provider speed when updating based on other axis motion
- Start work on help/documentation page (Home | MultiFunPlayer)
- Rework heatmap/chapter/bookmark tooltips
- Add ability to disable sync on auto-home start/end
- Use precise sleep for main script update loop
- Make internal media source playlist items easier to click
- Change default mpv arguments to
--keep-open --pauseto not pause on next playlist file - Change axis settings to enable random motion provider on R0/R1/R2 by default
- Fix TCP output sending data in 1024 byte chunks (#122)
- Fix plex media source getting stuck due to infinite timeout
- Fix internal media source not clearing media state when disconnecting
- Fix exception when using bookmark and chapter actions when none are loaded
- Fix stutter when auto-home delay is longer than sync duration
- Fix smart limit canvas popup
- Fix keyframe heatmap not displaying long slopes correctly
- Fix unable to map multiple buttplug devices with the same name
If you like what I’m doing, please consider supporting me on Patreon
3 Likes
I’m sorry I haven’t read through the years of comments on here yet. But in the original post it mentioned lube as a function. Can the lube pump be actuated by scripts? So the videos would automatically add lube at a scripted point!?
Yup, tho I’m not sure if/which firmware supports it.
You can activate lube via a script (<videoname>.lube.funscript) or you could setup a looping motion provider with a custom script that for example is at 0% for 1 minute, then at 100% for 5seconds. I should probably add a new motion provider that lets you specify on/off time so you dont have to make a script each time.
Also make sure you have lube axis enabled in device settings.
Once I get a Tempest max device I will gladly look into this. I hate the fact that i Keep having to look under my VR headset to re-lube my launch. Also would it be any more difficult to add a second pump? I’d love for a second pump to be added. Just to add a squirt of water every now and then to loosen up the lube.
Don’t think there is a firmware with two pumps, from MFP side its not an issue but the firmware needs to read the commands and run the pumps.
From what I understand you can run more than one device at a time and have each device run on separate scripts right? For example, a lovense edge 2 can use a vibration script while at the same time your Fleshlight Launch is running a normal scripts. That’s just how its been explained to me. I haven’t tested or used the program yet. But if that’s the case I could just run a lube script for a separate device(lube pump filled with water).
Is that now how it works?
Yes you can run multiple devices at the same time.
For Serial/TCP/UDP/Websocket/Pipe outputs MFP sends all axes as TCode. So you would have to parse it on your pump device.
With buttplug output you can map specific axes to specific devices.
I was wondering how well the lovense gravity plays with funscripts… and if it was a thumbs up or down to get it… thank you for making it possible with MFP Yoooi!!
1 Like
Does the gravity work well with MFP? Like no stutters etc?
Given that I wrote the V6 buttplug library from scratch, I wonder if all the bluetooth stroke devices that had trouble before are now working fine. Like Launch/The Handy/Vorze A10 etc.
Unfortunately, handy via intiface still has stutters on mfp
Dear, what does it mean to support SLR multi-axis scripts. I can’t find their format anywhere - is there a link or is this information under a non-disclosure agreement?
SLR extended funscript format to support more axes, tho I think none are released as of now.
1 Like
Tried to set it up to work using a SMB share on HereSphere with the Handy. Got everything connected fine, I see the script playing in the app perfectly, but the handy is playing it all jittery, not smooth at all. Is it a known issue or is it fixable on my side? I’m using HereSphere demo if that matters, I wanted to see if the whole thing was working before buying.
It is a known issue as in The Handy wants you to send all communications thru their servers, which is terrible for real time motion. Their “fix” for that is to upload the whole script to the device which MFP doesnt do.
The Handy support in MFP is added as “experimantal” feature. You could maybe try lowering the update rate. Or you could try using MFP with buttplug.io as it communicates via bluetooth.
Otherwise you have to use some other player that uploads the whole script to the device, and loose like 95% of MFP features.
I set it up with buttplug.io and it’s still jittery, a little but better, but still pretty bad. I also lowered the update rate to the minimum (5hz). Is there something else to try?