ScriptPlayer Beta Features (and how to get them)

Hey there, I’ve been trying get my we-vibe verge to work in conjunction with my Handy for a while now, and I haven’t been able to find a good solution. What I want to do specifically is have multiple devices using different funscripts linked to a single video source. The closest single app I’ve found to what I want is MultiFunPlayer, but it seems like it was designed for the OSR in particular, and while it has multiple channels and a bunch of connectivity options, there’s pretty much no documentation out there for it, so while I can get it working with Intiface, I haven’t been able to hook it up to the handy via wifi. Using the Handy through bluetooth with Intiface just makes all of my devices respond jerkily.
Scriptplayer, on the other hand, can connect to the handy directly while also using Intiface, but it seems like it can only run one script at a time.

So my question is, a) is there some way for Scriptplayer to route multiple scripts to different devices, or b) is there a way to get multiple copies of Scriptplayer running at the same time, linked to a single video player?

Right now, the only way I’ve found to do what I want is to use Scriptplayer to control the vibe, link it to DeoVR, and have that app control the Handy directly. That means I can only watch video using my headset, which is kinda awkward.

Nope, neither of those things are possible

That is sad. I am sad. :frowning_face:

Srsly tho, thanks for responding. I think that being able to do one of those things would really improve scriptplayer, but I can barely make a python file to convert up/down motions into vibration intensities, so I’m certainly not going to try and guess how hard it would be to program multiple script functionality in.

I’ll keep troubleshooting, and if I find any solutions I’ll try to remember to come back and post them.

Why do you need multiple funscripts?
Do none of the vibration-conversion modes work for you?

hey having this weird issue keep happening and cant figure out how to resolve it. Everytime i load a script and then connect my handy then scriptplayer will stall for a few seconds and will just close, ive tried connecting my handy first then the script but still closes a few seconds later. ive enjoyed using scriptplayer alot so would like some kind of resolution from anyone who could help. thanks

Apparently an issue with the HandyFeeling server:

Hello :slight_smile: I ran into a bug that prevented e-stim audio from playing when using an external player, found that someone else had already reported it, and I think I’ve found the issue. I sent you a pull request with what I think is the proper fix, feel free to have a look at it.

1 Like

Update: Should be fixed now - new beta version available:
https://ci.appveyor.com/project/FredTungsten/scriptplayer/build/job/xmsof2minm5s3jbt/artifacts

3 Likes

@Liquid Multi-axis devices (like OSR2 and SR6) have a funscript for each axis.

Edit: Sorry all, trying to figure out how to block quote the original post.

Seems to be working for me now. Thanks for the quick fix!

I want multiple funscripts because vibes are best with different patterns than a stroker, especially if you’re using them together.

As for why I made the program, part of it was just as a coding experiment, part of it was for better customization of the patterns, and part was that unlike yours, not everyone’s funscripts come with a simple txt beatmap with just timings on it, so I wanted something more universal.

1 Like

Issue: High cpu usage from ffmpeg.exe when there is a path with ffmpeg registered while using ScriptPlayer with remote control function. (tested with DeoVR / Heresphere and Whirligig)

ffmpeg is what generates the thumbnails and previews for loaded videos and videos in your playlist - a high cpu usage means it’s running efficiently (it will be done faster)

You can click the icon in the top right corner to show what it is currently working on:
image

When it’s done generating all optional assets it should stop using any resources.

Edit: True. Since I enabled the automatic thumbnail generation by accident, it really takes a lot of time for VR content. Didn’t expect that, because non VR content is done within a few seconds.
Sorry for any inconveniences. :slight_smile:

1 Like

Is it possible to choice player by default ?

I would like to use deovr player as my default player but i have to change it everytime. There is some bug or error with the bluetooth connection. Sometimes it broke at the middle of action so i have to reopen the scriptplayer and load the files by manually. It means that every time i have to choose deovr again and again.

Also i would like to know that if anyone know the pattern for filenaming in Deovr. I would like to use fuzzy name matching option but i cant use it for Deovr because i dont know the patterning method for filenaming.

There is an option to remember the last used playback mode.

image

I don’t know the pattern for DeoVR, but it has to be a regular expression to work, e.g.

image

The playlist gets saved when you close ScriptPlayer, so if you have a lot of crashes, you would have to load the files, close ScriptPlayer and open it again.

1 Like

Thanks a lot. This playback mode will be really usefull in my case .

Actually it’s not working for vr files which i have played via deovr. U have to add it one by one. If u dont it’s not working in playlist mode as normal files and i think that it must be related with the filename issue.

Oh, yes, makes sense

@Liquid
I am also having issue with deovr on windows (air link to quest 2).
ScriptPlayer would load and work with the first funscript file, but once you exit the video in deovr, things start not working.
Script might continue to play while nothing is playing in deovr, subsequent playback in deovr would cause scriptplayer not to load the script.
Probably due to handling/syncing using json between deovr and scriptplayer.
btw, where do I find the debug output? I am seeing debug lines in the code but can’t see where it is writing to.

While it’s running you can view it with DebugView, if it crashes you can find it in %AppData%\ScriptPlayer